AI agents for customer support teams that answer from your documentation

Orkeste agents read each new Zendesk ticket or Intercom conversation, search your help pages in Confluence or your synced documents, and draft an answer or an internal note. Urgent cases are flagged to the team in Slack, and the replies you choose wait for a person on your team to approve them.

Where support time goes

The same questions, every day

Password resets, invoices, how to export data: half the queue is questions your documentation already answers, and each one still takes a person a few minutes.

Urgent tickets hide in the queue

An outage report or an unhappy key account looks like any other ticket until someone opens it, sometimes hours later.

Knowledge stays in a few heads

The answer to the tricky question lives in a Confluence page nobody finds, or in the memory of the one person who handled it last time.

Four agents beside your support team

They read, search the documentation and draft. The replies you choose wait for a person on your team to approve them.

Triage agent

Reads each new ticket, identifies the topic and the urgency, and adds an internal note in Zendesk with a suggested category and priority for whoever picks it up.

Answer drafter

Searches your documentation and writes a reply grounded in it. The reply is posted to the ticket or the Intercom conversation once a person approves it.

Escalation agent

Spots tickets that mention an outage, a refund or a cancellation and posts them to the support channel in Slack with a one-line summary.

Conversation summariser

Summarises long Intercom conversations for the next person who picks them up, or for the weekly review in Notion.

A new ticket, from queue to answer

The answer drafter on a common question.

  1. Read: A customer asks in Zendesk how to export their invoices. The agent reads the ticket and the customer’s previous tickets.
  2. Search: It searches your help pages in Confluence and finds the export guide.
  3. Draft: It writes a short answer with the steps from the guide.
  4. Approve: The reply waits in Validations. A person on the team checks it and approves; the answer is posted to the ticket.

What stays with your team

Refunds, exceptions, upset customers and anything the documentation does not cover. The agents prepare and flag; your team owns the conversation.

The tools these agents work in

Workflows to start from

Agent roles for this team

Frequently asked questions

Will AI agents replace our support team?

No. They read, search and draft so your team spends its time on the cases that need judgement. The replies you choose wait for a person to approve them.

Can the agent assign or close tickets?

Not today. In Zendesk an agent adds public replies and internal notes; it does not assign, merge, tag or close tickets. In Intercom it replies to conversations but does not assign, tag or close them.

Where does it find the answers?

In the knowledge you give it: Confluence pages, documents synced from SharePoint or OneDrive, and files you add to the agent. Its briefing can tell it to answer only from those sources and to escalate when they do not cover the question.

What if a draft is wrong?

You edit it or reject it in Validations before anything reaches the customer.

What does it cost to run?

Each run uses credits from your plan, from 2 credits with Claude Haiku 5.5 to 235 with Claude Fable 5.1 depending on the model you choose, and you can set a daily and a monthly budget per agent.

Keep reading