In freight, the inbox is the operation. Aide puts governed AI agents on it.
Aide's AI agents run on the shared inbox your team already uses, resolving status checks, quotes, documents, booking changes, and billing disputes end-to-end, with the shipment context behind every answer. Your ops desk gets out of the check-call business and back to exceptions and relationships.Powered by the Agent Governance Engine: every word and action is bounded by approved procedures, tested on your real threads, and logged to the load. Aide acts only when it is certain, and hands the rest to your team.Built for freight operations, front office to back
The same governed platform, configured to each desk's own intents, procedures, and rules.
Status, quotes, and carrier coordination on the two-sided inbox.
Entry status and document flows; determinations stay human-gated.
Multi-team ops desks: track-and-trace, billing, exceptions.
Agent and carrier inquiries recognized, enriched, and routed.
Dispatch, parts, service, and AR inboxes beyond freight proper.
International lanes and customs-adjacent flows, inside the rules.
Built for the emails actually in your inbox
Every high-volume freight intent, resolved end-to-end by the exact procedure your team approved for it, lane by lane. Aide responds instantly, acts on the shipment, and logs what it did.
Freight has hard lines. Aide treats them as blocking gates, not suggestions.
Sanctions screening, dangerous goods, customs determinations, liability concessions: some things an AI must never freelance. Aide is built so the hard gates block, the approved language executes verbatim, and rollout happens lane by lane: none, human-in-the-loop, or fully agentic, per intent.
Works with your existing stack
One click into the inbox you already run. Shipment context from your TMS and visibility stack. No migration, no replatforming, no engineering.
The natural home: live on the shared inbox and the marketplace integrations your ops desk already runs.
Resolves and updates tickets inside your existing workflows.
Grounds every answer in the account record you trust.
Reads the shipment, rate, and gate context your TMS and visibility tools push to the inbox.
Shipper and carrier replies over email and SMS, answered in seconds, day or night.
Frequently asked questions
Yes. Aide reads the live shipment context your visibility tools and TMS push to the helpdesk, so a status question gets the current milestone, the revised ETA, and the appointment state, not a tracking link. Industry research puts status checks at 30 to 45 percent of a broker or forwarder's inbound, which is why most teams automate this intent first.
It acknowledges the request instantly and drafts the quote from the rate context you connect, inside pricing bounds your team sets. It never invents a rate. Where you want a person on final numbers, the quote goes out human-approved; where a lane is fully governed, it goes out in minutes. Speed-to-quote wins bookings, and the first workable rate usually takes the load.
Those are hard lines, and Aide treats them as blocking gates rather than suggestions. Status lookups like entry state can automate; determinations such as HTS classification, valuation, dangerous-goods review, and denied-party screening always route to a person. The gate lives inside the procedure itself, and every action carries a trace.
No. A tracking-page chatbot answers what the tracking page already shows. Aide works the shared inbox where freight actually runs: it resolves status, quotes, documents, and disputes over email, executes the approved next action on the shipment, and hands anything outside its bounds to your team with context attached.
No, and that is not the goal. Aide absorbs the check calls and document requests so your people work the exceptions, the carrier relationships, and the accounts. The operation's knowledge compounds as it runs: every conversation feeds the intent taxonomy your team reads, and the role shifts from answering the same 1,500 emails to managing what actually needs judgment.
Shipment status and check calls, quote requests, document retrieval (BOLs, PODs, invoices, certificates), booking changes, exception notifications, billing and detention or demurrage disputes, and carrier or agent routing. Each intent is configured with your exact procedure, tested on your real threads, and deployed at the automation level you choose: none, human-in-the-loop, or fully agentic.
Aide runs inside the helpdesk you already use, and Front is the natural home for freight teams. Shipment, rate, and gate context flows in from your TMS and visibility tools, pushed to the inbox or connected via API, so every answer reflects the load as it is right now.
Aide is conversational AI for logistics that goes a step further: agentic AI. It converses naturally over email and chat, and it also acts: it pulls the POD, drafts the quote, updates the booking, and builds the D&D dispute case from gate timestamps. Answering questions is table stakes. Acting on the shipment is the difference.
Yes. Aide is SOC 2 Type II certified and GDPR compliant, and its model providers operate under zero-data-retention agreements. Every automated action is logged in the Action Trace. Security documentation is available at aide.app/security.
Most teams connect their helpdesk in a day and are live on their first intent within days. You start with shipment status, the biggest block in the queue, watch Aide handle it in the Agent Simulator on your own historical threads, and expand lane by lane as your ops leads sign off.
Get a demo for pricing.
Put governed AI agents on your freight inbox
Status, quotes, documents, and disputes resolved end-to-end on the stack you already run, governed by the rules you set.