Zendesk CSAT Follow-up Agent with OpenClaw

The loudest rule here is a prohibition. It never contacts the customer in any form: no apology, no credit, no public reply, nothing that reaches their inbox. OpenClaw is a plain agent pointed at a plain job, and the job is one internal comment and one Slack line, because deciding to make it right usually costs money and needs a person.

Loading preview…
Free to start · guided setup

Watch it work before it's live

Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.

CSAT 1/5 on ticket #48213

Open

Yuki Tanabe <#48213>

Three different people asked me to send the same screenshot, and the third one asked me to explain the whole problem again from the beginning. Eleven days to change one setting. I have no confidence it would go any better next time.

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect Zendesk

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Followup rules

    Which scores you want worked and what should happen to them: the threshold that counts as low, who gets the Slack line, the accounts or plans that always matter, and what a reasonable recovery step looks like at your company.

  4. Runs on OpenClaw

    Preselected for this page — connect your OpenClaw account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

Why OpenClaw for this agent

The customer hears nothing

There is no public reply operation on this graph. The worst outcome is an internal note that reads badly, sitting where your team can already see it and correct it.

Eight lines, written for a colleague

A note that runs long gets skimmed and then quoted wrongly. The length ceiling is part of the instruction rather than a style preference.

Before you fork

Is there any path from that note to the customer's inbox?

No. The Zendesk operations wired in read tickets and comments, list a requester's other tickets, and add an internal comment. There is no mail tool anywhere on the graph. Whether you go back to the customer, and with what, stays a decision somebody has to authorise.

Run it with a different agent

Put Zendesk CSAT Follow-up Agent to work on OpenClaw

Free to start. Guided setup, a test run against staged conversations, and it's live.