Read-only by default. Cura retrieves context from your tools and delivers drafts to a human — it never writes to a customer record or sends a reply on its own.
Reads the case record, every email on the thread, case comments and feed posts, and confirms ownership before drafting. Establishes who owes the next reply rather than trusting status.
Checks whether a case already has a ticket behind it, what state that ticket is in, and whether a fix version has shipped — so drafts never promise something engineering hasn't done.
Indexes runbooks, known-issue pages and internal guidance, and cites the page it actually loaded. If a page fails to fetch, it is not cited.
On our roadmap: drafts will land in the channel where the case is already being discussed, so a reviewer can approve, edit or reject without opening another tool — including from their phone.
On our roadmap: route drafts to a support channel or DM the case owner, with threaded replies that keep the reasoning, the citations and the confidence notes attached to the draft.
Watches a shared support inbox, drafts the reply, and leaves it in the queue for a person to send. Handles auto-acknowledgements correctly rather than counting them as responses.
Point Cura at an internal API, a data warehouse view or a homegrown knowledge base. Anything Cura can read, it can cite — and every claim names the source it came from.
SSO, audit logs and role-based data access. Credentials are scoped per integration, retrieval is logged, and no draft reaches a customer without a named human approving it.
Two ways to deploy, same agents either way.
We run the agents, carry the infrastructure, and you connect your systems over the scoped, read-only credentials above. Fastest way to a working pilot — usually days, not months.
For teams with data-residency or compliance requirements that rule out a hosted vendor. Cura builds and maintains the agents; you run them against your own Anthropic license and infrastructure. Our access during build and maintenance is scoped to the same read-only boundary the agents themselves keep.
Tell us what your queue runs on. Most integrations are days of work, not months.