Remind restaurants to reorder before they run short
Every morning, WebRun opens Encompass, identifies restaurant accounts whose last order date is beyond their typical reorder cycle, drafts a personalized reorder prompt in Gmail for the assigned rep to review before sending, and posts a rep-level summary of overdue-to-reorder accounts in Slack so no customer falls off the order guide unnoticed.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically remind restaurant customers to reorder from my foodservice business?
WebRun checks every active restaurant account in Encompass each morning to see if they are overdue to reorder based on their own buying history. It drafts a personalized reorder prompt in Gmail for each lapsed account, leaving every email unsent for the rep to approve, and posts each rep a Slack list of which customers need a nudge before they order from a competitor.
- Lapsed restaurant accounts identified every morning before they place an order with a competitor
- Reps start the day with personalized reorder drafts ready to send, not a cold-call list
- No reorder email sent to a customer without the rep reviewing it first
Built for foodservice distributors · broadline distributors · sales reps · account managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.encompasstech.comin a real browser with your saved login - no setup, no API keys. -
1
Encompass - find accounts overdue to reorder by buying pattern
encompasstech.com How to Automate Encompass
WebRun opens Encompass to find accounts overdue to reorder by buying pattern. - Open Encompass and pull each active customer's last order date and their historical average reorder interval
- Calculate days since last order for each account
- Flag accounts where days since last order exceeds 1.5 times their average reorder interval as overdue to reorder
- Capture customer name, account number, assigned rep, last order date, and typical order frequency
- Exclude accounts with a pending open order already in the system
Done when All active accounts overdue to reorder are identified with last order date, reorder interval, and assigned rep.
-
2
Gmail - draft personalized reorder prompt for each account
gmail.com How to Automate Gmail
WebRun opens Gmail to draft personalized reorder prompt for each account. - Draft a personalized reorder prompt for each overdue account addressed to the primary contact
- Reference the customer's last order and suggest they may be running low on their regular items
- Leave every draft unsent in the assigned rep's Gmail drafts folder for review before sending
Done when A personalized reorder prompt draft is in Gmail for every overdue account, unsent and ready for rep approval.
-
3
Slack - alert each rep to their overdue-to-reorder accounts
slack.com How to Automate Slack
WebRun opens Slack to alert each rep to their overdue-to-reorder accounts. - Send each rep a direct Slack message listing their accounts that are overdue to reorder, with days since last order for each
- Post a team summary to the sales channel with total count of overdue accounts and combined prior-period revenue at risk
- Note that Gmail drafts are ready for each account so the rep just needs to review and send
Done when Every rep is notified in Slack about their overdue accounts and knows the Gmail drafts are waiting.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it send reorder emails to restaurant customers automatically?
No. Every reorder prompt is drafted in Gmail and left unsent for the assigned rep to review and personalize before sending. No email goes to a customer without the rep approving it.
How does it calculate whether an account is overdue to reorder?
WebRun measures the average interval between the account's last several orders in Encompass and flags when days since the last order exceeds 1.5 times that average. Accounts with a pending open order are excluded automatically.
What if a customer's buying pattern changes seasonally?
You can configure separate reorder interval baselines by season or by customer type. Alternatively, provide a fixed reorder window per account and WebRun will use that instead of the calculated average.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.