Documentation
Everything the agent knows, written down.
Guides for briefing an agent, a reference for every connector, and the full REST and webhook API. Written by the people who build it, updated the day it ships.
Quickstart
One call creates an agent, points it at a source and hands it a policy. It reads your transcripts before it answers anything, so the first draft already sounds like your team.
Sandbox keys, no card, no call
Every response is replayable
Rehearse on real calls before going live
Browse
Start anywhere, nothing assumes the rest.
Each section stands on its own. If a page needs something from another, it links to it rather than assuming you read it.
Getting started
Connect a source, point Sermo at your transcripts and have a working agent answering by the afternoon.
8 articles
Composer
Brief an agent the way you would brief a new hire: the job, the policies, and when to stop and escalate.
12 articles
Voice agents
Latency budgets, barge-in handling, warm handoff and how phone numbers route to the right agent.
14 articles
Chat agents
Widget install, help-centre embedding, and answering from the saved replies your team already wrote.
11 articles
Connectors
Every supported integration, the fields it reads, and exactly what it writes back where.
41 articles
Signal
Root-cause clustering, volume reporting, and rolling a single fix out to every agent at once.
9 articles
API reference
REST endpoints, webhook events, rate limits, error codes and the versioning policy.
26 articles
Security
Data residency, retention windows, SSO and SCIM, and what lands in the audit trail.
7 articles
Changelog
Every release, what changed, and whether you need to do anything about it.
Updated weekly
For developers
An API you can plan around.
The contract is the product. If we cannot keep an endpoint stable we version it rather than quietly changing what it returns.
Typed and versioned
Every endpoint is versioned in the path and never changes shape underneath you. Deprecations get twelve months and a migration note.
Sandbox from day one
Sandbox keys issue instantly and behave exactly like production, against synthetic transcripts you can reset whenever.
A changelog worth reading
Every release says what changed and whether it needs anything from you. Subscribe by RSS or webhook.
Developer channel
A shared channel with the engineers who build Sermo, not a ticket queue. Most questions get an answer the same working day.
Request an invite
Status and incidents
Live availability per region and per connector, with a written post-mortem on anything that lasted longer than five minutes.
All systems operational
99.98%
Get started
Ready to hear what your support could sound like?
We will build you a working agent on your own transcripts — and show you the numbers before you commit to anything.