3.1k Downloads
Overview
Integrates with the Quo (OpenPhone-style) business phone system via the Maton gateway, enabling managed OAuth access to send SMS, list and inspect calls, manage contacts and conversations, and retrieve call recordings, summaries, transcripts, and voicemails.
Key Advantages
1.Full coverage of core business-telephony primitives: phone numbers, users, messages, calls, recordings, voicemail, contacts, and conversations.
2.Managed OAuth via Maton: the skill only needs a Maton API key, while the gateway injects Quo OAuth tokens automatically.
3.Clear, detailed HTTP API documentation with concrete Python and JavaScript examples for common operations (list numbers, send SMS, etc.).
4.Supports powerful querying and pagination across messages, calls, contacts, and conversations (time filters, user filters, participants, etc.).
5.Explicit error and troubleshooting guidance (status codes, rate limiting, API key issues, invalid app path, curl quirks).
Use Cases
- Sending outbound SMS messages from a business phone number when the user explicitly requests it (e.g., appointment reminders, quick follow-ups).
- Listing and inspecting recent SMS threads or single messages between a business number and a given customer number for context during support or sales workflows.
- Retrieving call logs for a specified phone number and participant, including durations, statuses, and timestamps for reporting or QA workflows.
- Fetching call recordings, summaries, transcripts, or voicemail associated with a call to power conversation analysis, QA review, or CRM note enrichment.
- Managing contacts: listing, creating, updating, and deleting Quo contacts and enriching them with company, role, phone, and email data from other systems or user input. - Synchronizing external IDs or
Evaluation Scores
8.0
/ 10
Reliability
7.5
Functionality
9.0
Usability
8.3
Safety
7.0
Performance
8.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.0/103/19/2026▼
OS: linux-x64LLM: arcee-ai/trinity-large-preview
**Judgement:** Quo is a strong, focused skill for interacting with a Quo/OpenPhone-style business phone system through the Maton gateway. It is well-suited for production-style workflows that need SMS, call logs, recordings, and contact management, assuming a valid Maton API key and properly configured Quo OAuth connection.
**What it’s good at**
- Sending SMS messages from business numbers when a user explicitly asks to do so.
- Browsing and filtering messages, calls, and conversations by number, participants, user, and time range.
- Accessing rich call artifacts: recordings, summaries, transcripts, and voicemails.
- Managing contacts (CRUD + custom fields) and linking them to conversations.
- Handling pagination and query parameters for larger datasets.
**Key risks / cautions**
- **Irreversible actions and cost:** Sending SMS is billable and cannot be undone; always require explicit user intent and clarify that charges may apply ($0.01/segment US/CA, higher internationally).
- **PII exposure:** Phone numbers, emails, transcripts, and recordings are sensitive. Avoid unnecessary retrieval, storage, or display; only fetch what is needed and respect user privacy constraints.
- **Authentication fragility:** Requires a valid `MATON_API_KEY` and an active Quo OAuth connection; failures may appear as 401/403 or connection errors.
- **Rate limiting and errors:** Must handle 429 and 5xx responses gracefully and avoid tight polling or bulk operations without backoff.
**Recommended scenarios**
- Conversational agents acting as a front-end to a sales or support phone system (checking last messages/calls with a given customer, retrieving transcripts, etc.).
- CRM-style workflows where the assistant keeps Quo contacts and conversations in sync with other tools.
- Operators who want to ask, “Show me recent calls/messages with this number/contact” or “Send this message from our main line,” and have the assistant perform those actions via Quo.
Use Quo specifically for Quo/OpenPhone operations; for unrelated third-party APIs, prefer the `api-gateway` skill as per the author’s guidance.
Comments (0)
No comments yet. Be the first!