Unified Communications
Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again.
From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24
What happens on its own.
The work nobody does. These run in the database rather than the browser, which is why they still happen when someone forgets, closes the tab, or was never told they were supposed to.
Every message is threaded for you
A trigger on the message table runs before every insert: it derives the counterparty from the sender (inbound) or the recipient (outbound), matches on the last ten digits of the phone (so, and are one person) or on a lowercased email, finds
The thread's summary line maintains itself
The same trigger sets, stores the first 120 characters as the preview, stamps on inbound only, adds one to on inbound only, back-fills the driver id and counterparty name if they were unknown, upgrades an UNKNOWN counterparty to DRIVER, and
A closed thread reopens itself when the other side speaks
RESOLVED flips back to OPEN on any inbound message ().
The load's Journey gets a COMMS entry per message
Written by a second trigger, deduped by message id, and wrapped so that a failure raises a warning and lets the message write succeed — a timeline projection must never cost a driver's message ().
What you can do here.
Every item below is live in production today. Anything not yet built is listed further down rather than left out.
What we haven’t built here — by design.
Publishing this is the point. Unified Communications ships 36 capabilities today; these 3 are not built yet, and you should know that before a sales call rather than after one.
| Capability | Status |
|---|---|
| Resend a failed message | Not built |
| Trip / Manifest context card | Not built |
| Bulk actions on threads | Not built |