Skip to content

Workflow guide

Support plan for restaurants

Answer hours, menu, and catering questions from your restaurant’s pages. Large bookings, deposits, and allergy questions go to your staff.

Build an agent for freeCheck available integrations

What the visitor sees

Questions to test

What the agent answers, and what stays with your team.

Use these questions as test prompts. Each one should be answered from the source under it. Account-specific answers need authentication and a supported connection.

Restaurant assistant

Planning sample

Answer from approved sources

  1. 01
    Is there parking near the restaurant?Hours and location
  2. 02
    Do you have vegetarian mains?Menu.pdf
  3. 03
    What’s the minimum order for catering?Catering and events
Boundary

Hand to your team

  • Large bookings and deposits
  • Allergy and dietary questions
  • Complaints and refunds
For example
Can you hold a table for 12 on Saturday without a deposit?
Planning guide. The examples on this page help you scope a test. They do not mean every provider, data source, or action is already connected.

Handoff rules

Write down where the agent stops.

When it does, your team sees the whole chat, not a summary.

  1. 01

    A food allergy question

    The agent doesn’t guess. It hands the chat to staff who can check with the kitchen.

  2. 02

    A complaint about a visit

    The agent apologizes and passes the chat to the manager.

  3. 03

    A booking for a large group

    The agent collects contact details and passes the chat to the manager.

Not every job belongs to an agent. Emergencies, licensed advice, and decisions nobody has approved stay with people. See the stop conditions

What your team sees

A safer first version

Four steps, one pilot review.

Record a baseline before the test, use the same time window after it, and keep the result tied to your own conversation data.

  1. 01Choose one support job
  2. 02Add approved sources
  3. 03Set action and handoff rules
  4. 04Run a private test

Sample measurement checklist

Pilot review

Pilot review progress: 0/4

Questions before setup

Decide the rules before customers see it.

No. Agents can’t run booking actions. The agent shares your booking link and hands large groups to your staff.

Write in the instructions that allergy questions always go to staff, then test it. The agent should never guess about ingredients.

Account-specific lookups and actions in another system need a supported integration and the right permissions. Check the integrations directory before including either in the workflow.

Use real questions with sensitive data removed. Compare each answer with the approved source, test the handoff, and record any missing or incorrect answer before making the agent public.

More workflow guides

Plan another support job.

All solutions

Test one narrow workflow first.

Start with five real questions, remove sensitive data, and compare every answer with the source your team approved.

Build an agent for freeTalk through your workflow

No credit card required