Communication · Integration
Quo
Add Quo to your product for your customers, and give your AI agents governed access to it.
Quo is the business phone platform that was OpenPhone until late 2025, and the thing to settle before building on it is which half of it is writable. Messages are: your product can list conversations, read a thread and send a text from a number the customer owns, which is what most integrations are actually for. Calls are read: you get the call record, its recording once processing has finished, its transcript and its summary, but you do not place a call through the API. Webhooks cover both sides through separate subscriptions for message events and call events, and one detail catches people out, webhooks created in the app and webhooks created through the API are separate populations that cannot see each other. Messaging draws on prepaid credit, so a send fails outright when a customer's balance runs out rather than queueing, which is worth surfacing before it happens.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Quo workspace so texts go out from a number their contacts already recognise.
Read a conversation thread so the whole history with a contact is visible in your product, not only the part you sent.
Take call completed and recording completed events, so a summary is fetched once it exists rather than polled for.
Watch a customer's messaging credit and warn them before sends start failing for want of balance.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a reply in an existing thread and leaves the send to a person.
An agent sends an approved text from the customer's own number, with the conversation it landed in recorded.
An agent summarises what a call covered from its transcript and flags what was promised on it.
Example prompt
What was the last thing this customer texted us, and did the call afterwards resolve it?
Set up Quo in 4 steps
- 01Enable the Quo connector in your fastn dashboard.
- 02Have each customer create an API key on their own workspace, so texts send from a number they own.
- 03Choose the numbers your product sends from, then create your message and call webhooks through the API rather than in the app.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Quo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Quo integration without building it. Your customers connect their own Quo account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Quo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Quo connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
TwilioWorks well with
Aircall
RingCentralOften used alongside
Tools the same teams tend to run next to Quo, across other categories.
Calendly
Gong
Google Calendar
Chorus.aiQuo integration FAQ
How do I add a Quo integration to my product?
Enable the Quo connector in your fastn dashboard, then let each customer authenticate their own Quo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Quo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Quo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Quo account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Quo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent drafts a reply in an existing thread and leaves the send to a person.
Who maintains the Quo integration?
fastn does. When Quo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Quo account?
Yes. Every customer authorises their own Quo account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Quo integration?
A common starting point: let each customer connect their own Quo workspace so texts go out from a number their contacts already recognise. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Quo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Quo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Quo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.