LION REACH

Marketing platform — paste the access token to unlock this browser.

Skip to content
LION REACH DEMO
Send Talk Build Watch Guard

Channel health

Audience snapshot

Campaigns

Automations recurring programmed sends

Journeys graph programmes a contact walks — drawn on the canvas, executed on 30-second ticks

Inbox two-way conversations across SMS and WhatsApp — STOP handling and human-handoff run before anything else

Pick a conversation. New inbound messages land here as the bridges push them to /inbound/:channel.

Channels live bridge and SMTP health, per-number usage, kill switches

Loading…

Analytics sends, outcomes and reasons — 'sent' means channel-accepted; see Definitions

What the numbers mean

Sent — the channel (bridge or SMTP host) accepted the message; not proof it reached a handset or inbox. Acceptance rate — sent ÷ (sent + failed); called delivery rate only where receipts exist. Delivered / read — bridge receipts, where the channel reports them. Opened — the tracking pixel loaded; image-blocking clients undercount, scanners overcount — treat as approximate. Skipped — deliberately excluded (consent, suppression, guardrails, caps, dedupe) with the reason recorded. Failed — attempted and refused.

Daily volume sent and failed per day, by channel

Deeper cuts each loads on demand

Why sends were skipped

Why sends failed

Campaign funnels audience → sent, per campaign

Segments

Templates

Suppression list do-not-contact

Activity log

Settings

Test send