Recognise
The caller's number is matched against the client's contacts, members, patients or requesters before the agent says hello, so a known caller is greeted by name and the agent already knows their history.
Integrations
Works inside the tools your clients already run.
The agent does not take a message and leave it for someone to type up. It recognises the caller from the client's own software, reads what is already there, and writes the booking, the ticket or the job back into it while the caller is still on the line. Every connection below is built and run by the platform, straight to that system.
At a glance
Every connection, and where it stands
Available means the connection is built and running and can be switched on for a client. Planned means it is on the roadmap and not connected yet, and a logo never implies more than the word under it.
Autotask PSAAvailable
FreshserviceAvailable
HubSpotAvailable
GoHighLevelAvailable
PipedriveAvailable
TrelloAvailable
Zoho CRMPlanned
ActiveCampaignPlanned
Capsule CRMPlanned
Close CRMPlanned
monday CRMPlanned
FergusAvailable
Workshop SoftwareAvailable
MechanicDeskAvailable
SimproAvailable
iTradeAvailable
ServiceM8Available
TradifyAvailable
JobberPlanned
WorkflowMaxPlanned
Google CalendarAvailable
Microsoft 365Available
Apple CalendarAvailable
CalendlyAvailable
ZenotiAvailable
Square AppointmentsAvailable
SuperSaaSPlanned
SimplyBook.mePlanned
RezdyPlanned
XeroAvailable
MYOBAvailable
WindcaveAvailable
ClinikoAvailable
GymMasterAvailable
ClubwarePlanned
NookalPlanned
SplosePlanned
HalaxyPlanned
Facebook Lead AdsAvailable
LinkedIn Lead SyncAvailable
Google Ads lead formsPlanned
JotformPlanned
Gravity FormsPlanned
WPFormsPlanned
Webflow FormsPlanned
ZapierAvailable
MakePlanned
n8nPlanned
TaxiCallerAvailable
Rex SoftwareAvailable
Logos belong to their owners and mark the system the agent connects to; none of them is an endorsement. Platform-side channels such as website chat, the texting agent and the platform diary, and systems without a square icon of their own, are listed by name in the tables below.
How to read these tables
What the agent does with each system
Each table says what the agent reads and writes in that system today. A Planned row says plainly that the connection is on the roadmap, and until it is live the agent is never allowed to promise it to a caller.
Read
Open tickets, the next free appointment, what an account owes, which technician is free. The agent reads the live system, not a copy of it, and answers from what is actually there.
Write
The ticket, the job, the booking or the lead is created in the client's system during the call, with the transcript and a summary attached, and a note of the call on every record it touched.
PSA and ITSM for IT providers
A phone line that behaves like a member of your service desk
For an MSP the first use of the platform is usually its own desk. A client rings, the agent knows who they are and what is already open, and the ticket exists before anyone on your team has looked up from their screen.
Reads the open tickets before hello
When a call lands, the agent matches the caller's number to a requester, contact or company in the desk. If there is a match, it pulls that person's open tickets before it speaks. So the greeting is not “how can I help”, it is “hello Sam, is this about the printer ticket from this morning?”. A caller who already has a ticket is updated, not duplicated.
Status, updates and new tickets
The caller can ask where their ticket is at and get the real status. Anything they add goes onto the ticket as an internal or private note, so your engineers see it and the caller does not get a stray public reply. A new issue becomes a new ticket, created under the right contact and company with the source marked as a phone call, in the queue your desk already works. On Autotask PSA the agent can tick the checklist steps it has covered with the caller. On Freshservice it can read a solution article back to the caller when the answer is already written down.
Every call noted
At the end of the call a summary is written onto every ticket the agent touched, so the next engineer to open it knows what was said, what was promised and what the caller was told. Where the desk is set up for MSPs, each of your client workspaces can have its own line.
What is not written back
Both connections are built against the vendor APIs. Service level status and time entries are not yet written back. The briefing will show both connections to you on a desk rather than on a slide.
| Integration | What the agent does with it | Status |
|---|---|---|
| Autotask PSA | Matches the contact or company by number; reads open tickets and status; adds an Internal Only note with ticked checklist steps; creates a ticket under the contact and company; reads a help article; writes a call note on every ticket touched. A daily phone index per tenant keeps recognition fast. | Available |
| Freshservice | Matches the requester by number and greets them by name; reads their open tickets before hello; answers “my tickets” and ticket status; updates as a private note; creates a ticket with source Phone; reads a solution article; notes the call summary on every ticket touched. Supports the MSP edition, one line per client workspace. | Available |
CRM and sales
Every call becomes a contact with a transcript on it
| Integration | What the agent does with it | Status |
|---|---|---|
| HubSpot | Recognises the caller; creates or updates the contact; logs the transcript, summary and the answers the caller gave; finds a contact by email for meetings. | Available |
| GoHighLevel | Recognises the caller; creates or updates the contact; logs the transcript, summary and answers. Guided setup page with one-button connect. A workflow can trigger a call and the result is posted back into the workflow. | Available |
| Pipedrive | Recognises the caller; creates or updates the person; logs the transcript, summary and answers; finds a contact by email for meetings. | Available |
| Trello | A card per lead, with the summary and transcript on it. | Available |
| Zoho CRM | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| ActiveCampaign | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Freshsales | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Capsule CRM | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Close CRM | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| monday CRM | On the roadmap: recognising the caller and logging the call on the contact, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
Every enquiry, whichever channel it came in on, also lands in the platform's own leads list with the whole call and text history for that number beside it. The CRM connection is on top of that, not instead of it.
Job management and field service
The job is in the system before the technician is back
| Integration | What the agent does with it | Status |
|---|---|---|
| Fergus | Looks the caller up; files an enquiry, a quote request or a diary booking according to a one-question rule the business sets; imports contacts; files photos the caller sends onto the job; “Sign in with Fergus” account creation. Proven on paying trade businesses, writing into live accounts. | Available |
| Workshop Software | Books into the real workshop diary by day, with the rego and the symptom; imports vehicles so a rego finds the customer. | Available |
| MechanicDesk | Puts booking requests into the workshop diary using the business's own job types. | Available |
| Simpro | Looks the caller up from commercial accounts; creates a lead with customer and site; takes quote requests; schedules against a free technician; imports contacts. | Available |
| iTrade | Looks the caller up; lodges a job with notes; takes a visit request. | Available |
| ServiceM8 | Recognises the caller; looks the job up; lodges the next job with the address; imports contacts. | Available |
| Tradify | One way only: the enquiry is emailed into the Tradify inbox. Nothing is read back, so no caller lookup and no booking. | Available |
| Jobber | On the roadmap: caller lookup and the enquiry or job lodged in the system, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| WorkflowMax | On the roadmap: caller lookup and the enquiry or job lodged in the system, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
Calendars and bookings
Reads the real diary, writes the real appointment
| Integration | What the agent does with it | Status |
|---|---|---|
| Google Calendar | Reads the real diary and writes the appointment with the caller on it. Two permissions only, and the business ticks which calendars the agent may see. | Available |
| Microsoft 365 / Outlook | Reads the real diary and writes the appointment with the caller on it. Two permissions only, calendars ticked individually. | Available |
| Apple Calendar | Reads the real diary and writes the appointment with the caller on it. Two permissions only, calendars ticked individually. | Available |
| Platform diary | For a business with no calendar of its own: a diary per staff member, held on the platform. | Available |
| Calendly | Checks availability and texts the caller a single-use booking link while they are still on the call. | Available |
| Zenoti | Live availability by therapist and room; books with the treatment attached. | Available |
| Square Appointments | Takes services, team and hours from Square. Australia. | Available |
| Cal.com | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Acuity Scheduling | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| SuperSaaS | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| SimplyBook.me | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Microsoft Bookings | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Rezdy | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Bookeo | On the roadmap: reading free time and writing the appointment, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
A connected calendar is read as busy or free and next free time only. The agent is never shown the contents of other events.
Accounting
Knows who is ringing and what they owe
| Integration | What the agent does with it | Status |
|---|---|---|
| Xero | Recognises the caller from contacts; answers what they owe; makes overdue-invoice reminder calls and leaves a note on the invoice; imports contacts. Nothing else in Xero is ever created, edited or voided. | Available |
| MYOB | Knows who is ringing and what they owe; sends a copy of an invoice; chases past-due accounts. | Available |
Payments on the call
A secure link texted mid-call, the card typed on the gateway's own page
| Integration | What the agent does with it | Status |
|---|---|---|
| Windcave | The agent texts the caller a secure payment link during the call and the card is typed on the gateway's own page. The agent never takes a card number. | Available |
| Stripe | The same secure link, settled through the business's own Stripe account. The agent never takes a card number. | Available |
Gyms, clinics and studios
Members and patients, recognised and booked
| Integration | What the agent does with it | Status |
|---|---|---|
| Cliniko | Recognises the patient; answers “when am I booked in”; offers genuinely free times and the soonest practitioner; follows the clinic's treatment-to-practitioner rules; moves or cancels if the clinic switches that on; writes the call up as a communication note. Never reads a clinical note, appointment type or reason. Clinics are running their phones on it today. | Available |
| GymMaster | Recognises the member; reads class timetables and spaces; books or cancels; books resources such as a sauna or a reformer. | Available |
| Clubware | In development and on the roadmap. No connection exists yet, and the agent will not promise one to a caller. | Planned |
| Nookal | On the roadmap: recognising the patient and booking against real availability, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Splose | On the roadmap: recognising the patient and booking against real availability, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
| Halaxy | On the roadmap: recognising the patient and booking against real availability, built against the vendor's own API. Not connected yet, and the agent never promises it to a caller. | Planned |
Messaging channels
The same agent, the same knowledge, on text, email and chat
| Integration | What the agent does with it | Status |
|---|---|---|
| Website chat | One line of code on the client's site. Visitors type or press a button and talk, with the same knowledge as the phone agent, in the client's colours. No vendor branding in the snippet or the visible interface, and the key never reaches the browser. | Available |
| Slack | Call notifications posted into a channel, with plain-English routing per destination. Posts only, reads nothing back. | Available |
| Microsoft Teams | Call notifications posted into a channel through a Power Automate flow. Posts only, reads nothing back. | Available |
| Texting agent | Customers text the business's number and the same agent texts back, one question at a time, and hands the thread to a person the moment someone asks. Needs its own texting number. Does not book or look up a CRM over text. | Available |
| Email agent | The business forwards its enquiries inbox to an address the platform provides. Every email is read and answered, booked, handed to a person, or set aside with the reason shown. Money, complaints and legal matters always go to a person. | Available |
Marketing, ads and forms
A lead form submitted is a lead rung
| Integration | What the agent does with it | Status |
|---|---|---|
| Facebook Lead Ads | An enquiry arrives in the leads list the moment a form is submitted, and a lead automation can ring it back with the agent's own knowledge, inside the business's hours. | Available |
| LinkedIn Lead Sync | Lead form submissions arrive in the leads list and are handled the same way. | Available |
| Google Ads lead forms | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
| Typeform | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
| Jotform | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
| Gravity Forms | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
| WPForms | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
| Webflow Forms | On the roadmap: a form submission arriving in the leads list through the leads form endpoint, with a one-off field match. Not connected yet. | Planned |
Lead automations never ring outside the business's hours, never ring a do-not-call number, and ring once per enquiry with a daily cap.
Automation, APIs and webhooks
One API for everything the agent can do
| Integration | What the agent does with it | Status |
|---|---|---|
| REST API and webhooks | One API with one token carrying ticked abilities. Sections for identity, calls, agents, text messages, text replies, leads, speech, result webhooks, form endpoints and website booking. Published as an OpenAPI document for import into SwaggerHub or Postman. | Available |
| Zapier | Triggers and actions for anything not connected directly, across several thousand apps. | Available |
| Webhook notifications | Every call posted to any URL the business names, with plain-English routing per destination. | Available |
| Make | On the roadmap: triggers and actions for anything not connected directly. Not connected yet; the REST API and webhooks already cover the same ground for your own engineers. | Planned |
| n8n | On the roadmap: triggers and actions for anything not connected directly. Not connected yet; the REST API and webhooks already cover the same ground for your own engineers. | Planned |
Other
Dispatch and listings
| Integration | What the agent does with it | Status |
|---|---|---|
| TaxiCaller | Takes the pick-up address, gives an ETA and a fare estimate, dispatches, texts the booking number, texts driver-on-the-way and arrival, and cancels if the passenger rings back. | Available |
| Rex Software | Listing lines: a number and an agent per property, built from the agency's property package. | Available |
Bring your own
Connect your own software, or your client's
The named connections are the front door. Behind it is the same API the platform uses itself, so anything with an endpoint can be wired in by your own engineers.
REST API
One token, abilities ticked per integration. Calls, agents, leads, texts, speech, form endpoints and website booking. OpenAPI document served for import.
Webhooks
Result webhooks after every call and every text reply. Point them at your PSA, your billing or a function of your own and build on what comes back.
Website chat embed
One line of code puts the same agent on a client's website, in their colours, with an allowed-domain list and no vendor branding anywhere in it.
MCP servers
The platform ships MCP servers as well as the API. What they expose, and how a partner uses them, is covered in the briefing.
Something else
Do not see yours?
Most of what is listed here began as a client running something we had not connected yet. For software not on this page, a connection is built against the vendor's own API as a custom setup, and until it is live the agent is never allowed to promise the connection to a caller. Bring the system and the two or three things the agent would need to do in it, and the briefing will tell you whether it is a week's work or already half done.