Customer support

The support desk end to end: replying, escalating, writing macros and help articles, coaching quality, and turning tickets back into evidence the product team can act on.

9 agents

Choosing between them

Summaries in one category tend to sound alike. What separates them is the line each agent draws around its own work — quoted here from its brief.

  • Cancellation & Retention Specialist

    Agent name: Zeynep Aydin

    Turns cancellations into a save playbook by reason, fixes failed-payment churn, and writes an exit flow that is not a maze.

    From its limits

    You do not give legal advice.
  • Escalation & Service Recovery Lead

    Agent name: Tomas Berenguer

    Handles the cases that already went wrong: builds the escalation brief, the apology that lands, and the fix that stops the repeat.

    From its limits

    You are not a lawyer and you give no legal advice.
  • Frontline Support Responder

    Agent name: Chidera Ilonze

    Triages your support inbox and hands back ready-to-send reply drafts with priority, sentiment and what to verify flagged.

    From its limits

    You do not send anything.
  • Help Center Content Lead

    Agent name: Solveig Lysaker

    Turns your top support questions into help-centre articles customers can finish alone, and prunes the ones nobody reads.

    From its limits

    You do not document behaviour you have not been shown.
  • Support Bug Intake Specialist

    Agent name: Lukas Brenner

    Turns vague customer complaints into bug reports engineering can reproduce, with severity, a dedupe check and an evidence request.

    From its limits

    You do not read the codebase, debug source or assign root cause.
  • Support Macros & Tone Architect

    Agent name: Rahul Iyengar

    Builds your saved-reply library and tone sheet: one macro per contact driver, with triggers, variables and a quarterly prune.

    From its limits

    You do not write policy.
  • Support Operations Planner

    Agent name: Marek Dvorak

    Sizes your support staffing, writes an SLA you can actually keep, and maps how tickets get routed and escalated.

    From its limits

    You are not an employment lawyer or an HR adviser.
  • Support Quality Coach

    Agent name: Chiara Vitali

    Scores support conversations against a rubric you can defend, and turns each one into a single specific coaching note.

    From its limits

    You are not an HR instrument.
  • Voice of Customer Analyst

    Agent name: Naoko Fujisawa

    Codes your tickets into themes with real counts, then says what to ship, what to say, and what to move into self-service.

    From its limits

    You do not do statistics your data cannot carry.

Put one of them on a real process

Build a team of agents, give the team a process that repeats, and read the plan before it runs.