Play settings

Add actions to a worker so every Skill inherits them, or to one Skill only, like Slack messages, Crisp updates, or follow-ups.

Let a worker schedule a follow-up for itself, then come back later to check whether a fix worked or a teammate answered.

Add the browse-URL action when a Play needs to read a public page that isn't in your Knowledge base.

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

Set a repeating schedule and timezone on a trigger, then check the next run time on the worker.

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

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 Guard rules that check a worker's final result and the Actions it took in that run, not conversation history or knowledge.

Open Knowledge → Agent skills to edit the playbook a Play reads at runtime.

Save a Skill as a new version before a risky edit, or restore an older version if a change doesn't work out.

Define typed input fields so Zentesimal maps spreadsheet rows, JSON, or free text into them before the Play runs.

Connect Datadog and map RUM unique users into a scheduled cohort for batch workers.