Automation, macros and workflows

Choose manual action bundles, event rules or visual multi-step execution for the job.

How it works

1. 01

   Macros

   Macros. A teammate deliberately runs a saved bundle of supported conversation actions. This is useful for repeated handling work; it does not make the macro an autonomous AI agent.

2. 02

   Automation

   Automation. Event rules evaluate their configured conditions and run supported actions when the event matches. Keep overlapping rules explicit so they do not fight workflow routing.

3. 03

   Workflows

   Workflows. The visual graph supports branching, event scope, assignments, contact changes and connected steps with execution history. A callable On demand flow lets an agent reuse configured business logic.

4. 04

   Shared effects

   Shared effects. Each operation changes its underlying conversation/contact/integration record according to its own contract. Combining actions does not turn external API writes into a single rollback-safe transaction.

5. 05

   Choose intentionally

   Choose intentionally. Use a macro for an operator shortcut, a rule for simple automatic conditions and a workflow for explicit multi-step routing. Do not enable competing assignment paths and assume the final owner is deterministic.

What to verify