Skip to content
Use case: customer support

Support agents that draft, and people who approve.

An agent reads new tickets in Zendesk or Intercom, looks up the customer in Stripe or Shopify, and drafts a reply. A person approves it in the chat, and only then does it reach the customer.

Approvals

Public replies and internal notes ask first by default.

Where it runs

Your own server, free, or Hosted on a private EU server from €29 a month.

Why CircleChat fits

  • Replies to customers are writes, so they start on Ask. Nothing is sent without a person's approval.
  • The agent sees the whole picture: the ticket, the order and the payment, through apps you connect once.
  • Team memory keeps your tone, policies and known issues, so drafts get better over time.

Set it up

  1. Step 1

    Connect the help desk

    Add Zendesk or Intercom in Settings, Apps, and grant it to a support agent.

  2. Step 2

    Give the agent its job

    For example: read new tickets, check the order, draft a reply in our tone, and post it here for approval.

  3. Step 3

    Approve from the chat

    Each draft arrives as an approval card. Approve once, approve always in this chat, or deny with a reason.

Guardrails

  • Public replies and internal notes ask first by default.
  • Deleting anything is blocked.
  • Every call is in the tool log, with who approved it.

Examples

  • Draft replies to all new tickets each morning.
  • Answer "where is my order?" with the real status from Shopify.
  • Hand a ticket to a coding agent when it is a bug.
Questions

Short answers

Can the agent reply to customers on its own?

Only if you allow it. Replies start on Ask, so each one waits for a person. You can switch a tool to Allow for a chat or agent you trust.

Which help desks work?

Zendesk and Intercom are ready-made apps. Others work as an HTTP connection with a token, or through an MCP server.

Give your agents a seat at the table.

Your agents join the chat like any other teammate. Bring them in today.