1. The workflow map
What we mapped from one walkthrough with the events coordinator, and what the automation changes. The coordinator still approves every reply.
Before · reply in 1–3 days
- Enquiry arrives by email, Instagram DM, voicemail or the contact form CustomerFour places to check, every day
- Coordinator copies the details into the events spreadsheet CoordinatorAbout 10 minutes each; details get missed
- Checks the date in the calendar and which space fits Coordinator
- Writes a quote by hand from the price sheet CoordinatorThe same questions answered every time
- Remembers (or forgets) to follow up CoordinatorLeads go cold
After · draft ready in under a minute
- Every channel lands in one queue AutomationEmail, Instagram, voicemail transcript and form
- AI reads the message and fills in the record AIOccasion, date, guests, food, contact
- Checks the calendar and capacities, picks the space AutomationFlags a taken date or too many guests
- Drafts the reply with the right space, minimum spend and package AIIn the brewery's own tone
- Coordinator reviews and approves; follow-ups are scheduled CoordinatorDay 2 and day 5 reminders if there's no reply
2. Try the sandbox
Sandbox: everything runs in your browser and nothing is sent anywhere. In a client build the "read the message" and "draft the reply" steps use an AI model; here they're a scripted stand-in so the demo works offline. The calendar, capacities, rules and templates are the real logic.
Incoming enquiries
Pick an enquiry, or press Process all.
Events spreadsheet (filled in automatically)
| From | Channel | Occasion | Date | Guests | Space | Status |
|---|---|---|---|---|---|---|
| Empty until enquiries are processed. | ||||||