Integrations

Plugs into the systems your queue already runs on.

Cura reads from your tools and hands drafts to a person. It never writes to a customer record or replies on its own.

Read-only by default Scoped credentials Every retrieval logged

Systems of record

Where the facts live.


Salesforce
  • Case record, full email thread, comments and feed posts
  • Checks who owes the next reply, not just the status field
Read-onlyNo create, update, close or comment
Jira
  • Linked defects, their state and fix versions
  • Stops a draft promising a fix that hasn't shipped
Read-onlyIssues, comments, fix versions
Confluence
  • Runbooks, known-issue pages and internal guidance
  • Only cites pages it actually loaded
Read-onlySpaces you choose
Internal docs and knowledge base
  • Your existing docs and knowledge base articles, wherever they live
  • Kept in sync as they change, and cited in the draft
Read-onlyTeam and above

Channels

Where the work happens.


Email
  • Watches a shared support inbox
  • Leaves the draft in the queue for a person to send
  • Knows an auto-acknowledgement isn't a real reply
Available nowShared mailbox or forwarding
Microsoft Teams
  • Drafts arrive in the channel where the case is being discussed
  • Approve, edit or reject from there, even on your phone
Coming soonNeeds a Teams app registration
Slack
  • Send drafts to a support channel or DM the case owner
  • Citations and confidence notes stay attached in the thread
Coming soonChannel-scoped Slack app
Custom API

Got an internal API, a warehouse view or a homegrown knowledge base? If Cura can read it, it can cite it, and every claim names its source.

RESTOAuth or service credentialRead scopes only
Built for security review
  • Credentials scoped per integration
  • Every retrieval logged
  • No draft reaches a customer without a named person approving it
SSOAudit log exportRole-based access

Deployment

Where Cura runs.

Two options. The agents are the same either way.


Hosted by Cura

We run the agents and the infrastructure. You connect your systems with scoped, read-only credentials. It's the quickest route to a working pilot, usually days rather than months.

Starter, Team, Bespoke and Enterprise
On-prem or self-hosted

For teams whose data-residency or compliance rules rule out a hosted vendor. We build and maintain the agents, and you run them on your own infrastructure and Anthropic license. Our access stays inside the same read-only boundary the agents keep.

Bespoke and Enterprise · see packages

Don't see your stack?

Tell us what your queue runs on. Most integrations take days, not months.

Book a demo Email us
Days, not months

Connecting your queue and indexing your docs is most of the setup work.