Automation Analytics (Clean Estimate V1)

V1 reference with a current V2 subset: Current V2 does not expose More > Analytics > Automations, enrollment totals, speed-to-lead cards, auto-dial metrics, or a panel named Delivery Health. It does have a per-workflow Automation report on Business > Reports, described below, built on V2's own automation engine rather than V1's.

Current V2: Automation Report (Reports Page)

Open Business > Reports, then the Automations card, or go straight to /reports/automations. It has its own page and report-tab entry, and lists every automation workflow with, for the selected range and location: Runs, Sends, Exits, and Conversions.

• Runs is how many times the workflow started.
• Sends counts a message only once it actually went out; a test-mode dry

run that never produced a real message is not counted as a send.

• Exits is how many runs ended early through one of the workflow's exit

conditions.

• Conversions is the subset of exits whose exit reason is a genuine

positive outcome (a proposal was accepted, or a booking was created), not just any matching event.

This card is gated on the View automations permission, separately from View financial reports, because the underlying automation tables enforce that permission at the database level. A teammate who can see the rest of Reports but lacks View automations will not see this card at all rather than seeing it empty.

V1's real Automations tab (average time to first contact, auto-dial connect rate, delivery health by channel, lead intake by source, enrollment overview, sequence performance) was built entirely on V1's old follow-up-sequence engine. V2 replaced that engine with its own linear automation workflow builder, so those exact cards have nothing to port; runs/sends/exits/ conversions per workflow is the equivalent question (how is each workflow doing) answered from the data V2's current engine actually has.

Export this card (automation_report) with the page's CSV/Print controls; see Reporting Overview.

Current V2: Message Delivery

Current V2's shipped delivery report lives under Inbox > Delivery, not Analytics. It has This week, This month, and This quarter presets, exact from/to dates, and a location selector when the teammate can see more than one location.

For both email and text messages, it reports the send boundary in complete buckets, including:

• messages attempted and accepted by the provider
• sends prevented by deployment configuration, consent, or notification preference
• missing contact methods or sender numbers
• sends still in flight, sends with no recorded outcome, and unrecognized outcomes
• recipient-change refusals and provider-call failures

For email, the page also reports later provider facts: confirmed delivery, bounce, spam complaint, delay, provider suppression/failure, open signals, and link clicks. Open signals are weak evidence and are not presented as confirmed human reads.

For text messages, the provider-fact area now includes carrier delivery and failure facts when the carrier reports them. Coverage still varies by carrier — some report only that the text was sent and never confirm it reached the handset — so a missing delivered/failed count is not the same as nothing having arrived.

V1 Workflow Analytics Baseline

The V1 automation report combined message delivery with configurable workflow metrics such as:

• average time to first contact and contact rate
• automated-call connection rate and at-risk leads
• lead intake by source
• active, paused, completed, and suppressed enrollment totals
• per-workflow run counts, success rates, and sequence performance

V1 also exposed per-workflow analytics from workflow details. V2 cannot provide those views until tenant workflow definitions, enrollment records, run history, permissions, and monitoring are ported. Fixed notification jobs and message delivery records are not substitutes for that data model.