WorkersWorker settings

Wake a worker when another worker finishes a result

Updated October 6, 2026 · 2 min read

To chain workers, add a Worker result trigger: the worker then runs each time one of the source workers you pick finishes a Result. A common setup is a custom Voice of Customer worker that analyses every chat your Support worker closes.

Which workers can be chained

Role

Workers

Source (finishes the Result)

Customer Support Chat, Customer Support Email, Success, Preventive Outreach, and your custom Support or custom workers

Listener (gets woken up)

Custom workers and custom Support workers

Add a Worker result trigger

  1. Open the worker that should listen and go to Settings → Triggers.
  2. Click Add trigger, choose Always-on, and pick the Worker result event.
New trigger panel with Always-on selected and Worker result chosen as the event source.
  1. Open the event Settings and pick one or more Source workers.
  2. Under Result statuses, choose which finished Results should wake this worker: Processed (the default), Skipped, or Failed.
Worker result settings with Customer Support Chat ticked under Source workers and Processed ticked under Result statuses.
  1. Save the trigger and make sure both workers are enabled. New Results from the source now start this worker automatically, and they show up on its Results tab.

When a source worker wakes its listeners

  • Customer Support Chat and custom Support workers wake listeners once per conversation, when the chat closes (resolved or escalated), not on every reply.
  • Customer Support Email wakes listeners when an email is answered or escalated. Ignored and spam emails never do.
  • Success wakes listeners on escalation.
  • Custom and Preventive Outreach workers wake listeners for each finished Result, and they are the only sources that produce Skipped or Failed Results today.

FAQ

Why is my worker missing from the Source workers list?

A worker never appears in its own source list. A source is also unavailable when picking it would create a loop, for example A wakes B and B wakes A. The picker shows the loop path.

Why didn't my listener run after a chat reply?

Chat and Support workers only wake listeners when the conversation closes, by resolution or escalation. Replies on an open chat don't trigger anything.

Should I select Skipped or Failed?

Only if your source is a custom or Preventive Outreach worker. Customer Support Chat, Customer Support Email and Success only finish Results as Processed, so the other statuses never fire for them.

What happens if I delete a source worker?

It stops waking listeners. Its name stays on the trigger as a Deleted worker chip that you can remove.

Related articles

  • Add a trigger to a worker

    Add a live or scheduled trigger so a worker only runs on the events you choose.

  • Limit a trigger with customer segments

    Add a segment condition so a trigger only continues for the accounts or messages that match.

  • Add a custom worker

    Create a Support chatbot for your Crisp inboxes, or a Success worker for onboarding, upsell, and churn, with the Add Worker wizard.

  • Read and filter Results

    Open the Results tab, filter by date or column, then read each row for the full outcome.

  • What is a worker

    A Worker is an always-on automation trained on your knowledge that starts as a copilot, then can go live on its own.

← All help articles