10 live connectors · capabilities by plan

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.

Filter by plan0 tools in view

Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.

Capabilities

0 workflow areas in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.

Pill colors indicate API access scopeReadread-onlyRead + Writeread & writeLimitedpartial — see card heads-up
No capabilities in this plan tier for RingCentral. Show all capabilities.

Limits 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.

Ready to put Claude on your firm's tools?

Two minutes from creating an account to your first answer.