Frequently asked questions

Cohesive360 is a connector that lets Claude read and draft against the data already in your SmartAdvocate tenant. Your team can pull a case summary, dictate a note, prep a docket, draft tasks, log time, file documents, or update parties in plain English — and review every draft before it touches SmartAdvocate. Nothing new is added to SA; the workflows you run every day become a sentence instead of a tab-switch. See the full capability list.

From your Cohesive360 dashboard, copy the connector URL (https://smartadvocate.cohesive360.ai/api/mcp). In Claude (Desktop, web, or mobile), open Settings → Connectors → Add custom connector, paste the URL, click Connect, sign in to your Cohesive360 account when prompted, and click Approve. The same URL works on every Claude surface. No software to install.

Not yet — and this is an Anthropic limitation, not a Cohesive360 one.Voice mode on iOS and Android currently only invokes Claude's built-in integrations (web search, Google Calendar, Gmail, Google Docs). Custom connectors like Cohesive360 work in text chat on mobile, on claude.ai in a browser, and in Claude Desktop — but not through voice mode yet. If you ask by voice and Claude says it can't reach the connector, switch to text chat in the same app; the same question works there. We're tracking the Anthropic roadmap and will update this the moment voice mode picks up custom connectors.

Sign in to Claude on the new machine — the connector follows your Cohesive360 account. Your seat moves; the old device is gracefully signed out on its next check-in. Seat count doesn't increase because a seat is one SmartAdvocate username, not one machine.

Your license binds to the first SA tenant it activates against, so one license can't point at two tenants at once. If you need to move between test.smartadvocate.com and app.smartadvocate.com, email support@cohesive360.com and we'll reset the tenant binding for you.

Claude gets 136 tools across 20 capability areas: case search and overview, notes, status updates, tasks, calendar, phone calls, time tracking, documents (upload + download + search + categorise), parties (plaintiffs, defendants), counsel, courts and dockets and judges, insurance, vehicles, incidents and injuries, medical providers and visits and bills, liens and lien tracking, settlements and disbursements and checks and payments, referrals (incoming, outgoing, sub-out), the firm-wide contact directory, tags and custom fields, and staff assignments. The Features page has the full list with concrete example prompts for each area.

Three categories:

1. Pending SA support.Four documented SA endpoints currently fail with empty errors on most tenants (time-entry create, lien-history add, judge-role update, refer-out plaintiff scope). SA's UI works as the fallback for all four.
2. Not in SA's public API.Firm-wide task search, non-case calendar appointments, permanent deletes, defendant CRUD, and firm tag-library admin all live behind SA's UI rather than the documented JSON API, so the connector cannot reach them.
3. Roadmap. Email/SMS sending, report execution, and admin/billing/firm settings are technically possible but not shipped yet.

The Features page has the complete list grouped by reason.

Both.Claude can read every part of a case file and write to most of them — notes, tasks, calendar, phone calls, documents, plaintiffs, counsel, court records, dockets, insurance, vehicles, injuries, medical providers and visits and bills, settlements, disbursements, checks, payments, referrals, contacts, tags, and custom fields. Every write goes through your Cohesive360 user's SA permissions; if your SA account can't write tasks, neither can Claude. And every write is reviewable in the chat before it commits.

Yes. Drop a file into a Claude conversation and ask Claude to file it on a specific case with a category. For files up to 500 MB, use the /uploadpage on your dashboard to stage the file from your browser, then tell Claude to attach the upload token to a case. The connector handles the SA hot-folder XML sidecar pattern so SA's auto-import picks it up with your firm's category metadata.

We've put connector-level instructions in front of Claude that tell it to:

• Verify firm-wide before saying “not found” on a case-scoped read.
• Read every write back via the corresponding GET before claiming success.
• Warn upfront about the four known SA-side blockers.
• State capability gaps immediately rather than enumerating cases for 10+ steps.
• Stop after two consecutive errors instead of looping.

These guardrails reduce — but don't eliminate — hallucination. Treat every draft as a draft. Review before saving anything that affects a deadline, a client communication, or a matter already in motion.

First place to check: was it written to the right scope? For example, create_contact adds a row to your firm-wide directory but does not attach the contact to a specific case — to put a contact on case X, the right tool is add_plaintiff, add_counsel, add_medical_provider, etc. Our connector instructions tell Claude to confirm intent before calling create_contact and to read every write back; if those guardrails fail, the contact still exists in your firm directory, and you can find it via search_contacts. If something genuinely seems missing, email support@cohesive360.com — we keep audit logs and can show you exactly which tool was called with which arguments.

Case data stays in SmartAdvocate.Every tool call fetches the data you asked for just-in-time from your SA tenant, hands it to Claude so you can read or draft against it, and discards the response after. We don't keep a copy of your cases, notes, tasks, contacts, or documents on our servers.

Yes — but encrypted.SmartAdvocate's API takes username and password (there's no OAuth or service-account path today), so our server has to authenticate to SA on your behalf when Claude on the web or mobile calls the connector. We hold a decryptable copy of your password, encrypted with AES-256-GCM, with the master key in Azure Key Vaultand the ciphertext bound to your user ID so a stolen blob can't be decrypted under another account. Plaintext only exists in server memory during an authenticate request to SA; never logged, never echoed in a response, never written to disk. See the privacy policy for the full crypto details.

Yes. Our original stdio installruns a local Node process inside Claude Desktop and reads credentials from a file on your computer — your SA password never transits our servers. The trade-off: Claude Desktop only (no web, no mobile), and end users have to keep the install up to date. You'll find it on your dashboard under Advanced — legacy stdio install.

Account metadata (your email, a scrypt-hashed Cohesive360 password, your firm's name, your acceptance of the terms and AI disclaimer), Stripe subscription state, the license key, OAuth tokens issued for connectors, and the encrypted SA credential vault described above. Not case data. Not Claude's responses. The privacy policy has the exhaustive list.

When you stage a file via the /upload page (for files larger than what fits inline in a Claude conversation), the browser uploads directly to a temporary Azure Blob Storagecontainer in the same Azure region as the connector. The connector retrieves it, hands it to SA's hot-folder, and the blob is deleted immediately on success. A lifecycle rule deletes any leftover blob after 1 hour even on failure, and a daily janitor cron sweeps any stragglers. The blob is encrypted at rest. We don't reuse upload tokens across users, and the connector verifies your user ID before redeeming a token.

Not today. SmartAdvocate's CaseSyncAPI authenticates with username and password only, the same endpoint their internal web app uses. We've checked 13 standard OAuth and OIDC endpoints and they all return 404. If SmartAdvocate adds OAuth, we'll wire it in within a week — that would let us stop holding passwords entirely.

We sign Business Associate Agreements (BAAs)on request for firms that handle PHI. Anthropic also offers a BAA for Claude on enterprise plans — both BAAs are required if PHI flows through chat. For other compliance frameworks (state bar requirements, ABA Model Rules on technology competence, your own client engagement letters), the connector inherits the same boundaries as your SA user — what your SA login can do, Claude can do; what it can't, Claude can't. Email security@cohesive360.com for the full security questionnaire and our SOC 2 readiness status.

Treat every draft as a draft. Claude can misread a note, misinterpret a date, draft a task against the wrong case, or summarise something incorrectly. The connector is designed so you always review before saving — particularly for anything that affects a deadline, a client communication, or a matter already in motion. Cohesive360 is a tool that sits beside your professional judgment; it is not a substitute for it.

At peak load — month-end reporting, big exports, long-running operations — the SA server can return HTTP 429 or 503. The connector:

• Respects the Retry-After header when SA sends one.
• Falls back to exponential backoff (0.5s → 1s → 2s) if no header is given.
• Retries up to 3 attempts, then surfaces a clear “try again in a minute” message.
• Doesn't retry on other 4xx errors — those indicate your request is the problem, not SA's load.

Published rate-limit numbers aren't available from SA. Conservative heuristic: under ~60 tool calls per minute from a single seat.

We built a credential circuit breaker for exactly this. If SA rejects your credentials once, the connector remembers the fingerprint of the bad credentials and refuses to retry until you update any part of your username, password, or URL. Before this protection existed, a stale password could cause every tool call to retry until SA locked the account. Now it trips the breaker on the first rejection and tells you what to fix.

No.The connector authenticates as your SmartAdvocate user and inherits that user's role and permissions. If your SA account can't write tasks, neither can Claude through the connector. The same boundary that limits what you can do by clicking in SA limits what Claude can do on your behalf.

No. The connector recognises the four known SA-side blockers (time-entry create, lien-history add, judge-role update, refer-out plaintiff scope) and tells you upfront before attempting them, including the SA UI workflow that works. For other endpoint failures, the connector reports the specific HTTP status and SA's response body and stops after two consecutive errors. We have open SA support tickets on each known blocker; the Features page tracks status.

Your Cohesive360 subscription is for access to the connector itself — the bridge that lets Claude read and write to your SmartAdvocate tenant. That includes:

• A monthly tool-call allowance based on your plan (5,000 on Solo, 25,000 per seat on Team, unlimited on Enterprise)
• The encrypted SA credential vault
• The OAuth-protected MCP endpoint
• The dashboard for managing seats and credentials
• The upload-staging service for large files
• Technical support at the level of your plan
• Product updates as we ship new tools and capabilities

It does not include Claude itself, any Anthropic API usage, your SmartAdvocate license, or any other third-party platform you use to interact with Claude. Those are separate products with their own subscriptions and bills — see the next two questions.

No. Cohesive360 and Claude are two separate products from two different companies. Cohesive360 is a connector; you bring your own Claude. Your team needs an active Claude subscription (Claude.ai Free, Claude Pro, Claude Max, Claude Team, or Claude Enterprise) oran Anthropic API account to actually use the connector — Claude is the chat interface and the model that runs the conversation; we just give it the tools to act on your SA tenant. If you don't already have Claude, your firm signs up for it directly with Anthropic at claude.ai or anthropic.com. Two subscriptions, two bills, no overlap.

Anything that supports custom MCP connectors. As of today:

• Claude Desktop on macOS and Windows
• claude.ai in any modern browser
• Claude mobile apps in text chat (iOS and Android)
• Claude API if your firm builds custom workflows

All Claude paid tiers (Pro, Max, Team, Enterprise) support custom connectors. Voice mode on mobile does not yet — that's an Anthropic limitation we cannot work around. The free tier of claude.ai does not currently support custom connectors; that may change.

That depends on which Claude product your firm picks. Anthropic publishes current pricing at anthropic.com/pricing — Pro is currently around $20/user/month, Max around $100/user/month, Team and Enterprise pricing varies. The Claude API charges per token consumed. Whatever Anthropic charges goes directly to Anthropic; Cohesive360 has no visibility into and takes no cut from your Claude usage. We can't quote firm pricing on Claude because we don't sell it.

Three plans, all billed per-seat per-month via Stripe:

• Solo — single individual login. Live price on the Pricing page.
• Team — minimum 5 seats. Live price on the Pricing page.
• Enterprise — custom pricing scoped to your firm; annual contract. Email sales@cohesive360.com.

Both Solo and Team include a 14-day free trial and can be cancelled anytime. Volume pricing for 25+ Team seats — email sales for a quote.

Solo is for an individual attorney or paralegal — a single login, no team management, ~110 tools, 5,000 tool calls per month.
Team is for firms with 5+ users — invite teammates, manage seats, all 135 tools, 25,000 tool calls per seat per month.
Enterprise is for firms where governance and compliance are the conversation: SSO, BAA, SOC 2, data residency, audit retention, dedicated account manager, optional private-environment deployment. Tool-call limits are unlimited on Enterprise. The Pricing page has a side-by-side comparison.

A tool call is one action Claude takes against your SmartAdvocate tenant on your behalf— searching for a case, reading a note, drafting a task, uploading a document, logging a call. One question to Claude usually triggers 1–5 tool calls depending on how much context Claude needs to gather.

The monthly limits exist so plan pricing is honest: someone running 100,000 calls a month genuinely costs us more than someone running 5,000.

• Solo: 5,000 / month (~250 per business day)
• Team: 25,000 / seat / month (~1,250 per business day per seat)
• Enterprise: unlimited

We send usage alerts at 75% and 90% of your limit so you can upgrade or wait without surprise. Hard cap at 100% — calls beyond the cap return a clear “monthly limit reached” message instead of a silent failure.

Yes, on Team and Enterprise plans.We can resell Claude licenses through your Cohesive360 contract, handle provisioning and seat assignments, and consolidate the bill onto a single invoice. This is useful for firms that don't want to manage two vendor relationships. Email sales@cohesive360.com to scope.

Yes — Enterprise plan only.We can deploy the connector inside your firm's own AWS, Azure, GCP, or on-premise environment alongside a private Claude (Anthropic on AWS Bedrock, Vertex AI, or your own Anthropic enterprise contract). This is required for firms with strict data-residency, sovereign-cloud, or air-gapped requirements. Setup takes 2-4 weeks and includes infrastructure-as-code templates, a runbook, and SSO integration. Email sales@cohesive360.com.

One SmartAdvocate username equals one seat. The same user across laptop, home PC, and phone counts as one seat — the license is tied to the SA login, not the device. Adding a new firm staffer who needs their own SmartAdvocate login means adding a seat. Removing a staffer frees their seat back to your pool.

Cancellation takes effect at the end of your current billing period. After that, every license instance is revoked and Claude stops being able to call SA on your behalf. Your account and subscription history remain in our database; email privacy@cohesive360.com to delete them entirely — we complete requests within 30 days. We never had your case data on our servers in the first place; that always lived in your SA tenant.

Not today — the license server is Cohesive360-hosted. If your firm has compliance requirements that prevent calling an external license service, email sales@cohesive360.com for an enterprise on-premise option. We've shipped on-prem versions for two firms with strict data-residency requirements; it adds setup time but it's tractable.

Email support@cohesive360.com. Response times: under 4 business hours on paid plans. Include the first 4 characters of your license key, the case number you were working on (if applicable), and the error message Claude showed you — that gets us to the right log entry fastest. We have audit logs of every tool call by every seat, so we can usually pinpoint what happened within 15 minutes.

Bugs to support@cohesive360.com — include a screenshot of the chat and the SA case number if relevant. Capability requests to product@cohesive360.com — describe the workflow (“I want to ask Claude to X and have it Y”) rather than the API endpoint, because we may already have a path to the same outcome through different tools.