Zendesk CSAT Follow-up Agent with Codex

Between the survey landing and the note appearing, most of the work is traversal: the ticket, its comments in order with timestamps intact, then the requester's other tickets by id. Codex sits comfortably inside structured records of exactly that sort, and the write at the end is a single internal comment in a shape you set. Nothing is open ended once the score has cleared your threshold.

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 Codex

    Preselected for this page — connect your Codex 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 Codex for this agent

Comment lists, in order

Ordering an exchange correctly and carrying timestamps through into the quote is structured work before it is writing. A wrong timestamp is what makes a note useless in a review.

One note, one Slack line

The entire output is an internal comment and a message to your CX lead. A harness suited to well scoped tasks has very little room to wander here.

Before you fork

Does the customer's survey comment leave Zendesk?

It goes to the model you connect, and it comes back quoted inside an internal comment on that same ticket plus the line to your CX lead. The customer receives nothing at all. If verbatim customer wording does not belong in a broad channel, point the Slack half at a private one.

Run it with a different agent

Put Zendesk CSAT Follow-up Agent to work on Codex

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