Interactive planning tool
Catering inquiry value calculator
Estimate potential contribution from catering inquiries your team follows up. Your inputs determine the result; this is not a revenue forecast.
Use the calculator ↗Resources for your team
Useful answers.
Practical next steps.
Explore 102 guides for clearer calls, useful websites, better chatbot answers and reliable staff handoffs.
102 guides
Phone operations
Set an honest after-hours callback expectation
An overnight caller may assume somebody is monitoring the inbox immediately.
Read the guide ↗Table requests
Ask about alternative dining times without suggesting availability
A flexible caller may accept a different time, but listing alternatives can sound like offering actual available tables.
Read the guide ↗Staff workflow
Define a backup when the normal request owner is away
A catering or events inbox may depend on one person who is not on every shift.
Read the guide ↗Phone operations
Choose when busy-service calls move to Ava
A host who is seating guests cannot always answer a ringing phone.
Read the guide ↗Getting started
A restaurant phone checklist for catering and busy service
Decide which calls can be answered from approved information and which need a person on your team.
Read the guide ↗Phone operations
Check callback details before ending a call
A request can be complete except for one incorrect digit in the callback number.
Read the guide ↗Catering inquiries
Ask about a catering budget without quoting a package
A budget helps staff understand an organizer’s expectations, but an intake conversation is not a quotation.
Read the guide ↗Catering inquiries
Record an event cancellation request without changing the booking
An organizer may use the word cancel while asking about options or charges.
Read the guide ↗Catering inquiries
Record date flexibility for a catering request
An organizer may have one preferred date and several acceptable alternatives.
Read the guide ↗Catering inquiries
Record an organizer’s decision deadline
An organizer comparing options may need information before an internal meeting.
Read the guide ↗Catering inquiries
Route a catering delivery-area question
An event address may fall outside a restaurant’s usual service area, and past deliveries do not establish a current policy.
Read the guide ↗Catering inquiries
Record a proposed headcount change to an existing event
A returning organizer may ask to increase or reduce attendance.
Read the guide ↗Catering inquiries
Use a headcount range when attendance is uncertain
Early event planning often produces a range rather than a final headcount.
Read the guide ↗Staff workflow
Measure what happens to catering inquiries
Counting inquiries alone does not show whether the catering team could use them.
Read the guide ↗Catering inquiries
Handle catering menu questions awaiting staff confirmation
An organizer may have seen a menu image that differs from the restaurant’s current catering materials.
Read the guide ↗Website operations
Write a catering page that invites useful inquiries
A catering page should help an organizer decide whether to ask for a conversation.
Read the guide ↗Catering inquiries
Capture a request to follow up an existing catering quote
An organizer following up a quotation should not have to start a new event inquiry.
Read the guide ↗Catering inquiries
Gather a repeat catering request without assuming the old package
A returning client may ask for the same event as last time.
Read the guide ↗Catering inquiries
Design a catering summary that supports the first callback
A catering summary should help a manager begin the next conversation, not reproduce every sentence of the intake.
Read the guide ↗Catering inquiries
Distinguish collection, delivery and staffed-service requests
The word catering can describe very different expectations.
Read the guide ↗Catering inquiries
Record event setup expectations for staff review
An organizer may assume that delivery includes arranging tables or remaining at the event.
Read the guide ↗Catering inquiries
Triage a short-notice catering inquiry
A request for an event soon may deserve prompt staff review, but urgency does not establish availability.
Read the guide ↗Catering inquiries
Route a proposed catering time change
Changing an event time can affect several arrangements that the assistant cannot inspect.
Read the guide ↗Catering inquiries
Clarify organizer and approver contacts
The person collecting event options may not be the person authorized to approve an arrangement.
Read the guide ↗Phone operations
Write a complaint callback note staff can act on
A caller reporting a disappointing visit may need to explain several things at once.
Read the guide ↗Website operations
Publish a menu update with an owner and review date
A menu change can leave old links, images and downloadable files in circulation.
Read the guide ↗Phone operations
Keep directions and entrance information usable
An address does not always identify the entrance a guest needs.
Read the guide ↗Phone operations
Give employment callers a consistent next step
Job seekers can reach the restaurant during its busiest service.
Read the guide ↗Catering inquiries
Collect a first catering inquiry without taking an order
A first-time catering caller may not know what the restaurant needs to assess an event.
Read the guide ↗Phone operations
Prepare a dated holiday phone message
Holiday hours often change independently of the regular weekly schedule.
Read the guide ↗Table requests
Route a large-party dining request for staff review
A larger dining party may need a different review path from an ordinary table request.
Read the guide ↗Phone operations
Route a question about arriving near closing
A caller asking whether they can arrive shortly before closing needs a decision about that particular service.
Read the guide ↗Table requests
Relay a late-arrival message without promising to hold a table
A guest running late often wants reassurance that a table will remain available.
Read the guide ↗Phone operations
Capture a lost-property inquiry without exposing items
A lost-property caller needs a clear route to staff, while the restaurant needs enough detail to search.
Read the guide ↗Website operations
Keep a readable menu page alongside a download
A downloadable menu can be convenient, but some guests want to read information directly on their phone.
Read the guide ↗Website operations
Correct a published menu-price discrepancy
A guest may report that a displayed price differs from another restaurant source.
Read the guide ↗Phone operations
Split a mixed call into useful staff actions
A caller may ask about opening hours, mention a future event and raise an issue from yesterday in one conversation.
Read the guide ↗Catering inquiries
Prepare an office-lunch inquiry for the catering team
An office-lunch organizer may care as much about building access and timing as menu options.
Read the guide ↗Website operations
Check the restaurant’s official ordering link
An ordering button should take guests to the destination the restaurant has approved.
Read the guide ↗Staff workflow
Give the opening shift a clear request-review routine
Overnight requests can disappear into a busy opening routine if nobody owns the first review.
Read the guide ↗Table requests
Record an outdoor-seating preference
A guest may prefer outdoor seating without realizing that the restaurant must confirm the arrangement for a particular service.
Read the guide ↗Phone operations
Answer parking questions without promising a space
Parking questions can combine directions, payment, availability and access.
Read the guide ↗Private events
Record audiovisual questions without promising equipment
A presentation or speech may depend on equipment that a dining room does not normally provide.
Read the guide ↗Private events
Route decoration and setup permission requests
An organizer may want to bring decorations, signs or outside setup materials.
Read the guide ↗Private events
Route questions about a private-event proposal
An event proposal may include several items the organizer wants to clarify.
Read the guide ↗Private events
Separate a room preference from an assigned space
An organizer may refer to a room seen in photographs or used at a previous event.
Read the guide ↗Private events
Capture a request to view an event space
A prospective organizer may want to inspect the room before deciding whether to continue.
Read the guide ↗Private events
Capture arrival, event and departure expectations
A private event can have several times that matter: organizer arrival, guest arrival, the main gathering and departure.
Read the guide ↗Private events
Decide whether an event inquiry belongs with venue or catering staff
Some callers ask about hosting at the restaurant and off-site catering in the same conversation.
Read the guide ↗Private events
Gather venue-access questions for an event organizer
An organizer may need detailed information about reaching or using an event space.
Read the guide ↗Website operations
Describe event spaces without implying availability
A private-events page can help organizers understand a venue while still leaving date-specific decisions with staff.
Read the guide ↗Private events
Collect the essentials of a private-room inquiry
A private-room inquiry differs from an ordinary table request because the organizer may expect exclusive space, a schedule and a separate agreement.
Read the guide ↗Table requests
Take a reservation cancellation message for staff
A guest may call to cancel or simply ask about cancellation arrangements.
Read the guide ↗Table requests
Capture an amendment to an existing reservation
A guest changing a reservation needs the restaurant to review the existing arrangement and the proposed change together.
Read the guide ↗Table requests
Help a guest who cannot find a reservation reference
A guest may need help about a reservation but have no reference number available.
Read the guide ↗Accessible guest journeys
Provide a useful route for website access feedback
A guest who encounters a website barrier needs a practical contact route.
Read the guide ↗Private events
Route a whole-restaurant buyout request
A request for exclusive use of the entire restaurant affects normal service and requires a management decision.
Read the guide ↗Staff workflow
Sample call categories before changing coverage
Before changing an answering script, learn what callers actually ask during the relevant service.
Read the guide ↗Chat and FAQs
Keep the restaurant demo separate from real guest service
A prospect may want to hear Ava answer as their own restaurant.
Read the guide ↗Chat and FAQs
Handle a guest who cites conflicting restaurant information
A visitor may quote a review, old menu or another website that disagrees with the chatbot.
Read the guide ↗Chat and FAQs
Turn repeated chat questions into approved FAQs
Repeated questions can reveal that a page or approved answer is missing useful information.
Read the guide ↗Chat and FAQs
Send food-suitability questions to restaurant staff
A visitor may ask whether a dish is suitable for a particular need.
Read the guide ↗Chat and FAQs
Record a visitor’s language preference for follow-up
A visitor may prefer another language for a staff conversation.
Read the guide ↗Chat and FAQs
Introduce a restaurant chatbot’s actual scope
A chat greeting sets the visitor’s expectations before the first question.
Read the guide ↗Chat and FAQs
Redirect an attempted food order to the approved destination
A visitor may begin listing dishes in chat because the interface appears conversational.
Read the guide ↗Chat and FAQs
Use a chat readback before sending a staff request
Typed conversations can change direction as the visitor adds dates or corrects a party size.
Read the guide ↗Chat and FAQs
Move a chat to staff with a clear reason
A visitor asking for a person should not have to repeat the same explanation through a long automated sequence.
Read the guide ↗Chat and FAQs
Give a useful answer when the chatbot does not know
A restaurant chatbot should not fill gaps in its approved information with a plausible guess.
Read the guide ↗Website operations
Separate contact routes by the job staff need to do
A single contact form can mix catering opportunities, reservation questions, supplier messages and employment inquiries.
Read the guide ↗Staff workflow
Build a practical test set for the restaurant assistant
A successful demonstration of one easy question does not show how the assistant handles mixed requests or uncertainty.
Read the guide ↗Staff workflow
Review how long requests wait for staff action
An inbox can look tidy while requests are waiting too long for their next action.
Read the guide ↗Website operations
Handle a guest who submits the same inquiry twice
A slow connection or unclear receipt can lead someone to submit again.
Read the guide ↗Accessible guest journeys
Help guests correct inquiry-form errors
A guest should know what to fix when a form cannot be submitted.
Read the guide ↗Website operations
Choose the minimum fields for an inquiry form
A form should collect enough for the next staff decision without becoming a full event contract or guest profile.
Read the guide ↗Website operations
Write a form receipt that does not confirm a booking
A success message appears at the moment a guest expects reassurance.
Read the guide ↗Accessible guest journeys
Give restaurant inquiry fields persistent visible labels
A visitor returning to a partly completed form should not have to remember what each box means.
Read the guide ↗Website operations
Put the restaurant’s practical information in a useful order
A visitor arriving on the homepage may be trying to find hours, a menu or the correct contact route quickly.
Read the guide ↗Accessible guest journeys
Describe useful restaurant images for their purpose
A photograph can carry practical information that is missing from the surrounding words.
Read the guide ↗Website operations
Keep a small change log for guest-facing information
When a guest hears an incorrect answer, staff need to know which version was active and who can correct it.
Read the guide ↗Accessible guest journeys
Test the inquiry journey with a keyboard
A staff member can discover practical navigation problems by trying the guest journey without a mouse.
Read the guide ↗Accessible guest journeys
Review the restaurant page with enlarged text
Guests may enlarge text or browse on a narrow screen to make a page easier to read.
Read the guide ↗Accessible guest journeys
Organize restaurant pages with descriptive headings
An event page may contain room information, inquiry instructions and questions about follow-up.
Read the guide ↗Website operations
Review restaurant photographs for the right expectations
Photographs can communicate a room, a dish or an event setup more quickly than a paragraph.
Read the guide ↗Staff workflow
Plan a controlled pause when restaurant coverage needs correction
If an assistant gives an incorrect critical answer or routes requests to an unattended destination, the restaurant needs a defined way to pause the affected workflow.
Read the guide ↗Staff workflow
Run a weekly restaurant pilot review with real decisions
A pilot review is useful when it produces a small set of decisions about information, routing and staff follow-up.
Read the guide ↗Website operations
Give every restaurant promotion a removal plan
A seasonal promotion can outlive its intended dates in banners, saved menu images and chatbot answers.
Read the guide ↗Accessible guest journeys
Make restaurant links say where they lead
A page with several buttons saying learn more or click here leaves guests to infer the destination.
Read the guide ↗Staff workflow
Review the usefulness of staff handoffs
A request can arrive promptly yet still be difficult to act on.
Read the guide ↗Staff workflow
Define request statuses that staff interpret consistently
Labels such as new, handled and complete mean different things to different staff.
Read the guide ↗Staff workflow
Approve an answering-script change before it goes live
A small script edit can change what a guest believes has been promised.
Read the guide ↗Website operations
Recover a broken contact or inquiry route
A visible contact button is only useful if the destination works and someone receives the request.
Read the guide ↗Table requests
Set expectations for a same-day table inquiry
A request for later today can arrive while staff are busy with the current service.
Read the guide ↗Table requests
Route a guest’s specific seating needs to staff
A guest may need information about seating, space or reaching a table.
Read the guide ↗Staff workflow
Carry unfinished guest requests across a shift change
A request received near the end of a shift can become everybody’s responsibility and nobody’s task.
Read the guide ↗Table requests
Pass along a celebration note without promising extras
A birthday or anniversary note can help staff understand a guest’s visit.
Read the guide ↗Phone operations
Explain lunch, dinner and between-service hours
A restaurant can be open for one purpose while another service is unavailable.
Read the guide ↗Phone operations
Separate supplier messages from guest requests
A delivery coordinator, maintenance provider and dining guest may call the same public number.
Read the guide ↗Table requests
Collect a table request with an unmistakable pending status
A caller asking for a table may hear any friendly acknowledgement as a booking confirmation.
Read the guide ↗Phone operations
Handle calls during an unexpected closure
When a location unexpectedly closes, callers may have travel plans or an existing arrangement.
Read the guide ↗Table requests
Answer a wait-time question without inventing live availability
A caller asking how long the wait is needs current dining-room information.
Read the guide ↗Website operations
Assign one owner to website opening hours
Hours can appear in a footer, contact page, menu and chatbot answer.
Read the guide ↗Phone operations
Recover a call intended for another location
A familiar restaurant name can lead someone to the wrong branch.
Read the guide ↗No matching guides. Try another topic or choose all topics.
Your workflow, first
Let’s map your first week.
Bring the calls you want covered. We’ll agree the script, handoff and limits.