Wire the phone into the rest of your business.
There is no marketplace of one-click connectors here, and we are not going to pretend otherwise. What there is: an API that covers the whole product, a call-flow step that can call your own service while the phone is ringing, and booking built into the product rather than synced to it.
REST API
Everything the dashboard does, over HTTP. Read call records and usage, manage contacts and extensions, publish call flows, pull reports into whatever you already use.
- JSON in, JSON out, paginated lists
- Personal API keys: hashed at rest, shown once, revocable
- Row-level tenant isolation enforced at the database
Call your own service, mid-call
Drop an API-call step into any call flow. Look a caller up in your own system while the phone is still ringing, then route on what comes back — VIP to a person, past-due to billing, unknown to the receptionist.
- Reusable connection specs, so credentials live in one place
- Route on the response without writing a service
- Every call is logged and auditable
Calendar and appointments
Booking is built in rather than bolted on. The AI receptionist books into the same calendar your team works from, sends the confirmation, and lets the customer reschedule from a link.
- Services with their own durations and availability
- Email and text reminders in your business hours
- Customer reschedule and cancel links, with calendar invites
The hq command line
Script the parts you would otherwise click. Dump and restore call flows, manage devices and numbers, run a test call, script a rollout.
- Device-authorization login, an --org flag per command
- --json output that pipes into jq
- Same permissions as your console account
- Built from source today — ask and we will send you a build
Need it to talk to something specific?
Tell us what system and what you want to happen on a call. If it has an API, the call-flow step can usually reach it, and the founder will tell you straight if it cannot.