While the chafing dishes are out,
this is how it goes.
What it captured — with the source of every field
The customer record — one, not three
Same customer — matched by phone number, thread continued
Handed to a person — and what the person receives
- The whole conversation, both channels
- Every captured field, with its source
- Why it stopped: a discount is a judgement the owner makes on site, not a fact on the course sheet
9:00 AM, the owner’s screen — what is waiting
Scripted simulation · sample data · synthesised voices · the per-head rates are an example price list, not a real caterer's quote. To hear the real AI, call +82 70-5277-0820.
Not a customer case — an example of how the product answers once this trade’s price list and safety rules are loaded. Amounts are typical published ranges; what is actually quoted comes from the price list the owner enters.
A missed call
is written down nowhere.
An eighty-head corporate lunch is a three-thousand-dollar job, and the company that books once books the holiday party too. The inquiry lands when every hand is carrying a chafing dish, and the organiser who gets voicemail sends the same brief to three other caterers. Whoever replies first with a date and a price gets the tasting.
The things a machine
must not say in this trade.
The four below are not settings you switch on and off. They are blocked from the start when the Catering answering is built. Anything that touches them is not answered — it goes to a person.
- It never takes a date the calendar already has.One team cannot serve two sites on the same day. It holds only dates the event calendar shows open, and a hold becomes a booking only through the site visit and a contract.
- It never moves the price.Per-head rates are read from the course sheet the owner loaded. Any adjustment comes after the site visit, in the owner’s written quote.
- It never confirms dietary or allergen handling.Vegetarian, halal and allergy requests are recorded with the headcount and answered by the kitchen.
- It never assumes the site will work.Parking, lifts, power and water are checked on the visit. It does not say “that should be fine” down the phone.
- If an AI answer causes a loss, our liability is capped at the fees you paid in the three months before the month of the incident. Losses from our wilful misconduct or gross negligence are compensated as the law provides, outside that cap. Terms §7 →
- Every call leaves a recording (you can switch it off), a summary, and the facts it answered from. Those records belong to you and can be exported in full at any time. Terms §8 →
- Replies are composed by a language model running in the United States. Customer records, bookings and call recordings are stored on our production servers in Seoul. Where the data lives →
When the call ends,
these fields are already filled.
The Catering CRM comes with Catering fields. You do not bend a generic CRM's blanks to your trade over months — it is written in your trade's words from day one.
Where every inquiry stands,
on one line.
If your trade is not here,
it can still usually be built.
Restaurants
Wedding & event venues
Boutique stays
Golf clubs
Cafés & bakeries
Travel agencies
Florists
Coworking spacesSend us your Catering price list,
and we show it answering from that.
No payment details. Within one business day you get a recording of the AI answering your customers' ten most common questions from your own price list — and if it is not right, you stop there.