Menu upload, operating details, order modes, optional phone reservations, and what callers experience on your line. Sections below link out to onboarding, dashboard, and integrations whenever those topics come up.
You will pick Restaurant as the assistant type in onboarding, then work through the core steps plus restaurant-only fields so callers hear options you actually support.
Provide your website or manual facts so the Intelligence step can extract hours, location, and common Q&A. Walkthrough: Onboarding Setup.
Menu-grounded answers, structured order-taking support, reservation handling when you enable it, and restaurant-style call summaries in the dashboard—aligned with how the Restaurant Assistant is configured in the product.
These fields map to your restaurant assistant's saved operating details. Fill them in onboarding or keep them updated in the dashboard so callers hear what you truly offer.
Business hours
Plain-language hours the assistant should treat as authoritative for open/closed questions. Pair with timezone so late-night or holiday answers stay correct.
Common mistake: copying seasonal hours without a note. If hours change often, update them when the menu or promo changes too.
Timezone
Choose the timezone for the location your business hours describe. The assistant uses it together with your hours for open/closed answers.
Order cutoff
Order Cutoff is a single free-text field in onboarding and the dashboard (placeholder: "30 minutes before closing"). Whatever you type is stored and passed to the assistant as written—there is no separate time control or validated clock format. Use plain language your team actually follows; if pickup and delivery differ, spell that out in the same field.
Business address
The physical address callers should use for pickup or directions. Multi-location brands should align each assistant instance with one site's hours, phone, and address.
Order fulfillment modes
Select which service types callers may hear as available. Labels in the product:
- Pickup
- Dine-in (on premises)
- Delivery
Common mistake: leaving Delivery enabled when you do not operate delivery. Turn off modes you do not support so callers are not offered them.
Delivery and liability (expand)
Delivery often involves fees, zones, and partner handoffs. Only enable it when your staff and systems can honor it; otherwise keep it off and mention catering or third-party apps in your knowledge base if appropriate.
Phone reservations
With phone reservations on, the assistant can collect table booking details during the call. With it off, phone reservation capture is disabled in the flow—the assistant does not run callers through that booking path. Match this toggle to how you actually take reservations. If it is off but your website or other materials still tell people to call to book a table, update that text (or the business facts in your knowledge base) so callers are not given conflicting instructions.
Business phone number
The main number associated with this assistant for callbacks or confirmations when that is part of your workflow.
Your dashboard labels restaurant calls using the same intent names below. Use them to sanity-check what callers experienced after each summary.
Order
Caller wants food or drinks for pickup, dine-in, or delivery. The assistant collects items, service type when possible, and contact details so your team can confirm or fulfill.
Reservation
Caller wants a table or time. When phone reservations are enabled, the assistant gathers party size, preferred time, and contact details consistent with your policy.
Menu inquiry
Caller asks about dishes, prices, ingredients, or allergens. The assistant uses your uploaded menu and business facts—keep the menu file current; callers with severe allergies should confirm with staff.
Hours
Caller asks when you are open or closed. Clear business hours plus the correct timezone prevent wrong answers across holidays or late-night calls.
Complaint
Caller is upset or reporting a problem. The assistant stays calm, captures the issue, and does not promise outcomes your policy does not support—your team follows up from the summary.
Other
Everything else (directions, parking, general questions). The assistant uses your knowledge base and hands off anything sensitive to your team as needed.
The assistant introduces itself as an AI, states that the call is recorded, and follows Coverforme's restaurant system instructions: it stays within what you have enabled and in your knowledge, avoids promising outcomes it cannot guarantee (including refunds, comps, and legal topics unless your facts clearly support them), captures what the caller said, and leaves follow-up to your team through call summaries. Voice and greeting come from Onboarding Setup.
Integrations deliver call summaries to Slack, SMS, Telegram, or your systems via a signed webhook—useful when an order or complaint needs the kitchen or manager immediately.
Read Integrations for setup detail; this page stays focused on restaurant behavior.