Connect your calendar, CRM, and business tools. Your agent reads from them and writes to them — during the call, in real time.
Your receptionist takes a message, then manually enters it into your CRM. That's two jobs for one call.
Scheduling over the phone means checking one system while updating another.
When systems aren't connected, data falls through the cracks.
Every feature below is included on every plan. No add-ons, no feature gates.
Native OAuth integration — check availability, book, reschedule, cancel. All through conversation. Attach calendars to team members, locations, and services.
Signed webhooks fire on call lifecycle events (ended, message taken, callback requested, escalation, appointment booked, contact created). Wire to any system with one endpoint.
Read and write contacts, calls, knowledge, locations, bookings, and more. Anything the dashboard can do, a script can do.
The REST API and webhook primitives connect to thousands of apps — HubSpot, Salesforce, Slack, Notion, Google Sheets — through your favorite automation tool.
Any system with an HTTP API. Define the endpoint, parameters, and auth — your agent calls it during conversations, in real time.
Google Calendar connects with one OAuth click. For HubSpot, Salesforce, Slack, or any other tool, create an API key and webhook subscription on Settings, then wire up via Zapier or your own code. Custom in-call APIs configure from the dashboard.
An integration that fails mid-call is invisible unless someone is watching. Watchtower scores every call on resolution and accuracy, so a booking tool that started returning errors shows up as a scoring drop and a flagged call rather than as a month of quiet failures.
Your agent answers in a voice and name you choose, included on every plan. Hear the voices →
Connect Google Calendar with one OAuth click, or configure a custom in-call API
Generate an API key and subscribe to webhook events for external integrations
During a call, your agent uses integrations based on context — checks calendar, calls your API, takes action
Call lifecycle events POST to your webhook URLs — your agent pushes data out to your systems automatically
The caller never knows an API call happened — "I have an opening at 2:30 on Tuesday"
Google Calendar is the pre-built OAuth integration for phone booking. It connects in one click, and the agent then checks live availability, books, reschedules, and cancels through conversation. GitHub connects read-only for Allison Forge meetings, which is a separate surface from call handling. Everything else connects through two universal primitives instead of a per-vendor connector list: a REST API and signed outbound webhooks. That is a deliberate trade. You do not wait for us to build a HubSpot connector, because the webhook and API already reach it.
Yes, and this is the piece most phone systems do not have. You define an HTTP endpoint, its parameters, its authentication (API key, bearer token, or HTTP basic, held inline or in a shared credential set), and how to read the response. The agent then calls it mid-conversation and weaves the result into what it says next. Checking inventory before quoting a part, looking up an order by number, verifying a membership, and opening a ticket in your help desk are all the same mechanism.
Through the API and webhooks, either with your own code or through an automation tool. Subscribe to the events you care about (a call ending, a message taken, a callback requested, an escalation firing, an appointment booked, a new contact created) and Allison POSTs a signed payload to your endpoint. The quickest path for most teams is Zapier's catch-hook trigger, which then reaches any app they support. Make and n8n work the same way.
Every integration carries a context burden level that instructs the agent on how much to involve the caller. Ambient means use it silently, like recognizing a returning caller by phone number. Conversational means narrate it naturally. Requested means only fire it if the caller asks. Confirmed means ask permission before acting, which is the sensible default for anything that writes data. Verified means confirm identity first, for genuinely sensitive lookups. These shape the agent's behavior through its instructions rather than acting as a hard runtime lock, so treat Verified as a strong policy rather than an authentication boundary.
White-glove setup
Custom API integrations, webhooks, CRM sync, escalation design — designed, wired, and tested on live calls. Included with any plan. No setup fees.
Call Allison, describe your business, and she'll build your agent. Or sign up and configure it yourself.