Automation Rules

Trigger emails, SMS, tasks, and status changes automatically as leads move through your pipeline — so the routine work happens without anyone remembering to do it.

Automations turn the repetitive parts of intake and follow-up into background work. Define what should happen and when, and VerdictFlow takes care of the rest — every action is logged on the lead so your team always sees the full picture.

What you can automate

Notify your team when a high-value lead comes in.
Send a follow-up email or SMS if a lead hasn't been contacted within X hours.
Auto-assign leads to specific team members based on case type or geography.
Create tasks when a lead reaches a particular status (e.g. "Send fee agreement" when status changes to Ready for Referral).
Move statuses based on activity (e.g. mark a lead Dropped if there's been no contact for 30 days).
Create calendar events when an intake call is scheduled.

How a rule is built

Every automation rule is just three pieces:

Trigger — when should the rule run? (e.g. "lead status changes", "new lead created", "X hours after last contact")
Conditions (optional) — which leads should match? (e.g. "case type is Personal Injury and source is Google Ads")
Actions — what should happen? (e.g. "send this email, then create this task")

You can chain multiple actions in a single rule, and each action records itself on the lead's activity timeline so there's a clear audit trail.

Safety rails

Test mode lets you fire a rule against a sample lead before it goes live.
Per-rule activity log shows every execution: when it ran, which lead it ran on, and whether each action succeeded.
Pause any rule instantly if you need to stop it without losing the configuration.

Next steps

Auto-routing rules — automatically send qualifying leads to partner firms.
Tasks — see how automation-created tasks show up in your team's queue.
Lead pipeline — customize the statuses your automations will react to.

Automation Rules

Trigger emails, SMS, tasks, and status changes automatically as leads move through your pipeline — so the routine work happens without anyone remembering to do it.

What you can automate

Notify your team when a high-value lead comes in.
Send a follow-up email or SMS if a lead hasn't been contacted within X hours.
Auto-assign leads to specific team members based on case type or geography.
Create tasks when a lead reaches a particular status (e.g. "Send fee agreement" when status changes to Ready for Referral).
Move statuses based on activity (e.g. mark a lead Dropped if there's been no contact for 30 days).
Create calendar events when an intake call is scheduled.

How a rule is built

Every automation rule is just three pieces:

Trigger — when should the rule run? (e.g. "lead status changes", "new lead created", "X hours after last contact")
Conditions (optional) — which leads should match? (e.g. "case type is Personal Injury and source is Google Ads")
Actions — what should happen? (e.g. "send this email, then create this task")

You can chain multiple actions in a single rule, and each action records itself on the lead's activity timeline so there's a clear audit trail.

Safety rails

Test mode lets you fire a rule against a sample lead before it goes live.
Per-rule activity log shows every execution: when it ran, which lead it ran on, and whether each action succeeded.
Pause any rule instantly if you need to stop it without losing the configuration.

Next steps

Auto-routing rules — automatically send qualifying leads to partner firms.
Tasks — see how automation-created tasks show up in your team's queue.
Lead pipeline — customize the statuses your automations will react to.