Voice & chat agents
Outbound and inbound calls, and chat on the channels your clients already use — qualification, booking, first-line answers, with a clean handoff to a person.
Scope a buildWhat this is
A voice or chat agent handles the front of the conversation: it works a short script, answers the questions it has answered before, books against a real calendar, and writes the outcome where your team can see it. The moment the conversation goes off-script, turns hostile, or asks for a human, it hands over — with the context, not a cold transfer. It runs on real telephony and real messaging, not a widget that only works on your own site.
What you get
- Inbound and/or outbound, over phone (SIP) and chat (WhatsApp, SMS, web)
- A qualification script you approve, with clear escalation rules
- Booking against your real calendar; outcomes written to your CRM
- Near-conversational latency so it doesn’t feel like an IVR
- Two weeks of monitoring real conversations after launch, and tuning
How we start
We scope one flow — usually inbound qualification or outbound follow-up — agree the script and the escalation rules, and run it as a limited pilot before it touches all your traffic. See the interactive AI Caller demo for how one sounds.
See how this plays out for one industry: AI agents for property management.
Who owns the code?
You do, completely. The agent logic, the call flow and the integrations are handed over as code in your repository. The underlying telephony and voice vendors (VAPI, ElevenLabs, or equivalents) are accounts in your name — we configure them, we don't resell access to them.
How is our data handled?
Call transcripts and outcomes are written to your CRM or database, not stored on infrastructure we control long-term. Vendor accounts run under API tiers with training disabled where available, and access to logs is least-privilege, revoked at handover unless you keep support running.
How long does it take?
A single flow — inbound qualification or outbound follow-up — usually takes two to four weeks: script and escalation rules agreed first, then a limited pilot before it touches all your traffic. Multi-flow or multi-language builds take longer, scoped after the first call.
What happens when the conversation goes off-script?
It hands over — with the context attached, not a cold transfer. Anything outside the agreed script, a request for a human, low confidence in intent, or a hostile caller all route to a person immediately. The agent never improvises on the parts that matter.
Have something like this?
Tell us the workflowWondering who owns the code or where your data goes? See how we work.