Ellie is a browser agent. She runs on top of the web tools your team already opens — your TMS, inbox, phone, load boards, and compliance sources — instead of asking you to migrate to one more platform.
Traditional software connects through brittle middleware and APIs that break when a TMS updates its UI. Ellie skips that. She deploys as a Chrome extension and works directly on the web pages your reps already use, the same way a person would, so there is no fresh integration project to stand up and nothing to reconcile.
No middleware. She acts on the page directly, so a TMS UI change doesn't break her.
No new system. Reps stay in one workflow instead of switching between an AI site and the TMS.
Fast to live. Install the extension, connect the tools that matter, set the rules, go.
Ellie is system-agnostic on the web side. If your team works in it through a browser, Ellie works in it too.
▦
TMS platforms
Cloud, web-based transportation management systems. She reads load details and works inside them.
◎
Load boards
Sources capacity from the boards your team already searches.
Email & inbox
Runs carrier outreach and works the negotiation thread from the inbox.
☎
Phone & voice
Handles inbound carrier calls and outbound voice outreach.
❝
SMS
Reaches carriers by text in parallel with email and voice.
✓
Compliance & FMCSA
Checks MC, DOT, authority, safety, insurance, and fraud signals automatically.
Drop in the TMS platforms, load boards, and tools your customers run today.
Don't see yours? If your team opens it in a browser, Ellie can run on it.
Envoy is SOC 2 Type II compliant and aligned to all Trust Services Criteria. Ellie runs inside your existing access and permissions, and the Carrier Context Graph she builds belongs to you, not to a vendor.
🛡
SOC 2 Type II
Aligned to all Trust Services Criteria.
🔒
Runs in your permissions
Ellie works inside the access your team already has.
Your data, your graph
The Carrier Context Graph belongs to you.