Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Voicemails, calls, SMS — read by Claude across your whole firm
Cohesive360 exposes RingCentral RingEX to Claude through 20 tools across 7 capability areas — call log, voicemails (with AI transcripts on the standard plan tier), SMS, Team Messaging (inter-office chats), fax, and contacts. Connect once as a RingCentral admin and Claude reads firm-wide data. Outbound SMS, fax, and team-message sends always confirm with you before firing.
Voicemail triage in one Claude prompt
Pull every unread voicemail across your firm, read the auto-generated transcripts, and surface the 3 that need urgent callbacks — in seconds. Toni gets 50+ calls a day; Claude reads them all without skipping the one that matters.
Firm-wide visibility for admins
When the connecting user is a RingCentral admin, Claude sees every user's calls, voicemails, and SMS — not just one line. "Who in the firm called Progressive Insurance last week" becomes a one-prompt question. Non-admins automatically see only their own data.
Works on standard RingEX
Voicemail transcripts come from RingCentral's basic voicemail-to-text (included in most plans) — not a premium add-on. No RingSense AI subscription required for the core triage workflow. If your firm does subscribe to RingSense, the connector automatically picks up the higher-quality transcripts too.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
7 workflow areas in Solo plan. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Confirm which user/extension is connected, and discover the firm's RingEX seats. Both tools surface the internal extension IDs that other tools need for cross-user queries (admins only).
Confirm which user/extension is connected, and discover the firm's RingEX seats. Both tools surface the internal extension IDs that other tools need for cross-user queries (admins only).
What you can ask Claude
- “Who am I connected to in RingCentral”
- “List the firm's RingEX extensions — just real users, not IVR menus”
- “Which seats are active in our RingCentral account, and which are disabled”
Underlying tools (2)
who_am_ilist_extensionsRead inbound, outbound, and missed calls — your own line by default, a specific colleague's line, or firm-wide if you're a RingCentral admin. Each call includes recording metadata + AI-transcript availability when RingSense is subscribed.
Read inbound, outbound, and missed calls — your own line by default, a specific colleague's line, or firm-wide if you're a RingCentral admin. Each call includes recording metadata + AI-transcript availability when RingSense is subscribed.
What you can ask Claude
- “Show me my last 5 RingCentral calls”
- “List all calls across the firm in the past 24 hours, grouped by user”
- “Show Toni's calls yesterday — extension 103”
- “Pull the full details of call ID 12345 and summarise the recording transcript”
- “Show me every call we had with Progressive Insurance this month”
Underlying tools (3)
list_call_logget_call_log_recordget_call_recording_metadataList voicemails with read/unread status, pull individual messages with the AI-generated transcript text, or batch-fetch multiple voicemails in parallel for the 'summarise my whole inbox' workflow. Transcript source is RingCentral's basic voicemail-to-text (included in most plans) with RingSense AI fallback when subscribed.
List voicemails with read/unread status, pull individual messages with the AI-generated transcript text, or batch-fetch multiple voicemails in parallel for the 'summarise my whole inbox' workflow. Transcript source is RingCentral's basic voicemail-to-text (included in most plans) with RingSense AI fallback when subscribed.
What you can ask Claude
- “Any unread voicemails on my line”
- “Pull the AI transcripts for all 6 of Toni's unread voicemails and flag urgent callbacks”
- “Read me the voicemail from Ezequiel Guevara, message ID 3146344973012”
- “Mark voicemail ID 3146...123 as read”
Underlying tools (4)
list_voicemailsget_voicemailget_voicemails_bulkmark_voicemail_readList SMS conversation threads grouped by phone-number pair, drill into a specific thread, send outbound SMS. The send tool always asks Claude to confirm with you before firing — every SMS is billed against your RC plan's segment quota, so we never auto-send.
List SMS conversation threads grouped by phone-number pair, drill into a specific thread, send outbound SMS. The send tool always asks Claude to confirm with you before firing — every SMS is billed against your RC plan's segment quota, so we never auto-send.
What you can ask Claude
- “List my SMS conversations from the past 30 days”
- “Show me every SMS with this client's phone number this week”
- “Reconstruct the SMS thread between me and +1-516-912-5429”
- “Send a text from my RC number to +1-555-... saying 'Confirming our 3pm tomorrow.'”
Underlying tools (3)
list_sms_conversationslist_sms_messagessend_smsRead and post in RingCentral's internal chat system (formerly Glip, now 'Team Messaging') — direct messages, group chats, and team channels. Send-message is gated by the same confirm-before-firing pattern as SMS/fax.
Read and post in RingCentral's internal chat system (formerly Glip, now 'Team Messaging') — direct messages, group chats, and team channels. Send-message is gated by the same confirm-before-firing pattern as SMS/fax.
What you can ask Claude
- “How many inter-office messages did I send yesterday and to whom”
- “List my Team Messaging chats from the past week”
- “Search team messages for 'client Smith' across the last 30 days”
- “Show me the last 20 posts in our litigation team channel”
- “Post to our intake channel: 'new client lead from Joel — check Voicemail #4'”
Underlying tools (7)
list_team_chatsget_team_chatlist_team_postsget_team_postlist_teamssearch_team_messagessend_team_messageSend outbound faxes via your RC fax number — accepts either a PDF URL Claude can reach, or a base64-encoded document. Same confirm-before-send behaviour as SMS; fax pages are billed against your RC plan.
Send outbound faxes via your RC fax number — accepts either a PDF URL Claude can reach, or a base64-encoded document. Same confirm-before-send behaviour as SMS; fax pages are billed against your RC plan.
What you can ask Claude
- “Fax the medical records summary attached to case 50820 to (212) 555-0143”
- “Send a cover letter to the opposing counsel's fax line — use the document I just shared”
Underlying tools (1)
send_faxSearch the connected user's personal RC contacts. Lighter-weight than the firm-wide extensions list — useful when looking up a specific client's phone number before sending SMS or initiating a callback.
Search the connected user's personal RC contacts. Lighter-weight than the firm-wide extensions list — useful when looking up a specific client's phone number before sending SMS or initiating a callback.
What you can ask Claude
- “Look up Joel in my RC contacts”
- “What number do I have stored for Adam Yusupov”
Underlying tools (1)
list_contactsLimits and roadmap
What the RingCentralconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- MMS image attachments. RC's API lists MMS attachments on SMS messages but our connector doesn't currently fetch their content. Photos and screenshots clients send to your line via MMS show up as 'image attached' — to view, open the thread in the RingCentral app. Phase 2 will add a dedicated download tool.
- Outbound voice calls (RingOut). Initiating an outbound call from a Claude prompt — 'call this number' — isn't wired yet. RC has the API (the RingOut scope) and our adapter is structured for it; we just haven't shipped the tool. Coming in Phase 2.
- Webhook push notifications. Today the connector polls — Claude only knows about a new voicemail when you ask. RC supports webhook subscriptions for real-time new-message events. Phase 2 will subscribe Cohesive360 to those.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Call recordings predating RingSense activation. Recordings made before a user enabled their per-user AI toggle in Settings → AI don't have transcripts attached, and RC doesn't retroactively transcribe them. Only forward-going recordings get the AI treatment.
- Cross-firm or non-RingEX accounts. Each customer's connector is wired to their own RingCentral account via a Private app. If you switch firms or RingCentral providers, you re-run the OAuth setup with the new account. Phase 3 — ISV partner status — lets any customer connect with a single click.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Permissions inherited from RingCentral
We don't simulate authorisation on top of RC. If you're a RingCentral admin you see firm-wide; if you're not, you see only your own data. RC enforces server-side per request — we just pass through. Your existing RC role structure is the source of truth.
Encrypted refresh-token vault
RingCentral OAuth tokens (access + refresh) are encrypted at rest with AES-256-GCM; master key in Azure Key Vault, AAD-bound to your user ID so a stolen blob can't be decrypted under another account. Plaintext exists only briefly in memory during a tool call.
Writes require user confirmation
Outbound SMS and fax tools instruct Claude to confirm with you before firing. Every send is billed against your RC plan's segment/page quota, so we never auto-send. Voicemail mark-as-read is a state flip on RC's side, surfaced in Claude's tool call so you can see when it happens.
Disconnect wipes the token
Clicking Disconnect on the credentials page removes the encrypted token row from our database immediately. Optionally revoke server-side from RingCentral's admin portal for a full break. Your RC account, recordings, and call history are never touched.
Transcript quality flagged honestly
RC's basic voicemail-to-text is good for triage but garbled on phone numbers and proper nouns. The connector and Claude both flag this — every transcript Claude returns includes a reminder to verify callback numbers from caller-ID before dialling.
What RingCentral via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your RingCentraltenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.