Quo is a next-generation business phone system that helps teams engage customers, collaborate internally, and scale communication with AI — without losing the personal touch. Connecting Quo gives Claude access to your customer conversations across calls, text messages, and contacts. You can ask questions about those interactions to uncover patterns in what customers are saying and where opportunities may be lost. Claude can search, analyze, and summarize conversations to surface insights like Why are we losing deals? What do customers love about our service? What complaints show up most often?
update-contact or get-contact. Only firstName is required; all other fields are optional.activityId — it ties the task to exactly what the user is referring to. Use conversationId (CN…) when the user means the whole thread with a contact (also from fetch-* results). Use inboxPhoneNumber (E.164 or PN… ID, from list-inboxes) only when the task isn't about any specific call/message/thread.userId to return only calls handled by a specific team member (use list-users to look up user IDs). When participantPhoneNumber is omitted, the tool aggregates across participants discovered from the 100 most recent conversations. To page through additional results, use participantPhoneNumber + pageToken for a single participant, or conversationPageToken for older conversation batches.participantPhoneNumber is omitted, the tool aggregates across participants discovered from the 100 most recent conversations — cross-participant queries are therefore capped at 100 participants per call. For exhaustive analytical pulls, either narrow with participantPhoneNumber (enables full pagination via pageToken) or page through older batches with conversationPageToken.id | status | direction | participants | createdAt | duration; rows whose call has a voicemail are followed by an indented voicemail block (status, duration, recordingUrl, transcript). Voicemails are processed asynchronously — a voicemail with status 'in-progress' has null duration/transcript/recordingUrl, so retry in a few seconds. Missed calls where the caller hung up without leaving a message are still listed, just marked '(no voicemail)'. When participantPhoneNumber is omitted, the tool aggregates calls across all participants whose most recent activity falls within your createdAfter window — conversation discovery auto-pages to cover that window so older missed calls aren't dropped just because the inbox has had newer activity since. If createdAfter is not set, conversation discovery is capped at the 100 most recent conversations. For exhaustive single-contact pulls, use participantPhoneNumber + pageToken; if you hit the conversation-discovery safety cap, use conversationPageToken to continue.list-contacts first if you need to discover contact IDs.externalIds or sources. Returns a compact pipe-separated table (id | name | company | role | email | phone) and supports pagination via pageToken (1–50 results per page).from number for send-message or the inboxPhoneNumber for fetch-messages / fetch-call-transcripts.pageToken (1-100 results per page).id (US… format) to filter other tools like list-inboxes by user. Supports pagination via pageToken (1–50 results per page, max 50).send-message instead when you want to text one person, or to text several people privately without exposing them to each other (call send-message once per recipient). The from number must belong to the user's Quo workspace — use list-inboxes to discover available numbers. Recipients must be valid phone numbers in E.164 format (international supported). Note: Quo MCP is not HIPAA compliant; do not send protected health information.from number must belong to the user's Quo workspace — use list-inboxes to discover available numbers. Recipient must be a valid phone number in E.164 format (international supported). Note: Quo MCP is not HIPAA compliant; do not send protected health information.null for any field you want to clear. Use get-contact first if you need to inspect current values before updating.
