Emails and notifications
This is the full catalogue of messages direct.eat sends. For choosing which ones reach you, see Notification settings. You can preview every email template in Settings → Notifications → Email templates.
Status in the tables:
- Sent means it goes out today.
- Planned means the template is built but nothing sends it yet.
How messages are sent
Section titled “How messages are sent”| Channel | Today |
|---|---|
| Sent. Order emails to diners come from your shop’s name, with your logo and colours, and replies go to your shop when you’ve verified a reply-to address. Emails to your team come from direct.eat | |
| In-app | Sent. The bell in the dashboard, with an unread count |
| Push to phones and browsers | Planned for real devices. The dashboard records each push that would be sent |
| SMS and phone calls | Planned. Missed-order texts and calls are worked out and logged at the right times, but not yet delivered to real phones |
Service emails to diners never contain marketing. Every email has a plain-text version. Marketing emails (campaigns and automations) are covered in Campaigns and consent.
Emails to diners
Section titled “Emails to diners”Sent from your shop, to the email the diner gave at checkout.
| When | Status | |
|---|---|---|
| Order received | The order is placed (paid, or cash confirmed). Includes the full receipt. This is the diner’s durable confirmation | Sent |
| Order accepted | You accept the order, with the ready time or delivery window | Sent |
| Ready time changed | The ready or arrival time moves by 5 minutes or more (at most 3 times per order) | Sent |
| Order delayed | The order runs 10+ minutes past its promised time, or you mark it delayed | Sent |
| Ready to collect | You mark a collection order ready | Sent |
| Out for delivery | You mark a delivery order out for delivery | Sent |
| Delivered | The delivery is completed. If a delivery failed, the diner gets an email explaining what happened instead | Sent |
| Order rejected | You reject the order, or it was auto-cancelled because nobody accepted it. Says whether and how much is refunded | Sent |
| Order cancelled | Cancelled after acceptance, with the refund amount and timing | Sent |
| Message from the restaurant | You send a message or quick reply in the order thread. Messages within 60 seconds are batched into one email | Sent |
| Refund issued | A full, partial or item refund is created | Sent |
| Not confirmed yet: keep waiting or cancel | You haven’t accepted after 8 minutes. The diner chooses to keep waiting or cancel | Sent |
| Review request | After collection or delivery (60 minutes after hand-over by default), plus at most one reminder after 2 days. Never offers an incentive | Sent |
| Loyalty reward ready | A loyalty member’s balance now covers a reward | Sent |
| Gift card received | A gift card or goodwill credit is issued to this email address | Sent |
| Loyalty programme changing | 30 days’ notice before a change that reduces the value of the loyalty card | Sent |
| Diner sign-in code | A diner signs in or saves their details on your storefront | Sent |
| Receipt / simplified VAT invoice | On collection or request | Planned |
| Full VAT invoice | The diner asks for a full VAT invoice | Planned |
| Pre-order reminder | 2 hours before a pre-order placed more than 12 hours earlier | Planned |
| Feedback request | 60–90 minutes after collection | Planned |
| Diner email change, account deleted, data export ready | Account changes by the diner | Planned |
Diner push and texts
Section titled “Diner push and texts”When a diner allows notifications on the tracking page, they also get a push for: received, accepted, cooking, ready, out for delivery, delivered or collected, rejected, cancelled, ready time changed, new messages, and the keep-waiting-or-cancel choice. Text messages (where you’ve switched them on and the diner gave a mobile) are for ready time changes, ready, out for delivery, rejected and cancelled. Both are planned (see above).
Messages to your team
Section titled “Messages to your team”Orders and the kitchen
Section titled “Orders and the kitchen”These follow each person’s notification settings. Critical events always reach someone: the owner can’t switch off every channel for them unless a verified on-call contact covers the shop.
| Event | What it means | Channels | Default |
|---|---|---|---|
| New order | Kitchen devices ring for every order. Optional push to your phone | In-app, push | Managers: in-app and push. Others: in-app |
| Order not accepted (critical) | An order is still waiting after the alarm. Part of the missed-order ladder | In-app, push, SMS | Owner: all three. Admins and managers: in-app and push |
| Missed order cancelled (critical) | Nobody accepted in time, so it was cancelled and refunded. Email: “Missed-order alert” | In-app, push, email, SMS | Owner: all four. Admins: in-app and email. Managers: in-app, push and email |
| Customer message | A diner wrote in the order thread and nobody has read it for 3 minutes | In-app, push | Owner and managers: in-app and push |
| Customer cancelled | A diner cancelled before you accepted | In-app, push | Managers: in-app and push. Others: in-app |
| Kitchen offline (critical) | No kitchen device or printer is connected while you’re open | In-app, push, SMS | Owner: all three. Admins and managers: in-app and push |
| Ordering paused automatically (critical) | Online ordering paused because the kitchen went dark. Email: “Kitchen offline: ordering paused” | In-app, push, email, SMS | Owner: all four |
| Ordering resumed | A device reconnected and ordering started again | In-app, push | Owner and managers: in-app and push |
| One device offline | A tablet or printer dropped out but another path still works | In-app, push | Owner and managers: in-app and push |
| Printer problem | Paper out, cover open or printer offline during opening hours | In-app, push, email | Owner and managers: in-app and push |
| Allergy issue | A diner reports an allergy problem with an order | In-app (urgent), push, SMS to on-call contacts | Owner, admins and managers |
The missed-order ladder itself (alarm, reprint, push, calls and texts at set times) is explained in Alerts and escalation. Calls go to the shop phone, then on-call contacts; texts to on-call contacts carry a one-tap accept link.
Payments
Section titled “Payments”| Event | Channels | Status |
|---|---|---|
| Payout or Stripe problem | In-app, push, email | Planned (needs live Stripe) |
| Card dispute, with deadline reminders 5 days and 1 day before | In-app, push, email | Planned (needs live Stripe) |
| Refund problem | In-app, push, email | Planned (needs live Stripe) |
| Stripe setup incomplete / Stripe action needed | Planned |
Reports
Section titled “Reports”| Who | When | Status | |
|---|---|---|---|
| Daily summary | Owner (others can opt in) | 30 minutes after closing: orders, takings, anything that went wrong, and the AI headline if switched on | Sent |
| Scheduled report | Whoever you choose | Daily, weekly or monthly, as you set in Reports | Sent |
| Order copy | Your chosen address | Every order, if you switch on “email me a copy”. Not a replacement for alerts | Sent |
| Bank holiday hours reminder | Owner | 30 days before a bank holiday | Planned |
Your account, team and billing
Section titled “Your account, team and billing”| Who | When | Status | |
|---|---|---|---|
| Verify your email | You | Signing up | Sent |
| Sign-in link / code | You | You ask for a sign-in link | Sent |
| Password reset | You | You ask to reset your password | Sent |
| Confirm email change | You | You change your email address | Sent |
| Confirm it’s you | You | A code before a sensitive change | Sent |
| Team invitation | The person invited | An owner, admin or manager invites someone. Link valid 7 days | Sent |
| Trial ending | Owner and admins | 7 days and 2 days before your free trial ends | Sent |
| Payment failed | Owner and admins | A subscription payment fails, then reminders on days 3, 7 and 14 | Sent |
| Invoice paid | Owner | A subscription invoice is paid | Sent |
| Cancellation confirmed | Owner | You cancel, with the end date, export pack link and domain steps | Sent |
| Subscription ended | Owner | The trial ended without a card, the subscription was cancelled for non-payment, or a cancellation took effect | Sent |
| Offer ending | Owner and admins | Before free months from an offer end | Sent |
| Webhook endpoint disabled | Owner and admins (plus a bell notification) | A webhook endpoint failed for 72 hours and was switched off | Sent |
| Support session notice | Owner | direct.eat support started or ended a session on your account, asked to make changes, or was allowed to | Sent |
| Role changed, Security alert (new sign-in, API key created) | You | Planned | |
| Plan changed, Card expiring, Price change notice (at least 90 days ahead) | Owner | Planned | |
| Welcome, Onboarding nudges, Shop is live, First order, Import complete, Data export ready | Owner | Planned | |
| Domain connected, Certificate problem, Domain problem, Domain expiring, Sending domain problem | Owner | Planned | |
| Sub-processor change, Terms update | Owner | Planned |
Quiet hours and pausing
Section titled “Quiet hours and pausing”Each person can set quiet hours and pause their own notifications for an hour in Settings → Notifications. Critical events still reach someone during opening hours. See Notification settings.
Related
Section titled “Related”Was this page helpful?