Quo, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Quo account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Phone & SMS
- Connects with a key
- 36 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Quo is
Quo, formerly OpenPhone, is a business phone platform for managing calls, messages, contacts, conversations, tasks, users, and webhooks.
You paste in a key from your own Quo account. It is kept encrypted, and you can withdraw it from inside Quo whenever you like.
One message in, the work done in Quo.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Quo. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Quo account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Quo
These are the ready-made tools your AI employee already has in Quo. It is not limited to them, but it never has to be taught these.
- Create ContactCreate a Quo contact with standard fields, optional custom fields, and external source metadata.
- Create TaskCreate a task linked to exactly one phone number, conversation, or activity.
- Create WebhookCreate one unified webhook subscription for selected Quo events and return its signing secret, which must be stored securely.
- Delete ContactPermanently delete one Quo contact by ID.
- Delete TaskPermanently delete one Quo task by ID.
- Delete WebhookPermanently delete one unified Quo webhook and revoke its signing secret.
- Get CallGet one call and its routing, participants, status, and timing details by ID.
- Get Call VoicemailGet voicemail processing status, transcript, duration, and recording URL for a Quo call. Returns a not-found error when the call has no voicemail.
- Get ContactGet one contact with default and custom fields by Quo contact ID.
- Get MessageGet one message by Quo message ID, including its content, related IDs, participants, delivery status, and timestamps.
- Get Phone NumberGet one Quo phone number and its assignments and restrictions by ID.
- Get TaskGet one task and its current links, assignee, due date, and completion state.
- Get UserGet one workspace user by Quo user ID.
- Get WebhookGet one unified Quo webhook by its numeric ID.
- Get Webhook DeliveryGet the payload and attempt details for one Quo webhook delivery event.
- List Call RecordingsList recording segments for a Quo call in chronological order.
- List CallsList calls between a Quo number and one external participant with optional user and creation-time filters. Returns one page and a cursor for the next.
- List Contact Custom FieldsList the workspace's contact custom-field definitions for constructing valid contact values.
- List ContactsList contacts, optionally filtered by external IDs or source, with stable-v1 phone and custom fields. Returns one page and a cursor for the next page.
- List ConversationsList inbox conversations with optional phone-number, user, creation-time, update-time, and inactive-state filters. Returns one page and a cursor for the next page.
- List MessagesList messages exchanged by a Quo phone number and one or more participants, optionally filtered by sender or creation time. Returns one page and a cursor for the next page.
- List Phone NumbersList Quo phone numbers and their assigned users, calling restrictions, and messaging restrictions.
- List TasksList workspace tasks with cursor-controlled pagination.
- List UsersList workspace users and return one cursor-controlled page.
- List Webhook DeliveriesList one page of delivery events for a unified Quo webhook, optionally filtered by status, event type, or dispatch time.
- List WebhooksList unified Quo webhooks across call, message, contact, task, and integration event families.
- Send MessageSend an irreversible text message from a Quo number to one or more recipients. This consumes messaging credits and may require carrier registration.
- Send Message and Mark Conversation DoneSend an irreversible text message from a Quo number and move the resulting inbox conversation to Done. This consumes messaging credits and may require carrier registration.
- Set Conversation StatusSet a Quo conversation to read, done, or open.
- Set Task AssigneeAssign or unassign a Quo user on a task.
- Set Task CompletionComplete or reopen a Quo task.
- Set Task Conversation LinkLink or unlink a Quo task and conversation.
- Set Task Due DateSet or remove a Quo task's due date.
- Update ContactPatch selected standard, custom, or source fields on an existing Quo contact. Omitted fields remain unchanged, while explicit null clears a field.
- Update TaskReplace both the title and description of an existing Quo task. Both fields are required because Quo treats this as a full textual update.
- Update WebhookPartially update a unified Quo webhook. Only explicitly supplied fields are changed; explicit null clears resource filters or the label where supported.
You stay the boss of your Quo account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Quo account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Quo is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Quo and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Quo
- Can an AI employee really work inside Quo?
- Yes. It signs in to your own Quo account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Quo?
- No. Nothing moves and nothing is replaced. Your records stay in Quo, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Quo account?
- You paste in a key from your own Quo account. It is kept encrypted, and you can withdraw it from inside Quo whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Quo?
- It has 36 ready-made tools in Quo today, among them Create Contact, Create Task and Create Webhook. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Quo and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Quo and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Quo?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Quo is written down with what it did and when.