Documentation Index

Fetch the complete documentation index at: https://docs.getomni.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

A New Analytics Page, WhatsApp Sequences, and Manual Status Overrides

A big week for visibility and outbound — the analytics page has been rebuilt from the ground up, WhatsApp joins email and SMS in automated sequences, and you can now set a lead’s status by hand from the dashboard.

​

Features

​

Redesigned Analytics Page

Use case: Get a faster read on conversion, agent activity, and lead pipeline health without exporting data. The analytics page has been rebuilt with new charts, cleaner filters, and a layout that puts the metrics that matter first. The underlying Analytics API is unchanged — this is a pure frontend refresh.

​

WhatsApp in Sequences

Use case: Reach leads on the channel they actually answer — extend automated follow-ups beyond email and SMS into WhatsApp. Sequence steps now support WhatsApp alongside email and SMS. Pick a Twilio Content Template from the new template dropdown, map your variables, and the step will send through your connected WhatsApp number on schedule. Templates are pulled live from Twilio so approved content shows up automatically.

​

Manually Update Lead Status

Use case: Override the agent when you already know the outcome — close a lead, opt them out, or send them to review without waiting on the checklist. A new status picker on the leads dashboard and lead detail page lets you set a lead to Completed, Opt Out, or Needs Review. The change goes through the same logic the agent uses — opting out stamps optedOutAt, completing skips remaining required checklist items, and review creates an escalation — and a confirmation modal summarizes the impact before applying. The action is attributed to the user who triggered it, and completing a lead this way fires the lead.completed webhook just like an agent-driven completion.

​

Improvements

​

Email Threading in Sequences

Sequence emails can now reply to the previous thread instead of starting a new one, keeping the conversation in a single thread in the recipient’s inbox. A new “Reply to previous thread” checkbox controls the behavior per step, and it defaults on for new email steps.

​

Document Validation in Webhooks

The document.extracted webhook now includes a classification block with per-checklist-item validation results. When validation fails, the webhook fires with status: completed, an empty extractionResult, and human-readable failure reasons on each matched item — making it much easier to react to document rejections downstream.

​

Document Period Returned for All Types

When a document type has a configured grace period, the webhook and document responses now return both the preferred and fallback period, and a period is returned for every document type rather than only those tied to a specific checklist item. This makes it possible to surface “valid but outside preferred range” documents in your own systems.

​

Clearer Status Attribution

When a user manually changes a lead’s status, the timeline summary and actionLog row now record which user made the change, so it’s easy to trace status updates back to the operator who made them.

​

Fixes

• Fixed an email rendering error that prevented quoted content from being collapsed for messages from certain email clients
• Fixed the “publish changes” banner appearing on sequence steps when no changes had actually been made
• Fixed an editor issue where empty paragraphs in email bodies could cause downstream errors
• Fixed inconsistent display of the completed/in-progress badge between the leads dashboard and the lead detail page
• Fixed a rare error reading properties of an undefined message body