Automation
The work that happens whether or not anyone is free.
Orders nobody accepted, the review request after a delivery, the basket that went quiet, the numbers at the end of the night. Jobs that have to happen at a certain moment, happening at that moment, every day.
Always running
- Every minuteOrders past their accept deadline, timed pauses that have run out
- Every 2 minutesAnything that failed to reach a connected system, retried
- Every 5 minutesReview requests, orders left open, autopilot rules
- Every hourBaskets gone quiet, delivery and payment failure checks
- At your closing timeThe day’s report, dated to the trade it belongs to
- OvernightThe 86 list cleared, scheduled closures applied and reopened
The back office half
Nobody has to remember any of this.
These are not flows we build for you as a project. They are part of the platform, on from the day you go live, and they hold whether it is a quiet Tuesday or the tablet is being ignored on a Friday night.
Every minute2 jobs
The accept deadline
Five minutes with no answer and the order is closed off, refunded and the customer told. One placed overnight waits for opening time.
Pauses that end themselves
Pause for 30 minutes on the tablet, and after 30 minutes everything agrees you are open again. Nobody has to go back and unpause.
Every 5 minutes2 jobs
Review requests
Half an hour after a delivery lands, the customer is asked how it went, with a link to rate it. Once, ever.
Orders left open
Orders left open past their window close on your own deadline, which is what makes the loyalty stamp actually land.
After you close1 job
The day’s numbers
Sent just after your own closing time, not at a fixed hour, and dated to that trading day. On a dead day, nothing is sent.
Overnight2 jobs
The 86 list
An item marked off mid service comes back at midnight, so last night’s shortage never hides today’s dish.
Closures you booked weeks ago
The shop closes and reopens on the dates you set, booked months ahead. A change made by hand in between is never overruled.
Continuously1 job
Failures, found rather than reported
Failed connections retry themselves. A spike in email or text failures raises an alert with us, rather than waiting for you to notice.
Autopilot
Set a rule once. It keeps going.
Every five minutes it looks for the people who qualify, and it tells you in a plain sentence who that is before you switch it on.
Second order
A first order with no second yet
Slipping regular
A regular starting to drift
Win back
Quiet past the days you set
We miss you
The same, in a warmer tone
Abandoned basket
A basket that went quiet
Birthday treat
Their birthday month, yearly
VIP reward
The moment they turn VIP
Order anniversary
A year since their first order
- Numbers on every rule. Who qualifies now, who was emailed, who came back.
- Queued, never blasted. Sends retry on their own if the provider stumbles.
- Draft, activate, pause. Nothing sends until you say so, and you edit while paused.
One run, start to finish
Most of the decision is who not to email.
Every five minutes each active rule looks for who qualifies. Then everything that should stop a send gets its turn.
- 1Who qualifies
- 2Which rule wins
- 3What stops it
- 4What sends
- First order 14 days ago, no secondSent
- Birthday this month, lapsed 90 daysSent, once
- A regular starting to slipHeld
- Basket left at 18:40Cancelled
- Not seen for six monthsNever
Five qualified. Two emails sent.
An illustration of the rules, not live data. Every skip is recorded, and a hold is only a hold: a birthday capped this run can still send on the next one.
The guardrails
Automated is not the same as relentless.
The hard part of an always on campaign is everything that has to stop it.
Only one sends
Highest priority rule wins, the rest stand down
A seven day gap
The default minimum between any two emails
A monthly ceiling
Give a rule a budget and it stops there
One reminder, ever
The basket gets one, whichever job fires first
Ordering cancels it
Come back first and the reminder never goes
Off means off
Unsubscribed is filtered from every audience, forever
Ordernised Intelligence
Every automated email is assembled, not improvised.
The part of the platform that works out who to contact and what to put in front of them. Deliberately not a chatbot let loose on your reputation.
From real events
A first order with no second. A basket that stopped. A birthday.
In your branding
Logo, colours, menu and ordering link, dropped in at send time.
Nothing invented
It will never decide you are award winning and email that.
The preview is the send
Same renderer, so what you approve is character for character what lands. Test it on yourself first.
A personal link, carrying nothing personal
No name, no address, no offer in the URL, and the discount is worked out again on our side at checkout.
It writes the search listing for your ordering page the same way, out of your own cuisines, town and menu.
Worth saying out loud
Three things it will not do.
Predict your Friday
Guessing someone’s usual slot, and the two loyalty reward triggers, are still on the list.
Switch itself on
We enable autopilot per venue, and only once there is a lawful basis for emailing that customer list.
Replace a person
It answers no phones and settles no bad reviews. It clears the jobs that never needed a person.
Real stories
The jobs nobody has to remember, on a busy Saturday.
Every grill table at Jinseon orders by QR, the loyalty stamp lands on its own when the order completes, and bookings, takeaway and loyalty share one customer record. Tips are up 56% and party revenue up 32%.
Read the Jinseon storyCommon questions
Nowhere, in the sense that the operational jobs are already running the day you go live: the accept deadline, review requests, the end of day report, the 86 list. The first thing most people deliberately switch on is the abandoned basket reminder, then the second order nudge, because both work on customers who have already decided they like you.
Each trigger comes with short starter copy you can rewrite, and the email around it is built from your own branding, your menu and your ordering link. Nothing writes claims about your business on your behalf, which is the part that usually makes automated email read badly.
Yes. Every rule is created as a draft and does nothing until you activate it. You get a plain English sentence describing exactly who it will email, a live preview that uses the same renderer as the real send, and a test email to yourself. After that you can pause it, edit it while paused, and switch it back on.
No. When somebody qualifies for several rules in the same run, only the highest priority one sends and the rest are recorded as cancelled. On top of that there is a minimum gap between any two autopilot emails to one person, an optional cap on how many times a rule may ever email someone, and an optional monthly budget per rule.
Sends sit in a queue and retry with backoff rather than failing a whole campaign. Every job records each run, so a job that has gone quiet is reported instead of silently doing nothing. And the whole pipeline is written to be repeatable: an overlapping run, a retry or a duplicate webhook cannot send the same email or charge the same order twice.
No. It runs on the data your ordering, bookings and payments already produce. Where you want something outside the platform involved, that goes through integrations, and anything that fails to reach the other system is retried automatically rather than lost.
Tell us what your week keeps repeating.
A short walkthrough on your own venue, and an honest answer on which of it is already running, which of it we would switch on, and which of it still needs a person.