Everything the platform produces can go somewhere else. Into your CRM. Into a channel your team already watches. Into a ticket queue. Into your reporting stack. And anything we hold, you can pull back out.
When a conversation finishes processing, we can notify your system with the details. Every conversation, automatically.
Any alert can fire off to somewhere else - kicking off a workflow, opening a ticket, messaging a channel, or calling a contact in an emergency.
Query anything back out through the API. Conversations, write-ups, what was flagged, what's outstanding.
A conversation ends, something gets flagged, and their system does the thing. We tell you; your workflow acts.
Land it in the warehouse next to revenue and ticket data, and ask questions no single system can answer.
Providers building toward one pane of glass pull everything through the API and put it inside the portal they already ship.
Create a user in their platform and have it created here automatically. No spreadsheet, no manual step.
If your team already runs automations, this is another source of triggers - and a fairly rich one.
This is the honest reason the API exists. Every partner has found a use for it we didn't anticipate.
Conversations and everything we've worked out about them are carried in vCon, an open industry format for conversation data, rather than something we made up.
Which means it's readable by anything that understands the format, and leaving doesn't require an export project or a negotiation to get your own data back in a usable shape.
We think that's the right way round. A vendor that needs to trap your data to keep you is telling you something about the product.
Credentials against a sandbox tenant, the current reference, and a corpus to build against, so you can hold a real enriched object before committing to anything.
What the surface covers: what you can build.