Plays
What Plays are and how to add or customize them.
- What is a Play
A Play is an always-on automation trained on your knowledge that starts as a copilot, then can go live on its own.
- 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.
- Enable or pause a Play
Turn a Play on once its knowledge, Skills, and a test run look right, or pause it any time without losing its setup.
- Duplicate a Play
Copy an existing Play into a new, disabled instance so you can try a second playbook without starting from a blank wizard.
Play settings
Triggers, actions, and input settings.
- Add an action to a worker
Add actions to a worker so every Skill inherits them, or to one Skill only, like Slack messages, Crisp updates, or follow-ups.
- Schedule a follow-up from a worker
Let a worker schedule a follow-up for itself, then come back later to check whether a fix worked or a teammate answered.
- Let a Play browse a public URL
Add the browse-URL action when a Play needs to read a public page that isn't in your Knowledge base.
- Add a trigger to a worker
Add a live or scheduled trigger so a worker only runs on the events you choose.
- 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.
- Limit a trigger with customer segments
Add a segment condition so a trigger only continues for the accounts or messages that match.
- Wake a Play when another Play finishes a result
Add a Play result trigger so one Play runs each time another finishes a Result, like a VoC Play that analyses every closed chat.
- Add or edit Guards
Add Guard rules that check a worker's final result and the Actions it took in that run, not conversation history or knowledge.
- Edit Agent Skills for a Play
Open Knowledge → Agent skills to edit the playbook a Play reads at runtime.
- Save and restore skill versions
Save a Skill as a new version before a risky edit, or restore an older version if a change doesn't work out.
- Set Play input fields
Define typed input fields so Zentesimal maps spreadsheet rows, JSON, or free text into them before the Play runs.
- Use Datadog RUM as worker input
Connect Datadog and map RUM unique users into a scheduled cohort for batch workers.
Running Plays
Run a Play, read results, and work in batches.
- 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 a note on a Result
Leave an append-only note on any Play Result so the next teammate who triages it has context.
- Add baseline and target lines to Results charts
Click a Results chart to add a tagged baseline or target line, then drag, rename, or delete it.
- Add a prompt column on Results
Add a prompt column when you need a one-off label or summary on existing Results.
- Reprocess Crisp conversations with a Chatbot
Rerun your Chatbot on Crisp chats still waiting on a reply, in windows of up to 24 hours, from Run Play → Batch.