RideDesk
RideDesk Mail

The email system your dispatch desk deserved all along

Every confirmation, invoice, pay link and reply your operation sends — from your own domain, fully authenticated, tracked to the open, and answered in the same panel the booking lives in. RideDesk Mail runs on RideDesk’s own EU mail infrastructure in Frankfurt, so there is no mailbox provider to pay, no SMTP relay to configure and no mail server to babysit.

And because your emails carry Gmail’s structured-data markup, a booking confirmation can appear in your customer’s inbox as an order card with the trip details up front — the treatment Gmail reserves for senders it can read and trust.

Included inFree ForeverFreePro$99/moEnterprise$199/moFull pricing

  • Your own domain, properly authenticated

    Verify your domain once and every email is signed with DKIM (RSA-2048), aligned SPF and DMARC — mailed-by and signed-by both read as YOUR business. Setup is guided: a downloadable zone file you import into Cloudflare or any zone-file-capable DNS host in one go, or a copy-paste record table.

  • Sent, delivered, opened, clicked

    Every message carries live delivery chips in the panel: delivered, opened, clicked, bounced or complained. You stop wondering whether the customer saw the pay link — you can see it, next to the booking, the moment it happens.

  • Unlimited mailboxes on your domain

    Receiving is catch-all: bookings@, info@, accounts@, a new address for a campaign — every address at your domain lands in the one org inbox, filed into alias folders, with no per-mailbox fee and nothing to create first. Your organisation never misses an email sent to its domain.

  • Gmail order cards, built in

    Booking confirmations, invoices and rental reservations embed schema.org Order, Invoice and Reservation markup — the structured data Gmail uses to render order cards and surface what matters. Your emails are built for that treatment from day one; plain-text competitors simply are not eligible.

  • Every template is yours to edit

    Booking received, confirmed, invoice, pay link, reminders, review requests — every system email is an editable template in English and German, with a live preview, click-to-insert variables and your own header, footer and logo. The details table and payment button stay pixel-perfect while the words become yours.

  • Replies land next to the booking

    Inbound mail is parsed, threaded into conversations and matched to the booking it belongs to. Reply from the panel — from any address on your domain — with attachments both ways, folders, search and Trash, and an AI draft that already knows the customer’s ride and your cancellation policy.

What the inbox actually does

A shared team inbox built for dispatch work, not a webmail clone.

  • Conversation threads

    Messages group into conversations — your sent replies and the customer’s answers in one thread, with the reply always going out from the alias the customer wrote to.

  • Send-as any address

    On a verified domain the composer offers any local-part as the From address: reply as bookings@, invoice as accounts@, campaign as offers@ — no mailbox setup, validated server-side.

  • Alias folders and per-role access

    Each receiving address is a folder. Owners can restrict who sees which alias — accounts@ for the office, bookings@ for dispatch — enforced on lists, counts, search and notifications alike.

  • Instant new-mail alerts

    Inbound mail triggers a push notification in seconds — not on the next poll. Your own outgoing system mail and spam are filed but never wake anyone up.

  • Filtered before you see it

    Virus-positive mail is dropped outright; suspected spam is flagged, not deleted — a mislabelled real enquiry is still there to rescue.

  • AI reply drafts

    One click drafts a reply that already knows the sender’s most relevant booking and — for cancellation requests — your policy and what the refund assessment says, without ever inventing a price.

Under the hood

The parts you never have to think about again.

  • EU infrastructure

    Sending and receiving run on RideDesk’s own dedicated mail infrastructure in Frankfurt, Germany — EU data residency by default. Your mail does not route through a third-party newsletter tool.

  • A shared address on day one

    Before your domain is verified you already send from your company name at mail.ridedesk.app — a warmed, authenticated domain — so email works from the first minute of the account.

  • Bounce and complaint handling

    Hard bounces and complaints are captured per message and surfaced in the thread, so a mistyped address is visible immediately instead of a silent black hole.

  • No migration required

    Keep your existing mailbox if you like — RideDesk also speaks plain SMTP/IMAP. RideDesk Mail is the upgrade path, not a lock-in.

Questions operators ask

Do I need to move my existing email hosting?

Only if you want receiving in the panel on your own domain — that repoints the domain’s MX records, so it suits a domain without existing mailboxes or one you dedicate to operations. Sending on your own domain needs no MX change at all, and you can also run RideDesk Mail purely on the shared address.

What makes emails show up as order cards in Gmail?

RideDesk embeds schema.org structured data (Order, Invoice, Reservation) in the relevant transactional emails, which is the format Gmail reads to render rich cards and highlights. Gmail applies the treatment per sender based on its own trust signals — consistent volume and clean sending, which authenticated own-domain mail is exactly designed to build.

Is there really no limit on mailboxes?

Receiving is catch-all on your verified domain, so every address that exists — or that you invent on the spot — is delivered and filed. There is no mailbox count, no per-seat mail fee, and send-as works for any address on the domain.

Can different staff see different mailboxes?

Yes. Alias access is set per role, and it is enforced at query level — lists, unread counts, search, attachments and alerts all respect it. Restricted mail notifies only the roles allowed to read it.

Which plans include RideDesk Mail?

Pro and Enterprise. The free plan sends through your own SMTP mailbox instead — every template and the inbox UI work the same, so upgrading changes the engine, not your workflow.

More of the product

See it on your own operation

Start on the free plan, set up your rates, and switch on RideDesk Mail when you are ready — every plan and price is public.