Communication channels
Email, phone, SMS, and chat — inbound starts the work, the reply goes back on the same thread.
- Replies on the same thread
- Every exchange on the load
- Nights and weekends too
One load, every channel that touched it
A tender arrives by email, a pickup is confirmed on a call, the driver is texted, and the reply goes back on the original thread. All of it lands on the same load.
- email
Northline sends a tender for Laredo to Memphis
- phone
Voice agent confirms Friday 6 AM pickup with the carrier
- sms
Driver gets the appointment window
- email
Reply goes back on the original thread
The channels freight already uses
Email, phone, SMS, and chat start the work and carry the reply. Nothing is a notification bolted on the side.
Shared inboxes are watched. A tender, rate confirmation, or status question starts a job with the full thread attached.
Voice and SMS
Agents place and answer calls, and text when nobody picks up. Recording and transcript stay on the load.
Chat
The same agent, with the same load in front of it, in Teams, Slack, WhatsApp, or a web widget.
One trail on the load
Every message, call, transcript, and attachment is written to the load it belongs to — not left in someone's inbox.
Connecting a channel
The same path for a mailbox, a phone number, or a chat app.
Connect it
Authorize the inbox, number, or chat app. Each channel is scoped to your company and the team that owns it.
Say what starts a job
Sender, subject, number, or keyword decides which workflow handles the message and which agent picks it up.
Go live
Inbound starts the work. The reply leaves on the same thread, and the exchange is saved to the load.
What we connect
Whichever inbox, number, or chat app you already run. These are examples, not a certified partner list.
Connected through the provider where one exists, and plain IMAP or SMTP where it does not — for example:
Your own numbers, with recording and transcript attached to the load.
The same agent and the same load, on whichever surface the person is already on — for example:
What your team stops chasing
Most freight work arrives as a message from someone outside your systems.
Inboxes stop being queues
Tenders, check calls, and status questions are handled as they arrive, instead of waiting for someone to open the shared inbox.
Nights and weekends still get answered
After hours uses the same channels and the same rules, so a late tender does not sit until morning.
Handoffs keep the history
The next person on the load reads the calls, emails, and documents in one place, instead of reconstructing them.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.