Review Automation Reports

Know whether your automations are doing their job — running on the right records, not stalling or failing, and moving the numbers you care about like faster lead response and more booked visits. These reports let admins and managers catch silent failures early and prove automation is producing real sales results.

Entry pointAutomation

Use these reports whenever you publish a new workflow, change a sender, adjust lead distribution, or investigate missed follow-up.

What to Review

Report or view	Use it to answer
Workflow list	Which workflows are active, paused, unpublished, or recently changed?
Enrollment history	Which contacts or deals entered, waited, exited, or were manually unenrolled?
Workflow simulation or test view	Would this record qualify, and which branch would it take?
Contact activity history	Did the automation create the expected task, message, note, or owner update?
Lead distribution policies and claims	Were leads routed to the intended eligible owners?
Source and sales reports	Did automation improve speed, conversion, visits, deals, or revenue?

Daily Admin Check

1. Open Automation and review active workflows.
2. Check whether any workflows were paused or unpublished unexpectedly.
3. Open enrollment history for business-critical workflows.
4. Filter for waiting or exited records.
5. Review failed or skipped steps if shown.
6. Confirm connected senders are still verified for message actions.
7. Review lead distribution claims if your team uses claim windows.

Weekly Manager Review

1. Choose the automation that supports a key process, such as new lead assignment or site visit reminders.
2. Count how many records enrolled during the week.
3. Compare enrolled records with outcomes: calls completed, meetings booked, site visits scheduled, deals created, or deals won.
4. Identify drop-off steps. For example, many contacts may receive WhatsApp but few may book a visit.
5. Review whether owners completed the tasks automation created.
6. Adjust only one major rule at a time so the next report is easier to interpret.

Example: Missed Callback Investigation

A manager notices several new Facebook leads were not called. The investigation should follow the automation trail:

1. Check whether the contacts entered the new lead workflow.
2. Confirm they matched the Facebook source condition.
3. Check whether lead distribution assigned owners.
4. Check whether call tasks were created.
5. Check whether users completed or ignored those tasks.
6. If the workflow worked, coach the team. If it did not, fix the trigger, condition, assignment policy, or notification step.

Common Report Clues

Clue	Meaning	Action
No enrollments after publish	Trigger may not match live records.	Test with a sample record and check conditions.
Many records waiting	Delay, wait-until, business hours, or missing event may be holding records.	Review wait settings and expected time zone.
Records exited early	Exit rule may be too broad.	Check sequence exit policies and event filters.
Messages skipped	Sender, template, recipient, or phone/email value may be missing.	Verify connector and required fields.
Tasks created but not completed	Automation is working, but sales execution is the issue.	Review task ownership and manager follow-up.
Leads routed to wrong owners	Eligible owners or source filters may be wrong.	Update lead distribution policy.

What Good Automation Looks Like

Good automation should improve a measurable outcome. Examples:

• New lead response time decreases.
• Fewer leads stay unassigned.
• More site visits are scheduled after reminder sequences.
• Managers receive fewer manual escalation requests.
• Sales users spend less time creating repetitive tasks.
• Automated follow-ups create replies, meetings, or qualified pipeline.

For outbound campaign delivery and conversion, use Campaign Reports and Analytics.

Troubleshooting

Problem	What to check
Can't open enrollment history, runs, or these reports	Report visibility follows your role — ask your admin, who can also confirm the senders and connectors these reports depend on.
Workflow is published, your test record clearly matches the trigger, connectors are verified, but enrollment history still doesn't show the expected behavior	See Getting Help — include the workflow name, sample record, expected action, timestamp, and a screenshot of enrollment history.