A working system for catering email: who gets which message, where funnel stages end and message events begin, and how enquiry, proposal, booking, and closeout stay separate from promotion.
Catering email marketing breaks the moment a business treats every contact the same way. A bride waiting on a wedding proposal, a facilities manager who orders lunch every Friday, and a venue coordinator who referred a client last spring do not belong on one list getting one monthly send.
Most guides on this topic start with the tool. HoneyCart's own rundown on boosting catering sales with email marketing and automation opens with choosing an ESP and building a list — before separating a live proposal from a delivered event from a past client. A restaurant's regular-diner playbook, the kind ezCater built its restaurant marketing guide around, does not transfer either. A caterer's buyer shows up once, plans for weeks or months, and needs a different cadence than someone ordering lunch again next Tuesday.
This guide separates the catering lifecycle into audiences, funnel stages, and message branches you can run without promising a close, inventing urgency, or letting a headcount change slip into a promotional send. Here is what it covers:
- How to separate prospects, contracted clients, corporate buyers, planners, venues, and past clients into their own permission-based groups
- Where enquiry, proposal, and booking pipeline stages end and message events like opens and clicks begin
- How to reply to a new enquiry and follow up a proposal without inventing urgency
- Where booked-job operations messages must separate from promotional email
- How to run a cohort review that revises one trigger or message at a time
What you need before you write a single email
Before you write a single sequence, gather what already exists: your enquiry list or CRM, your current proposal and contract process, your event calendar, and your kitchen's season and capacity limits. Catering email marketing organizes messages around real job states — it does not start by picking a tool or copying someone else's template.
This guide maps triggers, owners, and suppression rules — not a specific ESP or CRM, a copy-paste sequence, or a promise that any message produces a booking. Platform choice and exact wording stay with the business and its own current documentation.
Before building any sequence, write down the local facts that will shape it. Nobody outside the business can supply these — they come from your own calendar, contracts, and licensing records.
| Field to record | What goes in it | Why it matters here |
|---|---|---|
| Peak season weeks | Your own calendar — the weeks you see the most enquiries and the weeks you go quiet | Sets when follow-up cadence should tighten and when a sequence should assume longer reply times |
| Standard decision window, by job type | How long a typical enquiry takes to become booked or lost, tracked separately per job type | Sets a realistic proposal follow-up cadence instead of one guessed number for every job |
| Kitchen and crew capacity ceiling | The maximum number of events your kitchen and staff can run on a single date | Tells you when to send an honest capacity message instead of nurturing a date you cannot serve |
| Entered ticket bands | Your own per-person or per-event pricing bands by job type, set by you or your finance owner | Qualifies fit before a proposal goes out, so pricing conversations start from real numbers |
| Local competitor set | The caterers you actually track in your market, with a count and the date you last checked | Keeps competitive claims in proposals current instead of inherited from an old list |
| Permits, licences, alcohol, insurance, and bonding owner | The named person or vendor responsible for each requirement | Keeps compliance and legal questions out of promotional sequences and routed to someone qualified to answer |
Step 1: Define audiences, permission, and catering lifecycle states
A caterer's email list is not one audience. Prospects, contracting clients, corporate buyers, planners, venue contacts, and past clients each arrive through a different source, hold a different permission basis, and are allowed a different set of messages — treating them as one list is how a live proposal gets buried under a holiday blast.
Never buy or scrape a list to fill any of the rows below. A purchased list has no verifiable source, permission basis, or job fit, and sending to it fails the first two columns before the first message goes out.
| Audience | Source | Permission basis | Allowed messages | Owner |
|---|---|---|---|---|
| Prospect | Inbound web form, phone call, or referral enquiry | The enquiry itself, for enquiry-related messages only | Acknowledgment, qualification questions, proposal follow-up | Sales/enquiry owner |
| Contracting client | Signed proposal, deposit, or contract | Contractual relationship | Booking confirmation, planning logistics, closeout, review request | Event/operations owner |
| Corporate buyer | Recurring-order account or B2B enquiry | Business relationship, still opt-out-honoring | Reorder reminders, account-relevant updates | Account owner |
| Planner / venue contact | Referral, booked event, or active proposal involving their client | Business correspondence tied to a specific job | Event-coordination content for that job | Event/operations owner |
| Past client | Completed job | Prior relationship, opt-out honored | One review request, then permissioned marketing only if opted in | Marketing owner |
| Vendor | Business correspondence — staffing, rentals, supply | Business relationship, not marketing | Operational coordination for a shared job | Operations owner |
CAN-SPAM applies once any of these messages carries commercial content, including business-to-business email: accurate sender identification, a working opt-out, and honoring that opt-out promptly are federal minimums, not a full consent or privacy analysis. Sensitive dietary or health data, SMS, and non-US recipients need their own qualified review beyond this table.
Step 2: Build the funnel and message-state dictionary
A catering funnel has two layers that must stay separate. Pipeline stages such as qualified enquiry, proposal, and booked job describe where a deal stands; message events such as delivered, opened, clicked, and replied describe what happened to one email. Treating an open as a booking invents demand that was never verified.
| Stage | Entry trigger | Exit trigger | Owner |
|---|---|---|---|
| New enquiry | Form, call, or referral received | Qualification check completed | Sales/enquiry owner |
| Qualified | Date, capacity, geography, and service fit confirmed | Proposal sent | Sales owner |
| Proposal sent | Proposal delivered to client | Client responds or validity window closes | Sales owner |
| Decision pending | Proposal awaiting client decision | Decision made or window expires | Sales owner |
| Booked/contracted | Signed contract or deposit received | Event delivered | Operations owner |
| Planning/production | Booking confirmed | Event date arrives | Operations owner |
| Delivered/event served | Event day begins | Event completed | Operations owner |
| Completed | Event finished, no open incident | Closeout finished | Operations/finance owner |
| Recovery/closeout | Incident flagged, or invoice outstanding | Incident resolved and invoice settled | Operations owner |
| Review/reorder/past-client | Closeout complete, no open incident | Ongoing | Marketing owner |
Every stage needs its own suppression rule — planning/production suppresses marketing sends entirely, and recovery/closeout suppresses review requests and reorder prompts until the operations owner closes the incident.
Message events sit underneath this table, not inside it. Google Analytics recommends distinct generate_lead, qualify_lead, working_lead, and close_convert_lead events — a naming pattern, though the caterer still writes the qualification rule each event depends on.
| Event | Category | System of record | Definition |
|---|---|---|---|
| Impression | Marketing event | Ad platform or GBP insights | A prospect saw an ad, listing, or post |
| Click | Marketing event | Ad platform or analytics | A prospect clicked toward the site or a listing |
| Call click | Marketing event | Call-tracking or GBP insights | A prospect tapped to call from an ad or listing |
| Form submission | Marketing/pipeline boundary | Website form handler | A prospect submitted an enquiry form |
| Qualified enquiry | Pipeline stage | CRM | An enquiry that passed the date/capacity/geography/fit check |
| Proposal | Pipeline stage | CRM or proposal tool | A scoped, priced offer sent to a qualified enquiry |
| Booked job | Pipeline stage | CRM plus contract/payment system | A proposal that reached signed-contract or deposit status |
| Completed job | Pipeline stage | Event/order-management system | A booked job delivered and closed with no open incident |
| Delivered | Message event | ESP delivery log | One email accepted by the recipient's mail server |
| Open | Message event | ESP event log | One email rendered with tracking enabled — a weak signal, not qualification |
| Email click | Message event | ESP event log | One tracked link inside one delivered email was clicked |
| Reply | Message event | Inbox or CRM | The recipient sent a reply to one message |
General automation and trigger-building mechanics are covered in theStacc's email automation guide.
Give every stage in this lifecycle map a home before you automate anything. Picture a proposal that never gets promotional email during its decision window, and a past client who only hears from you again once next season's dates are actually open. theStacc researches, drafts, and publishes the website content the organic side of this funnel depends on, on a set schedule.
Step 3: Handle new enquiries around date, capacity, and fit
The first reply to a new enquiry states three things: what was received, who owns the next step, and what qualification detail is still missing — date, headcount, service format, or location. It never implies the job is booked, and it says plainly when a date or area sits outside current capacity.
- What was received — restate the date, guest count, service type, and location exactly as submitted, so the client knows nothing was lost or misread.
- Who owns the next step — name the person replying, not a shared inbox alias, so the client has someone specific to reach.
- What is still missing — ask only for the qualification detail genuinely absent; never re-ask for information already given.
A Saturday wedding enquiry for 150 guests inside your usual service radius can move to qualification within a single business day. The same date at a venue that already sits at your kitchen's capacity ceiling should get an honest capacity message in the same window — not a nurture sequence pretending the date is still open. Stop the sequence entirely once a job is confirmed unsupportable; continuing to nurture it wastes sends and damages trust with a buyer who might return for a different date.
For general first-touch sequence mechanics, see theStacc's welcome email sequence guide.
Step 4: Follow up on proposals without inventing urgency
A proposal follow-up restates the exact scope and version the client already saw, names the open questions and the decision owner, states any real validity date on pricing or a date hold, and gives a clear way to change scope or opt out — inventing scarcity a hold does not actually carry breaks trust fast.
| Term | What it means | What it is not |
|---|---|---|
| Estimate/proposal | A scoped, priced offer for a specific date, guest count, and service | Not a hold on the date and not a commitment from either side |
| Tentative hold | A date reserved pending decision, under whatever hold policy the business enforces | Not a booking — a hold can expire or release under that same policy |
| Signed contract/deposit | The business's own defined trigger for "booked" | Not reached by a verbal yes, an email reply, or a hold alone |
| Booked job | A contract/deposit-status job now in the operations track | Not the same as an enthusiastic reply during the decision window |
Cadence follows the decision window recorded in the local economics card, not a universal number. A corporate buyer deciding in days needs a faster, shorter follow-up arc than a wedding client deciding over months. State a pricing validity date only if the business genuinely enforces one; if pricing does not expire, say that instead of inventing a deadline to create urgency.
General deliverability and message-testing practices are covered in theStacc's email marketing best practices guide.
Examples: how the email branch changes by job type
A wedding enquiry, a corporate drop-off order, and a memorial service are not the same email problem. Each job type carries its own urgency profile, planning complexity, operations owner, and legitimate exclusions, so the branch a lifecycle sequence takes — and how soon it moves from marketing tone to operational tone — has to differ.
| Job type | Urgency profile | Operations focus | Where the branch differs | Typical exclusion |
|---|---|---|---|---|
| Wedding / full-service | Low weekly urgency, long lead time, high stakes | Venue, rentals, staffing, timeline coordination | Longer proposal-decision cadence, tasting and planning touchpoints, planner/venue cc | Never rushed with artificial countdowns tied to "the date" |
| Corporate recurring | High-frequency, short lead time, price-sensitive | Account owner managing standing orders | Reorder cadence, account-level updates, not per-event copy | Not folded into a once-a-year holiday blast list |
| Drop-off / boxed meals | Same-week or next-day urgency common | Kitchen/dispatch owner | Fast acknowledgment and confirmation, minimal proposal stage | Never treated as needing a multi-week nurture arc |
| Private party | Moderate urgency, moderate planning | Event lead | Personal-tone follow-up, fewer vendor-coordination messages than weddings | Not addressed with corporate-account language |
| Memorial / funeral | Urgent, compressed timeline, high sensitivity | Event lead with direct phone access | Minimal email volume, human contact prioritized, no promotional tone | Never enters a promotional or reorder sequence |
Search results here are full of holiday template roundups, including Lunchbox's ten holiday catering campaign examples. Subject-line ideas from a list like that are fine for inspiration; its cadence, promises, and outcome claims are not facts about your business.
Step 5: Separate booked-job operations from promotion
Once a job is booked, final headcount, dietary information, venue and load-in details, staffing and rentals, delivery, permits and alcohol, payment, contracts, and emergency changes all belong to operations, not marketing. Critical operational messages route through an authoritative system and a named escalation owner — never through a promotional sequence a client can silently unsubscribe from.
| Purpose | Example message | Sender/owner | Opt-out treatment |
|---|---|---|---|
| Operational | Final headcount confirmation | Operations owner | Not opt-out-suppressible — contractual |
| Operational | Dietary/allergen information update | Operations owner, kitchen lead cc | Not opt-out-suppressible |
| Operational | Venue/load-in logistics change | Operations owner | Not opt-out-suppressible |
| Operational | Emergency day-of change | Operations owner, escalation contact | Not opt-out-suppressible |
| Marketing | Past-client holiday reminder | Marketing owner | Always opt-out-suppressible and honored promptly |
| Marketing | Reorder prompt to a corporate account | Marketing/account owner | Always opt-out-suppressible |
This comparison is the line most catering blast lists cross without noticing. Marketing consent — an opt-out honored under CAN-SPAM — does not replace the contractual and emergency-communication rules governing the operational rows above, and the two should never share one suppression list.
Step 6: Close the job and choose the correct next path
Closing a job means checking for an unresolved incident before anything else, assigning an invoice and closeout owner, sending a neutral review request only when the job is clean, asking permission before using any photo or quote, and deciding whether the client is corporate-reorder-eligible or simply a past client for future marketing.
- Completed, no incident, satisfied client — enters the review-request track, then the reorder or past-client marketing track once permission is confirmed.
- Completed, unresolved complaint — enters recovery first; no review request and no promotional email until the operations owner closes the incident.
- Completed, corporate account — routes to the reorder track on its own account-level cadence, separate from one-off event clients.
- Completed, one-off private or memorial job — closes with a thank-you and, where appropriate, a single permissioned review request, not a general marketing list without a fresh opt-in.
Route the review request itself through a documented process — theStacc's review management guide covers timing and platform selection — rather than an email written ad hoc the same week as the invoice.
Step 7: Run a cohort review and revise one trigger or message
A cohort review declares which job group is being measured, the send window, the decision or completion lag expected for that job type, and every stage outcome, complaint, and unsubscribe inside that window, with one named owner and one stated stop rule — then changes exactly one trigger or message before the next cohort runs.
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Delivered rate | Unique messages accepted as delivered under the ESP's documented status | All unique attempted sends in the same campaign/cohort | Declared send window | ESP delivery log | Email operations owner | Tests, duplicates, suppressed-before-send records; bounces reported separately |
| Email click rate | Unique delivered recipients with at least one tracked content-link click | All unique delivered recipients in the same message/cohort | Send window plus a declared 7-day observation period | ESP event log | Email owner | Bots/security scanners under a documented filter, tests, unsubscribe/privacy-link clicks |
| Qualified-enquiry progression rate | Unique emailed enquiry records meeting the written qualification rule after the message | All unique delivered enquiry records eligible for that message | Declared enquiry cohort plus qualification lag | ESP plus CRM matched by stable ID | Sales operations owner | Spam, duplicates, unsupported dates/headcounts/services/geographies, pre-qualified or unmatched records |
| Booked-job rate | Unique qualified-enquiry cohort records reaching signed-contract/deposit status under the business rule | All unique qualified enquiries in that emailed cohort | Cohort plus declared decision lag | CRM plus contract/payment system | Sales owner with finance sign-off | Proposals, tentative holds, tests, duplicates, pre-existing bookings, cancellations before the rule |
| Completed-job rate | Unique booked jobs from the cohort marked completed | All unique booked jobs from that cohort | Booking cohort plus event/order completion lag | Event/order-management system | Operations owner | Cancellations; postponements counted once under a stated rule; tests |
Before any of these five formulas mean anything, run the sequence itself through a QA checklist:
- Trigger — the exact stage change or date event that fires this message, logged with a timestamp.
- Recipient — which audience/permission-matrix row this message is allowed to reach.
- Purpose — the one job this message does, stated in one line.
- Verified facts — every date, headcount, or price in the message checked against the current record, not a cached draft.
- Personalization source — the system field each merge tag actually pulls from.
- Links — every link tested, including the opt-out link.
- Sender/reply owner — a real person who reads replies to this address.
- Send ceiling — the maximum sends this trigger can generate before someone reviews it.
- Suppression — which lists or stages are excluded from this send.
- Error fallback — what happens if a merge field is blank or a record is incomplete.
- Proofreader — a second named person who reviewed the message before it went live.
- Test record — a dated test send kept on file for this trigger.
If complaints or unsubscribes on one message exceed what the business considers acceptable, pause that trigger and investigate — ruling out availability, qualification, sales, operations, and email-failure causes separately before blaming the message.
A cohort review is only useful if the content behind it keeps shipping. Picture a service-area or job-type page still drawing qualified enquiries three years after you published it, so your inbox work goes to people who already found you. theStacc's Content SEO module researches, drafts, scores, and publishes that organic-side content on a set schedule.
Frequently Asked Questions
These answers assume the audience, funnel, and operations separation covered above is already in place. They focus on the judgment calls that come up once a caterer is actually running enquiry, proposal, booked-job, and closeout messages — not on general email mechanics covered in theStacc's broader email marketing guides.
Catering email marketing includes an audience and permission map for prospects, contracted clients, corporate buyers, planners, venues, and past clients; a funnel and message-state dictionary that keeps enquiry, proposal, and booking stages separate from delivered, open, click, and reply events; and distinct message branches for enquiry follow-up, proposal follow-up, booked-job operations, and closeout. It does not include a single blast list.
A caterer should send an acknowledgment that states exactly what was received, names who owns the next reply, and asks only for the qualification details still missing, such as date, headcount, service format, or location. If the date or area is outside capacity, the message should say so honestly instead of starting a nurture sequence toward a job that cannot be served.
A proposal follow-up should restate the exact scope and version the client already saw, name any open questions and the decision owner, state a real validity date only if pricing or a hold genuinely has one, and give a clear way to ask questions, change scope, or opt out — without implying a deadline or interest level that was never verified.
No. A click or reply is a message event that shows engagement with one email; a qualified enquiry or booking is a pipeline stage that requires checking real facts such as date, headcount, geography, and service fit, or, for booking, meeting the business's own signed-contract or deposit rule. Google Analytics recommends keeping lead-generation events distinct from lead-qualification events for this reason.
Booked-event operations messages cover final headcount, dietary and allergen information, venue and load-in logistics, staffing, rentals, delivery, permits, alcohol, payment, contracts, and emergency changes, and they route through an authoritative operational system with a named escalation owner. Marketing emails cover promotional and relationship content and must always carry a working, honored opt-out; operational messages generally should not.
A caterer should stop an enquiry sequence the moment a job is confirmed unsupportable — the date is already booked, the location sits outside the service area, the guest count or service type falls outside capacity — or the moment the contact asks to stop. Continuing to nurture a job that cannot be served wastes the sequence and damages trust with a buyer who may return for a different date.
Yes, when each has given permission and receives messages relevant to their actual role. A planner or venue contact should get event-coordination content tied to a specific booked job or an active proposal, not a consumer-style promotional blast, and a corporate buyer's recurring-order account should be treated as its own audience with its own reorder cadence, separate from one-off event clients.
Long enough to cover that job type's real decision and completion lag, not a fixed calendar month. A corporate drop-off cohort might resolve to booked or lost within days, while a wedding cohort can take months between proposal and signed contract, so the review window should follow the cohort's own dates rather than an arbitrary reporting cycle borrowed from a different business.
Put the lifecycle into operation
Start with one job type and one owner rather than rebuilding every sequence at once. Map that job type's lifecycle stages, write the audience/permission matrix, separate its operational messages from its promotional ones, then run one cohort review before touching a second job type — a working system beats a finished-looking one.
This piece assumes buyers already find you. For the organic-discovery side of that funnel, see theStacc's catering SEO guide; for general list-building and consent mechanics, see the email marketing for local businesses guide.
Put one job type's lifecycle into operation this month, starting with the audience and permission matrix. Picture an enquiry inbox sorted by stage instead of by arrival time, with promotional email nowhere near an active proposal or a booked week. theStacc writes and publishes the organic content that fills the top of this funnel, on a set monthly schedule.
Sources & references
- FTC — CAN-SPAM Act: A Compliance Guide for Business
- Google Analytics Help — Recommended events for lead generation (GA4)
- HoneyCart — How to Boost Catering Sales With Email Marketing and Catering Automation
- ezCater — Complete guide to restaurant email marketing
- Lunchbox — 10 Holiday Catering Email Campaign Examples for Restaurants
Blog SEO, Local SEO, and Social Media — one dashboard, no headaches.