Integrations
Integrations that give the agent
something real to say.
A voice agent is only as good as the data behind it. Sono connects to the systems you already run — your PMS, your CRM, your helpdesk, your outreach tool — over their API, their webhooks, or an iPaaS hop, so the agent answers from your live records instead of a static script and writes every outcome back where your team already works.
How a system connects
Sono reads and writes your records directly. Hostaway and lemlist both connect this way.
Your system tells Sono when something happens; Sono calls back with the outcome.
For anything without an API worth using, or when you already run an automation layer.
A nightly CSV still works, and is often the fastest way to start.
Available now
Built integrations,
ready to switch on
Two systems are connected out of the box, each aimed at a different job. Everything else connects through the methods below.
Hostaway
Short-term rental PMS
Guest calls answered with that unit's own access code, wifi, check-in window and house rules — matched from the caller's reservation before the agent speaks. Maintenance reports become Hostaway tasks.
- →Reservations, listings and calendar, read live
- →Conversations and tasks written back
- →One number for the whole portfolio
lemlist
Sales engagement & cold email
Campaign events fire a webhook into Sono, which adds the two channels email can't reach — an AI call and a WhatsApp message — then writes the outcome back so the sequence reacts.
- →Opens, clicks, replies and steps as triggers
- →AI cold calling plus WhatsApp follow-up
- →Suppression honoured across all channels
Everything else
The rest of your stack
connects the same way
A named integration is a convenience, not a requirement. These categories are already in production across Sono deployments.
Sono writes tickets into Zendesk, Freshdesk, HubSpot and Jira Service Management with the caller's details, the transcript and the recording attached. Anything else connects through a webhook or a thin API connector.
Call outcomes, qualification answers and booked meetings land on the contact record, so a conversation Sono had shows up next to the ones your reps had. Meetings are written straight into the right calendar.
Sono reads the overdue ledger from your billing, ERP or accounts-receivable platform and writes back every outcome — contacted, promised-to-pay with a date, disputed, wrong number. See payment reminders and collection calls.
Availability checked and slots confirmed during the call, not after it. The caller hangs up with a time, and the calendar already has it. See appointments and bookings.
Keep your existing numbers and carrier. Sono can sit in front of your line as first response, behind your team as overflow, or only outside opening hours — you decide which calls reach it.
The rules
What every integration
may and may not do
The same boundaries apply whether Sono is connected to a PMS, a CRM or a ledger.
| Access | What that means | Who decides |
|---|---|---|
| Read | Only the fields needed to identify the caller and answer their question | You approve the field list before go-live |
| Write | Notes, tickets, tasks, call outcomes, transcripts and recordings | Scoped per system, never broader than agreed |
| Never | Prices, contracts, calendars and records outside the agreed scope | Hard boundary, not a setting |
| Credentials | Issued from your own account, revocable at any moment | You, at any time, without asking us |
| Sensitive fields | Can be marked internal-only — used on the call, never read aloud | You, field by field |
| Audit | A transcript and recording of every call, stored against the record | Retention set by your policy |
More detail on data handling, retention and sub-processors is in the privacy policy.
Don't see yours?
Most integrations are
configured, not built.
Tell us the system and what the agent would need to read and write. We will say honestly whether it is a configuration, a short build, or not currently practical — and roughly how long it would take.
FAQ
Frequently asked
questions
A live connection between Sono's voice agent and a system you already run. It lets the agent read your own data before it speaks — a reservation, an order, an overdue invoice, a campaign — and write the outcome back afterwards as a note, a ticket or a task. Without one, a voice agent can only recite a static script; with one, it can actually answer the question the caller asked.
Hostaway, for short-term rental and property management operators who want guest calls answered with each unit's own details, and lemlist, for outbound teams who want AI calls and WhatsApp attached to an email campaign. Beyond those two, Sono connects to most helpdesks, CRMs, billing and ERP systems through their APIs, and to anything else through webhooks or a thin connector.
Three ways, in order of preference. If the system has a public API, Sono talks to it directly. If it can send webhooks, Sono receives them and calls back. If neither is practical, a scheduled file exchange or an iPaaS hop through Zapier, Make or n8n works. Most connections are configured rather than built, and take days rather than months.
Read access is scoped to the fields you approve — typically enough to identify the caller and answer their question. Write access is deliberately narrow: notes, tickets, tasks, call outcomes and transcripts. Sono does not edit records it was not explicitly given permission to change, such as prices, calendars or contracts.
You do. Access is granted with credentials you issue from your own account and can revoke at any moment, which also means you can see exactly what Sono did and when. Sensitive fields can be marked internal-only, so the agent can act on a value without ever reading it aloud to a caller.
No. Lookups happen while the call is connecting and during the greeting, so the agent has the record before it needs it. If a system is slow or unreachable, Sono falls back to asking the caller directly rather than leaving dead air, and flags the failed lookup afterwards.
Connecting the accounts and mapping the fields is usually a day's work. What takes longer is agreeing the behaviour — which facts the agent may disclose, what it must escalate, what it says when it does not know. Most teams are live within one to two weeks including a review pass on real calls.
Often, yes. Tell us the system and what the agent would need to read and write, and we will say honestly whether it is a configuration, a short build, or not currently practical. Integrations that several customers ask for tend to become standard connectors.
Get started
See it answer using your own data
In a 30-minute demo we connect a sandbox account of whichever system matters most, place a call, and you hear the agent answer from your records and write the outcome back.
Book a Demo
Related industries and use cases
24/7 Customer Support
The use case most integrations serve — every call answered, day or night, with answers drawn from your own systems.
Learn moreOutbound Calls
Sono runs targeted outbound on the warm lists you already own – past customers, dormant leads, renewals, and service reminders.
Learn morePrivacy & Data Handling
How Sono handles your data: credentials you control, scoped access, and a transcript of every call.
Learn more