Reprocess Crisp conversations with a Support worker
Updated October 12, 2026 · 2 min read
Reprocess Crisp conversations with your Support worker when chats were missed, for example while the worker was paused or before you fixed a Skill. The worker picks them up as if the visitor had just written, so customers can get a reply.
Which Crisp conversations get reprocessed
A conversation is queued only if all of these are true:
- It is unresolved in Crisp.
- The last message is from the visitor (text or media), so the customer is still waiting.
- It is in the Main inbox.
- It had activity inside the window you choose. The window can be at most 24 hours.
Reprocess Crisp conversations from Run Worker
- Open Workers and select your Support worker (Chat or a custom Support chatbot). Make sure it is turned on.
- Click Run Worker in the worker header. Under Run mode, choose Batch.
- Under Input, pick Crisp. Under Time window, pick Last 15 minutes, Last 1 hour, Last 6 hours, or Last 24 hours. For an exact range, open Advanced and set From and To — up to 24 hours apart.
- Read the count under the yellow warning. With 10 or fewer unresolved chats in the window it reads “This will process N conversations”, which is the exact number. With more, it reads “About N unresolved conversations in this window”, an estimate that can include chats whose last message is not from the visitor.
- Click Run. You'll see “Batch job queued” while the conversations are processed in the background.
- Open the Results tab to follow each conversation as it is processed.
Reprocess a longer period
Run one batch per 24-hour window, using Advanced → From and To to pick each range. For a recurring sweep, add a scheduled trigger under Settings → Triggers instead of running batches by hand.
FAQ
Will customers get a reply from a reprocessed conversation?
Yes, they can. Reprocessed conversations go through the same path as live Crisp messages, so the worker can reply, route, or resolve them based on its Skills and Actions.
Why does the count say “No conversations match these filters”?
No chat in that window is unresolved, in the Main inbox, and waiting on the visitor's last message. Try a different window, or check that the conversations are in the Main inbox.
Why is the count only an estimate?
When the window has more than 10 unresolved chats, Zentesimal estimates from unresolved conversations instead of checking each last message. The batch still only queues chats where the visitor wrote last.
Can I reprocess conversations from other Crisp inboxes or older than 24 hours?
No. Reprocessing covers the Main inbox only, and each run covers at most 24 hours. To go further back, run several batches and set each range under Advanced → From and To.
Does this work on a custom Support chatbot?
Yes. Run it from that chatbot's own Run Worker. Conversations are processed by that chatbot, with its Skills and Actions, not by the default Chat worker.
Related articles
- How to run a worker
Use Run Worker for tests and on-demand runs. Choose Batch or Single event, pick an input, then check Results. Ongoing work uses Triggers.
- Read and filter Results
Open the Results tab, filter by date or column, then read each row for the full outcome.
- Add an action to a worker
Pick the actions a worker may take — like sending a Slack message or updating Crisp — and fill in the required settings.
- Schedule a worker to run on a cadence
Set a repeating schedule and timezone on a trigger, then check the next run time on the worker.
- Review chat escalations after the fact
See why the chat worker handed a conversation to your team: find escalated chats on Results, then open the Agent trace to read its reasoning step by step.