Practical automation recipes

Start with one narrow rule. A useful automation has a clear trigger, a condition your team understands, and an outcome you can verify.

Route new enquiries

Trigger: Lead created or native form submitted.
Condition: The lead matches the intended source, form, or category.
Actions: Assign an eligible owner or use supported round-robin assignment; create a follow-up; notify the relevant CRM users.

Keep source-level intake alerts separate from assignment alerts. Review both to avoid unnecessary duplicate notifications.

Follow up after a missed call

Trigger: A supported missed-call event is linked to a lead.
Condition: Use the available lead conditions to narrow the workflow.
Actions: Create a task or schedule a follow-up for the responsible user.

Not every phone status has the same meaning. Check the call and execution log before assuming the customer could not be reached.

Make a stage handover consistent

Trigger: Lead stage changed.
Condition: The lead entered the intended stage.
Actions: Create the next task, add a note, or notify the selected internal team.

Avoid a rule that repeatedly changes the same stage or assignment and triggers itself.

Prioritize a valuable enquiry

Trigger: Lead created or value changed.
Condition: The recorded value meets your threshold.
Actions: Assign the appropriate owner and schedule a review.

A value threshold is your business rule, not a guarantee that the lead will convert.

Test before enabling

1. Build the rule while disabled.
2. Review conditions, recipients, and assignment permissions.
3. Use available simulation controls where appropriate.
4. Enable the rule and create a controlled test event.
5. Check Automations → Execution history.
6. Confirm the actual task, follow-up, or assignment result.

A simulation is not proof that an external provider will deliver a message.

Flexible does not mean unbounded

Automations support many combinations of the implemented triggers and actions. Safety limits, supported fields, permissions, and execution safeguards still apply. “Unlimited possibilities” should not be read as unlimited volume or support for any action.

Current internal alerts are not customer email/SMS campaigns. Time-based team reminders are handled by notifications. Planned customer messaging is listed in channel availability.