Quo

Communication

Quo for AI agents. Managed auth, ready-made tools.

Send texts, review calls and transcripts, and manage contacts in Quo business phone numbers on behalf of each of your users.

About Quo

With the Quo connector, your agent works in each user’s own Quo workspace. It can send a text from a Quo number, read message threads, review recent calls and their transcripts, and look up or add contacts, using only the tools your project allows.

Quo, formerly OpenPhone, is a business phone system for calls, texts and shared numbers.

Tools

What your agent can do in Quo.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Quo connection.

  • List phone numbers

    Read
    quo_list_phone_numbers

    List the Quo numbers in the user's workspace.

  • List messages

    Read
    quo_list_messages

    Read the text messages exchanged with a contact on a Quo number.

  • Send a message

    Write
    quo_send_message

    Send a text message from one of the user's Quo numbers.

  • List calls

    Read
    quo_list_calls

    List recent calls with a contact on a Quo number.

  • Get a call transcript

    Read
    quo_get_call_transcript

    Get the transcript of a recorded call.

  • List contacts

    Read
    quo_list_contacts

    List the contacts in the user's workspace.

  • Create a contact

    Write
    quo_create_contact

    Add a new contact with a name, phone number and company.

Control

Limits you can set.

You decide what your agent may do in Quo, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read calls, messages and transcripts, and switch off quo_send_message so it can never text anyone.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example messages and contacts but not call transcripts. A call outside them is refused.

Get started

Connect Quo
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Quo

    Each end user authorizes their own Quo account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Quo account, once.
    const connection = await agent200
      .user("user_123")
      .connect("quo");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Quo tools

    Name the user, the model and the tools. The model decides which Quo tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Text Dana that her order is ready for pickup",
        tools: ["quo"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own Quo account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in Quo, such as reading messages, sending messages, reading calls or managing contacts. Users can revoke it later from their Quo account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Quo connector and how to use it.

Agent brief
Connector: Quo, through Agent200. In code: "quo".
What it does: Send texts, review calls and transcripts, and manage contacts in Quo business phone numbers on behalf of each of your users.
Page: https://www.agent200.com/connectors/quo/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Quo's own page, through the authorization link Agent200 returns. Never ask a user for a Quo password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: quo_list_phone_numbers, quo_list_messages, quo_list_calls, quo_get_call_transcript, quo_list_contacts. Write tools: quo_send_message, quo_create_contact. Name "quo" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/quo/framework/claude/
   https://www.agent200.com/connectors/quo/framework/chatgpt/
   https://www.agent200.com/connectors/quo/framework/claude-code/
   https://www.agent200.com/connectors/quo/framework/muse/
   https://www.agent200.com/connectors/quo/framework/grok-bot/
   https://www.agent200.com/connectors/quo/framework/openai-dots/
   https://www.agent200.com/connectors/quo/framework/claude-duet/
   https://www.agent200.com/connectors/quo/framework/hermes-agent/
   https://www.agent200.com/connectors/quo/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/quo.md

Guides

Use Quo with the AI you build on.

Step-by-step setup for Quo with a specific model, assistant or agent framework.

FAQ

Quo and Agent200, answered.

Who handles the Quo OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Quo.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Quo connection, never another user's. It cannot reach anything the user or Quo has not authorized.

Can I limit what my agent can do in Quo?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Discord

    Discord

    Read channels, post messages and start threads in the Discord servers your users connect.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
200 OK

Start with Quo.
Your agent does the rest.

Your users connect their own Quo accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)