247CallTaker
Restaurant

An AI receptionist that already knows restaurant calls.

It answers when you can't, asks your customers the right questions in the right order, books the job and texts you a summary. Try it now: you play the customer.

See plans from $29
Olive and EmberDemo line, answered by our AI

Pretend you're a customer calling Olive and Ember. Type what you'd say on the phone.

Sample business with sample hours and prices. Type "stop demo" anytime.

The questions it asks, in order

Built from how restaurant calls really go. Every question has a reason, and it skips anything the caller already said.

Quick mode (reservation):

  1. "Is this for a reservation?"
  2. "What day?" / "Is that tonight?"
  3. "How many people?"
  4. "What time works? I have slot1 or slot2."
  5. "Any seating preference, like table_types?"
  6. "Is this for a special occasion?"
  7. "Can I get a name and the best cell number for your confirmation text?"
  8. Read-back: "name, party people, day at time. I'll text you now."
  9. "Would you like to pre-order anything for pickup, or is that everything?" (only if takeout prepay is on and caller is ordering, not dining in)

Quick mode (takeout pre-order):

  1. "Pickup or delivery?" 2. "What would you like?" (repeat each item and price) 3. "Any changes or allergies I should note? Please also tell staff at pickup." 4. "Your total is total with tax." 5. Read refund policy (below). 6. "Okay to text the payment link to this number?" 7. "It'll be ready at pickup_time."

White Glove:

  • "Happy to help you find a great table. What's the occasion?"
  • "We have a patio that's lovely at sunset, or a quieter booth inside. Which sounds better?"
  • "Would you like us to bring out a dessert with a candle? Any name for the card?"
  • Full read-back including notes, then: "Is there anything else that would make the night special?"

Before any payment link (both modes, word-for-word from owner):

"Before I send the link: pre-paid orders are not refundable once paid. owner_policy_detail. Do you agree?" Wait for a clear "yes." Log the time and the exact wording read.

Calls it handles

  1. Make a reservation - date, time, party size. Agent checks availability, books, texts confirmation; adds reminder if booked more than N days out.
  2. Change or cancel a reservation - agent finds booking by name/phone, updates, texts new confirmation.
  3. Hours, location, parking - answered from facts.
  4. Menu and prices - agent reads items and prices from the current menu, never guesses.
  5. Takeout pre-order - agent takes the order, reads it back with total, states the refund policy, texts payment link, gives pickup time.
  6. Special occasion - birthday, anniversary, proposal. Agent books and adds a note (dessert, candle, quiet table).
  7. Table request - patio, booth, window. Agent records as a request unless the system can lock a table.
  8. Large party / private event - agent collects details and hands off to the events contact.
  9. Allergy / dietary questions - agent shares what the restaurant provided and always adds "tell your server too."
  10. Waitlist / "how long is the wait?" - agent adds to waitlist if the system supports it; otherwise gives the walk-in policy.
  11. Lost item, complaint, billing issue - message to manager.

Safety comes first

  • Caller describes a severe allergic reaction, choking, or someone unconscious: "Please hang up and call 911 now." Then alert manager on duty.
  • Food poisoning complaint: take details, do not argue or admit fault, alert manager same day.
  • Fire, gas smell, threat at the restaurant: "Leave the building and call 911." Alert manager.
  • Allergy questions are never "safe" or "guaranteed": always "Our kitchen handles allergens. Please tell your server too."

What it will never do

  • Never take card numbers by voice; payment only by texted Stripe link (PCI DSS).
  • Never send a payment link before reading the refund policy and hearing a "yes." Note for the owner: a no-refund policy does not stop chargebacks. Card holders can still dispute; a clearly disclosed policy is evidence the restaurant can submit. Stripe's dispute guidance asks for the policy text and "how and where the applicable policy was provided to your customer prior to purchase" (Stripe). Our logged read-back and the policy in the payment text are that evidence.
  • Never say a dish is "allergen-free" or "safe." Some states require menus to tell diners to inform the server, e.g. Massachusetts: "Before placing your order, please inform your server if a person in your party has a food allergy" (FARE).
  • Never invent prices, specials or availability.
  • Never promise a specific table unless the system locks it.
  • Never send marketing texts without opt-in. Confirmations/reminders need the caller's consent to text (TCPA); promotional content needs explicit consent (CompliancePoint).
  • Never deny being an AI. Give recording notice where required.
  • Never take or discuss alcohol orders for minors; follow owner rules on alcohol in takeout.

Plans

Every plan includes the restaurant playbook above. We set it up with your hours, services and prices.

Solo

$29 / month

Launch price. Regular $39.

  • For owners with no employees
  • 100 minutes
  • Answers, takes messages, texts you a summary
Start my plan

Starter

$49 / month

Launch price. Regular $59.

  • 200 minutes
  • Answers and takes messages
  • Text summary after every call
Start my plan

Booking

$99 / month

Launch price. Regular $119.

  • 500 minutes
  • Books into your calendar
  • Urgent calls to your cell
Start my plan

Busy shop

$199 / month

Launch price. Regular $249.

  • 1,200 minutes
  • Several lines or locations
  • Everything in Booking
Start my plan

Month to month. Extra minutes $0.25. The first 100 businesses keep the launch price as long as they stay.