Quo is a business phone service your brokerage may already text clients from, and connecting it lets BrokerPlus send and receive those texts. It lives on the Integrations settings page, in the card titled Quo, and only a brokerage admin can connect or repair it.
What the Quo Connection Does
Connecting Quo does not move a number here or replace a number claimed through BrokerPlus, which is covered in claim a phone number. It means a broker who texts a client from BrokerPlus sends from their own Quo line, and the client's reply arrives here beside the rest of that client's activity.
Calls are not part of this. Quo does not let another system place a call on your behalf, so calling stays in the Quo app. A brokerage that also has its own BrokerPlus number keeps using it: a number of your own always wins, and Quo answers for the people who have no BrokerPlus number.
The connection is workspace-wide: one API key connects your whole Quo workspace, not one person's line, and only one connection can exist for the brokerage at a time. Each teammate texts from the line assigned to them in Quo, matched by the email address they sign in with on both sides. Someone with no line assigned in Quo texts from the team's line instead.
Connect With an API Key
Create an API key in Quo as a workspace owner or admin. Sending through the key draws on your Quo credits, so add credits there before your team starts texting.
- Open Integrations in settings and find the Quo card.
- Paste the API key.
- Choose Connect.
BrokerPlus verifies the key against your lines, then registers the callback that brings replies in.
Reading the Connection's Health
The status chip reads Connected when texts are subscribed. Setting Up means registration is still running. Needs Attention means replies would not arrive, and the card names the reason underneath, such as a key that has lost access.
The card also warns when Quo will not send to a country yet. A workspace that has not finished its registration for the United States can text Canadian numbers and not American ones, and a text to a restricted country fails at Quo rather than here, so the card says so before your team hits it.
Repair a Connection That Needs Attention
Retry Setup re-registers the callback using the key already on file, without asking you to paste it again. A rejected key is the one problem it cannot fix on its own: restore the key's access in Quo, or paste a replacement with Update API Key.
Disconnect and Clean Up
Disconnecting removes only the callback this connection owns, so a webhook someone set up in Quo by hand is never touched. If Quo does not confirm the removal, the card shows Cleanup Pending instead of clearing outright, and a fresh key cannot be connected until that cleanup succeeds through Retry Cleanup.
What to Do Next
- Make calls and send texts from a client's file.
- Connect Dialpad for calls and texts if your brokerage uses Dialpad instead.
- Manage every connection from Connect and Manage Integrations, the settings page this card lives on.