Fixed quote after a free call

Restaurant review management that keeps replies calm and consistent

Guests pick restaurants from the map, and reviews decide which pin they tap. We build a workflow that asks every guest for a review the same way after their visit, flags new reviews the same day, drafts short replies in your voice for the manager to approve and groups recurring comments into monthly themes for the team meeting. A typical build costs $1,000 to $2,500 and takes about three weeks.

The problem

Why restaurant review requests need rules

Happy guests rarely think to leave a review, and unhappy ones usually do. Asking consistently fixes the imbalance, but shortcuts such as only asking guests who seemed pleased, or offering a free dessert for five stars, break Google's rules and, in the US, can break the FTC's.

Replying takes time the manager does not have after a double shift, so reviews go unanswered for weeks, or get a defensive reply written at midnight. A drafting step with a fixed tone and a person approving every reply solves both.

What we build

What our restaurant review management includes

Ask every guest the same way

One request after the visit to every guest who agreed to be contacted, via your reservation platform or POS receipt, never filtered by how happy they seem.

Table QR codes

A QR code to your Google review form on receipts or table cards, offered to everyone.

Same-day alerts

New Google reviews posted to Slack or email so the manager sees them while they are fresh.

Reply drafts in your voice

Short, calm drafts that thank, acknowledge and invite the guest to get in touch, ready to edit.

Monthly themes

Recurring comments about wait times, noise, specific dishes or staff grouped for the team meeting.

Private feedback for everyone

A feedback form offered to all guests alongside the review link, never instead of it.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Visit ends

    A completed reservation or closed check marks the visit.

  2. 02 Automated

    Request sent

    Guests who agreed to be contacted get one review request.

  3. 03 Automated

    Review detected

    New reviews are picked up and posted to the team channel.

  4. 04 Team review

    Manager approves reply

    A draft is prepared; the manager edits and posts it.

  5. 05 Manager or chef decides

    Complaints and refunds

    Any refund, comp or apology beyond the reply is the manager's decision.

How it behaves

How review requests and replies behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • One polite request after their visit, if they agreed to contact
  • A QR code on the receipt or table card
  • A calm reply from the manager to their review

What the team sees

  • New reviews in Slack or email the same day
  • Draft replies ready to edit
  • A monthly list of recurring themes

What the automation does

  • Checks consent and sends the same request to every eligible guest
  • Detects new reviews and drafts replies
  • Groups comments into themes

Edge cases and fallbacks

Guest complained during the meal
Still asked like everyone else; the complaint is handled by the manager.
Review names a staff member
The draft avoids repeating names; the manager decides any internal follow-up.
Fake or abusive review
Flagged to the manager, who can report it through Google's own tools.
Google or workflow outage
Alerts resume when service returns and missed reviews are picked up on the next run.

Architecture

Review requests and replies for a restaurant at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Visit completed Booking or check n8n workflow Consent check Review request Email, text, QR Google reviews Business Profile Reply draft Venue tone Manager Edits and posts
  • Input
  • Logic and services
  • Output
  • AI step
  • People

How it flows

  1. 1 A completed booking or closed check starts the workflow, which checks contact consent.
  2. 2 Every eligible guest gets the same request with your Google review link.
  3. 3 New reviews are detected and a short reply is drafted in the venue's tone.
  4. 4 The manager edits and posts each reply and handles complaints personally.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Restaurant review management & replies project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current reviews, reservation or POS data, consent records and reply tone.

  2. 02

    Design

    2 to 3 days

    Request timing and wording, QR placement, reply rules and theme report.

  3. 03

    Build

    About 1 week

    n8n workflow, review link, monitoring, drafts, alerts and themes.

  4. 04

    Test

    2 to 3 days

    Requests sent to staff phones and drafts checked against your tone guide.

  5. 05

    Launch

    1 to 2 days

    Switch on and walk the manager through approvals.

  6. 06

    Support

    Ongoing

    Wording updates and new platforms such as Tripadvisor or Yelp.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Google Business Profile Your reservation platform or POS for completed visits Twilio SMS or your email provider Slack or email alerts Claude or OpenAI for reply drafts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Tone guide, request timing, consent and reply rules.

    $200 – $400

  • Build

    Requests, monitoring, drafts, alerts and themes.

    $500 – $1,300

  • Integrations

    Reservation platform or POS, Google and messaging.

    $150 – $400

  • Testing and shadow run

    Staff test requests and draft checks.

    $100 – $250

  • Launch and training

    Switch-on and manager walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Messaging, n8n and AI usage are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment plus carrier fees (Twilio's published US pricing), if you send requests by text.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Pay-per-use fees for drafts, usually a small monthly amount.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

No review gating or incentives

Google's policy does not allow selectively soliciting positive reviews, discouraging negative ones or offering incentives for reviews. We ask every guest the same way.

Source: support.google.com

US: FTC rule on fake reviews

The FTC's final rule bans fake reviews, incentives tied to a particular sentiment and certain review suppression practices.

Source: www.ftc.gov

UK and EU: marketing consent

Review requests by email or text go only to guests who agreed to be contacted, in line with PECR and GDPR.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Restaurant reputation management questions questions, answered.

Keeping a steady flow of genuine reviews, replying to them well and acting on what guests say. The workflow handles the asking, alerts and drafts; the manager owns the replies and the fixes.

No. Google does not allow incentives for reviews, and the FTC rule bans incentives tied to positive sentiment. Asking at the right moment with an easy link works better and keeps you within the rules.

Briefly and calmly: thank the guest, acknowledge the issue without arguing, and invite them to contact the manager directly. The drafts follow that pattern and a person approves each one.

We do not set it up that way. Replies are public and permanent, so a person approves every one.

We start with Google, where most local searches happen, and add other platforms where they allow monitoring or alerts, confirmed per project.

Requests sent, reviews received each month, average time to reply and recurring themes. We do not promise a star rating.

Free 20-minute call

Want this for your restaurants & café?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call