Gmail for freight forwarders
Your work arrives as email. On Google Workspace that means Gmail, and it means sales@, ops@ and accounts@, where four people see a thread and each assumes another has it.
Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.
Gmail stays your mail system. The reply still leaves from it, on the same thread, in the approver's name.
- 01In a forwarding company the work arrives as email. On Google Workspace that means Gmail, and the shared addresses your customers already write to. Connect those mailboxes and FreighAI reads every conversation in them, does the work behind each one, and hands the right person a task with the reply written.
- 02Connects so FreighAI can read every conversation and send replies in your people’s names. Your team works in FreighAI, not in the inbox.
- 03Your team approves every reply before it sends. The approved reply leaves from your own Gmail, on the thread it arrived on.
- 04The access is your administrator's, not ours. Google's admin documentation says an app can be limited to “Specific Google data”, or set to “Blocked–App can't access any Google data”.
The enquiry sitting in sales@
Gmail is good at email. It was never asked to run a freight company.
A customer writes to sales@ at twenty to ten. Two pallets, Pune to Hamburg, ready Monday, packing list attached. Four people can open that mailbox and three assume somebody else has it. At four the customer writes again, asking whether anybody got the first one.
A forwarding business grows one shipment at a time. Every shipment brings more enquiries, more emails, more rates to find, more people to chase and more hand-offs between pricing, operations and accounts. Almost none of that work lives in a system. It lives in inboxes, browser tabs, WhatsApp and people’s heads. So the only way to handle more business has been to hire more people.
Google describes Gmail as “AI-powered, secure, and easy to use email”, with “professional email addresses at your domain”. True, and none of it the problem. Gmail delivers the message. It does not find the rate, notice the missing weight, chase the agent or decide whose job the enquiry now is.
- Which shared mailboxes has nobody owned since the last person left?
- When an enquiry needs pricing, operations and accounts, how often is it forwarded?
- When a pricer is on leave, who is watching the threads they were watching?
Your people stop living in the inbox
The mail does not move. The place your team works does.
FreighAI watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish.
It works out what each email is and what it needs, then takes the action that message calls for. It writes the reply, creates the task, and puts it in front of the right person in the right department, beside the original conversation. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
The email is only the start. The hours go on what follows it. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system. FreighAI talks to carriers, portals, your TMS and your accounting system itself. Nobody hops between websites to put an answer together.
| What arrives | Where it goes today | What FreighAI does with it |
|---|---|---|
| An enquiry at sales@ with a packing list | A mailbox four people watch and nobody owns | Spots what is missing in an enquiry and drafts the email asking for it. Suggests a price from what that customer paid on that lane before, within your margin rules. |
| “Where is my cargo?” | A browser tab, then a reply written from memory | Answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. |
| A carrier bill as a PDF at accounts@ | Checked by hand, or not at all | Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked. |
- An enquiry at sales@ with a packing list
- Where it goes today
- A mailbox four people watch and nobody owns
- What FreighAI does with it
- Spots what is missing in an enquiry and drafts the email asking for it. Suggests a price from what that customer paid on that lane before, within your margin rules.
- “Where is my cargo?”
- Where it goes today
- A browser tab, then a reply written from memory
- What FreighAI does with it
- Answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval.
- A carrier bill as a PDF at accounts@
- Where it goes today
- Checked by hand, or not at all
- What FreighAI does with it
- Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked.
- 01GmailThe mail arrives where it always did
- 02ReadThe conversation, not one message
- 03The legworkRate cards, the carrier, your agents
- 04TaskThe right person, thread beside it
- GATEYour team approves
- 06Sent from your GmailSame thread, in the approver's name
- 07Your TMSThe record goes where you keep records
Keep your TMS for the records. FreighAI runs the work around them.
Gmail, end to end
Nothing is taken. Google says an app can be limited to “Specific Google data—Can request data access only to scopes that you specify”. Your administrator makes that setting.
Nobody forwards anything to a robot address. In Google's wording, “Whenever a mailbox update occurs that matches your watch, your application receives a notification”.
FreighAI works out what each email is and what it needs, then takes the action that message calls for. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system.
It writes the reply, creates the task, and puts it in front of the right person in the right department, beside the original conversation. Whoever owns that kind of work.
Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. Google's documentation describes sending “directly using the messages.send method” or “from a draft”, and a reply stays grouped in its thread when the “Subject headers match”.
What your team can do once Gmail is connected
It watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish. Four jobs, four addresses.
It reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. A packing list is a packing list, spreadsheet or photograph.
It spots what is missing in an enquiry and drafts the email asking for it. Emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply.
It answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval.
Your people work in FreighAI, not in the inbox. Gmail keeps carrying your mail. Your team stops living inside it.
need DHL quote Gurugram → Ajman, 72kg, by Friday. urgent pls 🙏
Hi Marco — DHL Express, AED 425 + AED 35 handling. ETA Thu·18:00, valid 24h. PDF attached.
Approved by a person. Sent from your own Gmail.
The screen the pricer opens. The customer's thread on one side, what FreighAI went and found on the other, the reply waiting for a name on it.
- The thread stays a threadThe reply is grouped into the conversation it answers
- It goes out in their nameYour team approves. They do not compose, forward, file or chase. The reply goes out in their name.
- The chasing carries onFollow-ups, chasers and reminders happen on their own, on the same conversation.
What connecting it involves
- 01
Decide which mailboxes are in scope
Most forwarders have more shared addresses than they remember. sales@, quotes@, ops@, docs@, accounts@, and two created for a customer in 2019. List them and name who is accountable for each.
- 02
Your administrator approves the access
This is a Google Admin console decision and it stays one. Google's guidance to developers is to “choose the most narrowly focused scope possible”, so the request names the scopes the agreed workflows need and nothing else.
- 03
Say who owns which kind of email
An enquiry belongs to pricing. A booking amendment belongs to operations. A carrier bill belongs to accounts. One session writes down calls currently made in somebody's head. Work passes from pricing to operations to accounts with the email and everything it found attached. Nobody forwards it, re-keys it or asks for an update.
- 04
Agree what a person still has to see
Your team approves every reply before it sends. What differs is who that person is for each kind of reply, and who covers on a Friday evening.
- 05
Run it on one shared mailbox first
Keep answering as you do now and let FreighAI work the same threads in parallel. Then compare what it read out of each email with what your own pricer read. We scope the first workflow, integration requirements and implementation plan with your team.
What the Gmail connection does not do
Worth knowing before you plan around it.
- FreighAI does not become your mail system. Gmail keeps delivering, storing and filtering your mail as it does now. Retention, archiving, spam handling and anything your administrator has configured stay with Google.
- Only the mailboxes you connect are read. A personal Google account is not part of it, and neither is a shared mailbox nobody put on the list.
- The access belongs to your administrator. Google's settings run from “Trusted—Can access all Google services” to “Blocked–App can't access any Google data”. That control can be narrowed or removed without asking us.
- Nothing sends on its own. Your team approves every reply before it sends. A reply that is ready at two in the morning waits.
- An email that does not say enough is still an email that does not say enough. Nothing is guessed. Spots what is missing in an enquiry and drafts the email asking for it.
- Gmail is not your record. Keep your TMS for the records. FreighAI runs the work around them. Direct customs filing and duty lookup, statutory books such as bank reconciliation, customer self-service portals, and full warehouse and fleet management stay in the system you already run.
What stays in Gmail, what moves into FreighAI, what never leaves your own system
A mail connection earns its keep when your team can say, without looking, which side of it each thing lives on.
Your customers keep writing to the same addresses and notice nothing except a faster answer. Your team stops spending the day reading and forwarding.
| What it is | Where it lives | What the connection adds |
|---|---|---|
| The mail itself | Gmail, on your own domain, exactly as today | The conversation is read where it sits |
| The work behind the answer | Browser tabs, phone calls and somebody's memory | Pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system. |
| The reply | Leaves from your Gmail, on the same thread | Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. |
| The job and the books | Your own system, and they stay there | A won quote becomes a job on its own, fully filled in. |
- The mail itself
- Where it lives
- Gmail, on your own domain, exactly as today
- What the connection adds
- The conversation is read where it sits
- The work behind the answer
- Where it lives
- Browser tabs, phone calls and somebody's memory
- What the connection adds
- Pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system.
- The reply
- Where it lives
- Leaves from your Gmail, on the same thread
- What the connection adds
- Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
- The job and the books
- Where it lives
- Your own system, and they stay there
- What the connection adds
- A won quote becomes a job on its own, fully filled in.
Your customers and agents, writing to the addresses they already have.
Reads the conversation, does the work behind it, creates the task, drafts the reply, waits for approval.
The job, the documents and the books stay where they are.
Almost nobody runs on email alone
The enquiry arrives in Gmail, the customer chases on WhatsApp, and half your agents reply from Outlook. Connecting one channel and leaving the others out splits one piece of work between two places, which is where it is lost.
Common questions
Do we have to move off Gmail?
No. Gmail keeps carrying your mail on your own domain. What changes is where your team spends the day. Your people work in FreighAI, not in the inbox.
Does the customer see anything different?
No. The reply arrives from your own address, in the thread they wrote to. Google's documentation describes how a reply stays grouped in a conversation, through matching “Subject headers” and “In-Reply-To headers”.
What access are you asking for, and can we take it away?
The request is specific, not general. Google's scope list separates viewing “your email messages and settings” from sending “email on your behalf”, and which is needed depends on the workflows you switch on. Your administrator can later set the app anywhere from “Trusted” to “Blocked–App can't access any Google data”, without asking us.
We already use a Google Group as a shared inbox. Do we still need it?
It does a different job. Google's Collaborative Inbox lets a member “assign responsibility for a conversation to yourself or another group member”, which settles who answers. It does not price the lane, chase the agent or draft the reply.
What about the mail that is not an enquiry?
Most of a forwarder's inbox is not enquiries. It works out what each email is and what it needs, then takes the action that message calls for. A booking confirmation, an arrival notice and a carrier bill each call for something different, and each goes to the department that handles it.
- Google Workspace — Gmail for business: “AI-powered, secure, and easy to use email”, with “professional email addresses at your domain”verified 2026-09-03
- Google for Developers — Gmail API push notifications: “Whenever a mailbox update occurs that matches your watch, your application receives a notification message describing the change”verified 2026-09-03
- Google for Developers — Sending email: “directly using the messages.send method” or “from a draft”; a reply is grouped into a thread when the “Subject headers match”verified 2026-09-03
- Google Workspace Admin — Control which apps access Google Workspace data: “Specific Google data—Can request data access only to scopes that you specify”, through to “Blocked”verified 2026-09-03
- Google for Developers — Choose Gmail API scopes: “choose the most narrowly focused scope possible”; viewing “your email messages and settings” is a separate scope from sendingverified 2026-09-03
- Google Workspace — Collaborative Inbox: “You can assign responsibility for a conversation to yourself or another group member”verified 2026-09-03
Everything here about how Gmail and Google Workspace behave comes from Google's own published material on the date checked. Google's pricing, storage and quota figures are deliberately not repeated.
Open sales@ and pick the messiest thread in it
One that ran a week, went round three people and still ended with somebody asking for the weight. We will show what would have been read out of it, whose task it would have been, and where a person still decides.