Choose an order email, a pickup text, or a discount request. See the facts, permission check and outcome for each one.
ALDER CUP / FICTIONAL CAFÉ / VANCOUVERSIMULATED ACTIONS · NO REAL DELIVERIES
Alder Cup / Operator workspaceINTERACTIVE DEMO
Confirm Maya’s office order
EMAIL/Maya · maya@example.com
Same order for Friday, September 25 at 9:30? 12 oat lattes and 12 cinnamon buns. Please confirm the total.
✓Matched order AC-1042 and Friday pickup slot
✓Read menu prices and the approved email template
✓Confirmed order status and CAD 150 permission limit
PRE-APPROVED WORKFLOW
MESSAGE TO THE CUSTOMER
Hi Maya, your 12 oat lattes and 12 cinnamon buns are confirmed for Friday, September 25 at 9:30 am. The subtotal is CAD 123.00 before tax. Collect at the side counter. We’ll text your saved number when it’s ready. Thanks, Alder Cup.
Email sentDEMO / 09:14:08 / SENT
Confirmation sent under the owner’s existing rule.
Simulated workflow. Fictional records and send receipts. No message leaves this page. Real sending needs connected channels and permissions in your agent.
Define this once. Revisit when your rules change.
Pre-approved work. Clear exceptions.
Tell your AI what it can handle, when it can act and which decisions come back to you.
CAN HANDLE UNDER THESE RULES
Routine customer updates
Confirm an already verified repeat order up to CAD 150 before tax.
Use the approved confirmation template and current order details.
Send a pickup SMS only after a ready event, with a verified number and SMS opt-in.
Log the result returned by the sending tool.
ASK THE OWNER FIRST
Promises outside the routine
Discounts, refunds or other price changes.
Changed booking times or unverified availability.
Missing consent, a new recipient or unclear customer identity.
Unknown facts, failed sends or conflicting instructions.
These are sample rules for a fictional café. You set the rules for your own business.
Optional: compare draft wording and edit a café rule
This separate drafting exercise changes sample group-booking rules and tone. It does not change the fixed email/SMS workflows above.
ALDER CUP DEMO CAFÉ · FICTIONAL BUSINESS
The customer asks
“Could our group of 10 come by next Friday around 3 pm? Do you have any group discounts?”
WITHOUT THE BUSINESS BRIEFILLUSTRATION
Polite wording, but missing the details.
Thanks for reaching out! We’d love to help. Please contact our team to discuss group bookings and any available offers.
The reply leaves out the booking policy and gives no clear next step. You still have to add those details.
WITH YOUR APPROVED BRIEFBRIEF V1
A reply that uses your rules.
Thanks for thinking of Alder Cup! Could you confirm the exact date for your group of 10 at 3 pm?
Groups of 8 or more need staff approval, so your booking isn’t confirmed. We can check the options with the team, but can’t promise a discount.
Uses the group policy, keeps the tone warm, and checks what it doesn’t know. This is a draft. Nothing has been sent.
About these examplesWe wrote these examples to show how a brief can be used. They aren’t a live AI test or a guarantee of results. AI may ask useful questions without a brief too. Including your rules gives it those details to work from.
See the brief behind the reply and try changing a rule
Where the sample facts come from
Latte CAD 5.50 · bun CAD 4.00sample-menu.md
Groups of 8+ require staff approval.owner-rules.md
No automatic discount offers.owner-rules.md
Availability is not confirmed.unknowns.md
Your business knowledge gives AI something to work from.
Keep a reviewed brief where your AI can find it. Try one new conversation to check that it uses the right facts.
Inside the sample workspace
Inspect the files behind the action.
Open a file to see the prices, customer details and rules behind this example.
alder-cup / business-contextILLUSTRATIVE FILES · READ ONLY
OWNER-DEFINED ACTION RULES
Permission comes with conditions.
Email
For verified repeat orders up to CAD 150 before tax: use order-confirmations.md. Confirm the current pickup slot and amounts.
SMS
For a ready event: check a verified, opted-in recipient and use pickup-notifications.md.
Exceptions
discount-approvals.md requires the owner’s decision before offering a discount. A message permission does not grant a price-edit permission.
Result
Record the provider’s result. A failed or unknown send is not a success; do not blindly retry.
FICTIONAL ORDER SNAPSHOT / AC-1042
Maya’s Friday office order
Items
12 oat lattes × CAD 6.25; 12 buns × CAD 4.00.
Subtotal
CAD 123.00 before tax.
Pickup
September 25, 2026 at 9:30 am. Side counter. Slot confirmed in this example.
Customer
maya@example.com. Saved number ending 0186, verified, SMS opt-in recorded.
Event
Ready at 09:24 in the SMS example. This is a fictional fixture, not a live order feed.
01 / BUSINESS
Alder Cup
What we do
An independent neighbourhood café.
Our voice
Warm, clear, short sentences. No invented claims or promotions.
Source
Fictional owner brief. The tone selector above changes the example drafts.
02 / POLICIES
The rules behind the reply
Groups
Groups of 8 or more need staff approval.
Bookings
Check live availability. Never treat a draft as a confirmed booking.
Discounts
No automatic discount offers. Ask staff about actual options.
Source
Fictional owner-rules.md and your demo selections.
03 / PRODUCTS AND PRICES
Details a generic post would miss
Latte
CAD 5.50
Oat milk
CAD 0.75 substitution
Cinnamon bun
CAD 4.00
Source
Fictional sample-menu.md
04 / STILL TO CHECK
An empty field is not permission to guess.
Availability
Not connected. Check the booking system and staff.
Opening hours
Not supplied in this brief.
Group offers
Not confirmed. Do not invent a discount.
Next Friday
Ask for an exact calendar date.
The brief and its source notes are yours to inspect.