Quo (OpenPhone)

Quo — formerly OpenPhone — is a business phone service. Connect a Quo number to Auxx.ai and text messages sent to it arrive in the inbox you choose, alongside your email channels, so the same team answers them the same way.

Prerequisites

• A Quo workspace with at least one phone number.
• Owner or admin access to that workspace — only owners and admins can create an API key.
• An inbox in Auxx.ai for the conversations to land in.

1. Create a Quo API key

1. Sign in to the Quo dashboard.
2. Go to Workspace Settings → API.
3. Create a new key and give it a name you'll recognize later, e.g. "Auxx.ai".
4. Copy the key. Quo shows it once — if you lose it, create another.

2. Connect Quo in Auxx.ai

1. Go to Settings → Channels.
2. Click New Channel and select Quo.
3. Paste your API key.
4. Pick the phone number this channel should answer, from the list of numbers on your workspace.
5. Choose the inbox its conversations route into.

That's the whole setup. You don't need to configure anything back in the Quo dashboard:

There is no webhook URL to paste and no signing secret to copy across.

One connection, one channel per number

Your API key represents the workspace, not a single number. So you paste it once:

• The connection is your Quo workspace. Connect it a single time.
• A channel is one phone number from that workspace, routed into one inbox.

To answer a second number, add another channel against the connection you already have — go to Settings → Channels → New Channel → Quo and pick the next number. You don't need a second API key, and each number can route into a different inbox if you want sales and support kept apart.

Check that your number is allowed to send

Quo restricts messaging per number and per region, and a restricted number will fail at send time — the message simply won't go out. This catches people off guard, because the number receives texts perfectly well.

On one real workspace we tested, of three numbers only the toll-free line was cleared to send SMS to US recipients; the other two were restricted.

Before you rely on a number for replies, open it in the Quo dashboard and confirm messaging is unrestricted for the regions you text. If it isn't, Quo's own registration process is what lifts it — it isn't something Auxx.ai can change.

What history you get

Connecting a channel brings across recent conversations for that number, most recently active first, so a thread someone replied to yesterday is there even if it started a year ago. It is a bounded catch-up, not a complete archive — very old, long-dormant conversations may not be included.

Two things never come across, because Quo's API doesn't return them for past messages:

• Attachments on picture messages (MMS). A message that was nothing but an image backfills with a placeholder and no file.
• Voicemail and call recordings.

This isn't a limit we can work around — Quo only ever hands out media at the moment a message arrives, never afterwards. Anything from before you connected stays viewable in the Quo dashboard.

How SMS differs from email

Texting isn't email, and the composer changes to match. On a Quo channel you won't see:

Incoming picture messages arrive as messages with any text they carried, but the image itself isn't stored in Auxx.ai yet — open the conversation in Quo to see it.

Troubleshooting

Next steps