.svg)
GmailMailbox syncLimoSphere CRM
A shared inbox for chauffeur and limousine operators. Connect your business mailbox, phone numbers and messaging accounts, and every customer conversation lands in one place your whole team can work from — instead of scattered across personal inboxes and handsets.
Shared team inboxEmail, SMS, WhatsApp & callsAI drafts the booking
Channels
Connect what your customers already use.
Bring your existing mailbox and numbers in as they are. Nobody has to learn a new address or change how they reach you. Facebook Messenger and Instagram DMs are next.
GmailMailbox sync
RingCentralCalls & SMS
TwilioSMS delivery
WhatsAppCustomer chat
MessengerComing soonOne customer, one history
The whole conversation, in order.
A passenger emails for a quote, texts a change on the way to the airport, then calls when the flight lands. Those are not three separate enquiries — they are one job, and your team should be able to read them as one thread.
- Threaded properly — replies stay attached to the original mail rather than starting a new chain in the customer's inbox.
- Nothing arrives twice — duplicate deliveries are recognised and dropped, so a thread never doubles up.
- Calls included — inbound and outbound calls log against the same customer, with recordings.
- Live for everyone — new messages appear for every agent watching, without a refresh.
Email
Do you have a sedan for a JFK pickup on the 14th at 6am?
Email
We do — sending you a quote for that window now.
SMS
Flight changed, can we move it to 7:30?
Call
Inbound call · 2m 41s · recording attached
What it does
Built for the way a dispatch office actually works.
One inbox for the whole team
Customer mail stops living in one person's mailbox. Every agent sees the same threads, so nobody forwards a booking question to find out who already answered it.
Every channel, one timeline
Email, SMS, WhatsApp, Telegram and phone calls thread into a single history per customer — the same passenger, whichever way they got in touch. Messenger and Instagram join the same timeline when they land.
Assignment and ownership
Assign a conversation to an agent, watch it move through open, pending and resolved, and see what is still waiting on a reply.
Labels and saved replies
Tag threads by what they are — quote request, complaint, corporate account — and answer the repeat questions with canned responses instead of retyping them.
Calls in the record
Inbound and outbound calls are logged against the customer with their recordings, so the phone conversation sits beside the email trail.
Tied to your dispatch data
Contacts resolve against the customer records your dispatch board already uses, so a conversation opens next to the person's booking history.
Assisted replies
An optional assistant drafts first responses to routine questions, with your team reviewing before anything is sent.
Notifications that follow you
Per-agent notifications with mutes and mobile push, so an urgent thread reaches the right person without paging the whole office.
Reply from your own address
Replies leave as your business address and thread correctly in the customer's mail client — not as a no-reply relay the customer cannot answer.
AI in the inbox
It reads the enquiry and starts the booking.
Most of what lands in a limo company's inbox is a trip waiting to be typed into a system. LimoSphere CRM does that part for you — and no other platform in this industry does.
Message to booking
Email
“Need a sedan from JFK T4 to Midtown on the 14th, landing 6am, three of us with luggage.”
Draft reservation
- Pickup
- JFK Terminal 4
- Drop-off
- Midtown, Manhattan
- When
- 14th, 06:00 arrival
- Passengers
- 3 · luggage
- Vehicle
- Business sedan
A message becomes a draft booking
Unique to LimoSphereAn enquiry arrives — “JFK pickup, the 14th, 6am, three passengers” — and the assistant reads it into a draft reservation with the pickup, time, passenger count and vehicle class already filled in. Your dispatcher checks it and confirms. Nobody retypes a trip out of an email.
Replies drafted for review
Routine questions — availability, a rate, a confirmation, a running-late note — come back as a suggested reply in your own tone. Your agent edits or sends. Nothing leaves without a person approving it.
A chatbot that answers after hours
Turn the assistant on for a channel and it handles the first response overnight and at weekends, then hands the thread to a human the moment it is out of its depth or the customer asks for one.
It knows your operation
The assistant works against your own data — your rates, vehicle classes, service area and the customer’s booking history — so a quote it drafts is one you could actually honour, not a generic guess.
A person confirms every booking and approves every reply — the assistant drafts, it does not dispatch.
AI chatbot
And before the enquiry is even an enquiry.
Put the same assistant on the front of your website. It answers from what you have taught it, prices the trip against your own rate engine, takes the booking — and everything it said is a conversation in the inbox above.
1A visitor asks
2Every vehicle, priced live
3Booked — and in your CRM
Answers in your words
You write the questions your team keeps answering, and their answers. The assistant uses your wording rather than a paraphrase of it.
Quotes from your rates
Every active customer-facing vehicle type in one reply, priced through the same engine as your booking website — zone rules, stops and minimum hours included.
Hands over cleanly
It moves the thread to your team the moment it should — and any public reply from an agent takes the conversation over for good.
Campaigns
Email campaigns that go out from your own mailbox.
Write once, send to a segment of the customers already in your CRM, and pick which connected mailbox it leaves from. Every address is tracked on its own — shared inboxes in this industry do live chat, SMS and WhatsApp campaigns, but not email, and not from a sender you choose.
Spring corporate rate card
from sales@yourbrand.comFinished1,240Sent
512Opened
14Bounced
8Failed
Eleanor Whitfield e.whitfield@northwind.coOpened
Marcus Webb m.webb@atlasgroup.comDelivered
Priya Raghavan priya@vertexpartners.ioBounced
Send from any mailbox you have connected
Unique to LimoSphereChoose the sender per campaign — your main business address, a second domain you also run, or an SES SMTP relay set up for volume. The campaign goes out from that mailbox, so replies land in an inbox your team already works, not a no-reply relay.
Results per recipient, not a batch total
Sent and failed are recorded against every address individually. Opens are counted with a tracking pixel, and bounces are matched back to the recipient automatically from the DSN reports your mail server returns — so a dead address is a name you can act on, not a number in a summary.
Nobody is mailed twice
Recipients are claimed atomically as the run works through the list. If a send is retried or two workers overlap, the same customer still receives the campaign exactly once.
Paced, watched, and safe to stop
The run is throttled rather than fired all at once, and a watchdog catches a stall instead of leaving a half-sent campaign. If the mailbox credential fails mid-run, the campaign aborts with the remaining audience intact — fix the connection and send to who is left.
We report what we can actually see. Whether a message landed in the inbox or the spam folder is not something any sender can measure without a dedicated email service provider, so we do not claim a figure for it.
Google accounts
How LimoSphere CRM works with Gmail.
Connecting a Google mailbox is what turns it into a shared inbox. Here is exactly what that involves, what we access, and what we will never do with it.
1You connect the mailboxAn administrator adds an inbox in LimoSphere CRM and signs in with Google. Consent happens on Google's own screen — we never see or store your password.
2Incoming mail becomes conversationsNew mail arriving in the connected mailbox is read over IMAP and placed in your shared inbox, threaded against the customer who sent it.
3Your team replies as youAgents answer from inside LimoSphere CRM and the reply is sent over SMTP from your business address, keeping the customer's thread intact.
What LimoSphere CRM does
- Read mail from the connected mailbox so it appears in your shared inbox
- Send the replies your agents write, from your own business address
- Store message content, headers and attachments to display the conversation
- Read your account's email address, only to confirm which mailbox granted consent
What it never does
- Sell or rent Google user data to anyone, under any circumstances
- Use Google user data for advertising, profiling or resale
- Use Google user data to train generalized or generative AI models
- Let LimoSphere staff read your mail, except where you ask for support or safety requires it
Limited Use disclosure. LimoSphere CRM requests the
https://mail.google.com/ scope because Google's IMAP and SMTP interfaces accept no narrower permission — there is no read-only or send-only alternative for IMAP access. LimoSphere's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can review the detail in our CRM Privacy Policy and revoke access at any time from your Google Account permissions.Security
Your mailbox stays yours.
No passwords held
Google and Microsoft mailboxes connect by signing in with the provider. LimoSphere CRM receives a revocable access token, never your password.
Encrypted at rest and in transit
Provider credentials and tokens are encrypted with AES-256-GCM. Traffic between your browser, LimoSphere and your mail provider is TLS-encrypted throughout.
Isolated per operator
Every record is scoped to the operator that owns it. One company's conversations are never queryable from another company's workspace.
Revocable in one click
Disconnect the inbox in LimoSphere CRM, or revoke access from your Google Account permissions page. Either stops the sync immediately.
Frequently Asked Questions
LimoSphere CRM is a shared team inbox for chauffeur, limousine and black-car operators. It brings every customer conversation — email, SMS, WhatsApp, Telegram and phone calls — into one timeline per customer, so any dispatcher or agent on your team can pick up a thread without forwarding it around. It is part of the LimoSphere platform and connects to the same customer records your dispatch board uses.
Gmail and Google Workspace, Microsoft 365 and Outlook, and any mailbox that speaks standard IMAP and SMTP. Google and Microsoft mailboxes connect by signing in with that provider, so LimoSphere CRM never asks for or stores your email password.
Yes — this is the part no other platform in this industry offers. When a customer emails or messages a trip request, the assistant reads it and produces a draft reservation with the pickup, drop-off, date, time, passenger count and vehicle class already filled in, using your own rates and service area. A dispatcher reviews the draft and confirms it. The assistant drafts; a person always dispatches.
It drafts replies to routine questions in your own tone for an agent to review or edit, and it can run as an after-hours chatbot on a channel, answering first-line questions overnight and handing the conversation to a human as soon as it is out of its depth or the customer asks for one. Nothing is sent to a customer without a person approving it, unless you deliberately enable the chatbot for that channel.
To act as a shared inbox, LimoSphere CRM has to read the mail arriving in your business mailbox and send replies from that same address. Reading incoming mail is what puts a customer's email into the shared inbox where your team can see and assign it; sending is what lets an agent reply from your business address instead of their own. Both use Gmail's standard IMAP and SMTP interfaces.
LimoSphere CRM requests the Gmail scope https://mail.google.com/ together with your basic profile email address. The Gmail scope is required because Google's IMAP and SMTP interfaces accept no narrower permission — there is no read-only or send-only alternative for IMAP access. The email scope is used only to confirm which mailbox granted consent, so the connection binds to the right address.
Message content, headers and attachments from connected mailboxes are used solely to display customer conversations inside your own LimoSphere workspace and to send your replies. LimoSphere's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never used to train generative AI models.
Yes. Disconnecting the inbox in LimoSphere CRM deletes the stored credentials for that mailbox and stops all further sync. You can also revoke LimoSphere's access at any time from your Google Account permissions page at myaccount.google.com/permissions, which immediately invalidates the tokens.
Data is stored on LimoSphere's managed infrastructure and is isolated per operator, so one company's conversations are never visible to another. Provider credentials and access tokens are encrypted at rest with AES-256-GCM, and all traffic between your browser, LimoSphere and your mail provider is encrypted in transit with TLS.
Yes. Calls and SMS through RingCentral or Twilio, plus WhatsApp and Telegram messages, thread into the same customer timeline as email. A customer who emails on Monday and calls on Tuesday is one conversation history, not three disconnected records.
LimoSphere CRM is built for operators already running the LimoSphere platform — it shares the same customer records, permissions and team accounts as your dispatch system. Talk to sales if you want to discuss using it alongside an existing setup.
See it on your own mailbox
Book a walkthrough and we will connect a test inbox with you, so you can watch a real customer email land in a shared conversation before you decide anything.
