Dispatch Flow Control hightouch.myorg.ai · Snowflake / Postgres → Hightouch → Twilio
loading… TRIAL MODE — no real SMS can be sent

Help

The waiting queue —  messages held on purpose

Every held message is a decision, not a defect. Click a reason to see the exact drivers behind it. Below: what each hold protects, and which buyer at a prospect account cares about it most.

⚖️ Compliance & Legal — General Counsel, Compliance Officer

Quiet hours · do-not-contact · consent gating. TCPA statutory damages run $500–$1,500 per text and class actions are filed on autopilot — one bad campaign to 10,000 drivers is an eight-figure exposure. Here, STOP becomes hard suppression in under a minute, quiet hours follow the driver's current timezone, and every send is audit-trailed (Hightouch sync logs + delivery records). The pitch: compliance as enforced pipeline, not training material.

🛡️ Safety & Operations — VP Ops, Safety Director

DRIVING suppression · HOS-illegal filtering. FMCSA penalties reach ~$16k per HOS violation, and CSA scores drive insurance premiums. This system never buzzes a phone at 70 mph and never advertises a load the driver can't legally haul — the two biggest red bands in the chart are safety refusals. The pitch: fewer violations, defensible duty-of-care, drivers who don't feel spammed into unsafe behavior.

📈 Growth & Marketing — CMO, Head of Driver Experience

Perfect-timing holds · frequency caps · best-load-only. Waiting for a meal window and sending one great match instead of nine mediocre ones is why reply rates run ~2.4× higher and opt-outs drop ~64% (modeled). Every message held here is list-equity preserved — the contact list is a depreciating asset this queue protects. The pitch: fewer, better messages that keep the channel alive.

🏗️ Data Platform — Head of Data / Analytics Engineering

The whole queue lives in the warehouse. No second copy of customer data in a marketing tool: eligibility is SQL, the queue is a table, Hightouch activates it in place and syncs only diffs. Governance, lineage, and debugging happen where the data already lives. The pitch: activation without surrendering the source of truth.

💰 Finance — CFO

Every held message is spend not wasted. Volume down ~57% while conversions rise; per-message channel fees only go to messages with a chance to convert; and the whole delivery layer is configuration — no custom pipeline team to fund. The pitch: revenue lift (faster load pickup) with a shrinking messaging bill.

Engagement/volume figures are modeled on the synthetic pilot; legal figures are statutory (TCPA 47 U.S.C. §227; FMCSA 49 CFR 395).

Dispatch Flow Control — presenter guide

What this dashboard is

A single screen showing the whole notification pipeline: Snowflake computes who should be told about which load (nine eligibility gates), Postgres carries realtime events, Hightouch Reverse ETL detects exactly what's new and delivers only that delta, and Twilio sends the SMS. Everything on screen is live data — the same views Hightouch reads.

Reading the flow chart

Red bands = compliance & safety suppressions (do-not-contact, no consent, driving, HOS-illegal). Amber = held, on purpose (quiet hours, waiting for a meal window, frequency caps, the trial gate). Green = flowing toward delivery. Click any band or node to see the actual drivers there and why. Click again to clear.

The buttons

Q & A you may get

Why does nobody get texted twice?
Hightouch diffs on a stable primary key (QUEUE_ID) and the message body is frozen at enqueue — a row can never look "changed", so it syncs exactly once. Prove it live: trigger a sync twice; the second run shows 0 added.
Why is the biggest red band "HOS-illegal"?
Most recommendations die because the load doesn't fit the driver's remaining legal drive hours (49 CFR 395). The warehouse refuses to advertise freight a driver can't legally haul.
Why do Twilio attempts fail?
By design: trial credentials + magic numbers mean every API call is real but delivery is refused at Twilio's gate. In a regulated channel, that's the last line of defense working. Swap production credentials and the identical rows go to real phones.
What's the promoter task for?
Log-based CDC reacts to data changes, not the clock. "Send at 3pm" writes nothing at 3pm — so a 1-minute job physically flips due rows to eligible; that UPDATE is the event.
Realtime vs perfect-timing?
Realtime = event-born (geofence, dispatch), seconds-to-a-minute. Perfect-timing = held for the driver's meal window or an active reply session, released in 1-minute batches, best load only.

Use-case checklist (ticks saved in this browser)

Good to know

Data refreshes: chart lineage is recomputed on demand (♻); the platform tiles poll every 5 s. Recompute is atomic — viewers never see empty tables. This page: hightouch.myorg.ai. Backend: systemd flow-viewer · data in Supabase VIEWER schema · full script in deck/DEMO_RUNBOOK.md.

Where every recommendation goes

Live lineage across all four platforms — click any band or node to see the actual records behind it.

Suppressed — compliance & safety, never sends Held — right message, wrong moment Flowing — on its way to delivery Hightouch mark — stopped upstream, never reaches Twilio

Presenter actions

Records

Click the chart to filter. Showing everything.

DriverLaneStageWhy Match strengthBest load / messageMatches