Key things to know
- SMS sends from ProPilot as usual, but attachments, voice notes, and calls happen in the Quo app - ProPilot opens Quo for you and syncs the activity back.
- Email is unchanged; it still uses ProPilot’s email system.
- Only admins can connect or disconnect Quo, and you need owner or admin access in the Quo workspace to generate the API key.
- SMS availability depends on your Quo account status (for example campaign approval and credits) - approval happens on Quo’s side.
Connect Quo
1
Open Phone Number settings
Go to Basic Setup > Phone Number (admins only) and
choose Connect with Quo. If you don’t have a Quo account yet, the panel links to Quo’s
signup.
2
Add your Quo API key
Generate an API key at my.quo.com/settings/api (requires Quo workspace owner or admin
access) and paste it - ProPilot validates it automatically, or click Validate key. The
key is stored securely and never shown back in the browser.
3
Pick a phone number and connect
Choose a number from your Quo workspace, then click Connect & register webhooks.
ProPilot automatically registers the webhooks it needs for messages and call events - no
manual setup in Quo.
What changes day to day
The 10% discount
While Quo stays connected, your ProPilot subscription gets 10% off, applied automatically to your bill. It is removed automatically when you disconnect, and pricing returns to standard.Disconnect, switch numbers, or rotate a key
- Disconnect - admins click Disconnect in the Phone Number panel. SMS reverts to an in-platform number and the 10% discount is removed.
- Switch numbers - disconnect, then reconnect and pick a different number from your Quo workspace.
- Rotate a leaked API key - there is no separate rotate button: disconnect, generate a new key in Quo, and reconnect with it. Webhooks are torn down and re-registered automatically.
Limitations
- No in-browser MMS or calling from ProPilot while on Quo - attachments, voice notes, and calls are handled in the Quo app, then synced back.
- Call transfers are unavailable on Quo. The Call Forwarding section in Your Profile only appears for organizations on an in-platform number.
- SMS availability depends on your Quo account status, such as campaign approval and available credits - if texts fail, check your standing in Quo first.
- Messages sent from the Quo app to numbers with no existing ProPilot conversation are not imported - only activity with saved contacts is mirrored.
- The Quo discount doesn’t stack with referral or promo codes.
Common questions
Can I send photos or make calls inside ProPilot with Quo?
Can I send photos or make calls inside ProPilot with Quo?
Not directly. Attachments and voice notes open an Open in Quo dialog, and calls show
Open Quo to call. You complete the action in Quo, and the activity (including call
recordings, transcripts, and AI summaries) syncs back into the ProPilot conversation.
Will texts I send from the Quo app show in ProPilot?
Will texts I send from the Quo app show in ProPilot?
Yes, for contacts that already have a conversation in ProPilot. Messages to unknown numbers
aren’t imported.
Can non-admins connect Quo?
Can non-admins connect Quo?
No. Connecting and disconnecting are admin-only in ProPilot, and the panel shows an “Admin
required” notice to other roles. You also need owner or admin access in the Quo workspace to
generate the API key.
My SMS through Quo stopped working. What should I check?
My SMS through Quo stopped working. What should I check?
Check your Quo account first: SMS depends on Quo’s campaign approval status and your
available credits. If your Quo standing is fine, disconnect and reconnect to refresh the
connection and webhooks.
What happens to my conversations if I disconnect?
What happens to my conversations if I disconnect?
Nothing is deleted - conversation history stays in ProPilot. New SMS simply goes back to
sending through an in-platform number, and the 10% discount is removed from your
subscription.
Is my Quo API key visible after connecting?
Is my Quo API key visible after connecting?
No. The key is stored securely and never exposed back to the browser. If you believe it
leaked, disconnect and reconnect with a freshly generated key.