REVIEW RECEPTION · SAMPLE REPORT
Restaurant sample report
Monthly review desk report
Review Reception · September 2026
Illustrative restaurant · Ireland
Fictional sample: This report demonstrates the proposed format. It is not a client result.
1. Your month at a glance
We checked 68 new reviews across your agreed platforms. 62 replies were submitted, of which 60 were confirmed published at the reporting cutoff. Six reviews await your approval.
Guests frequently praised attentive service and food quality. The clearest concern to check is the gap between courses during weekend service.
| Activity | Google | Tripadvisor | Total |
|---|
| New reviews checked | 44 | 24 | 68 |
|---|
| Replies submitted | 41 | 21 | 62 |
|---|
| Confirmed published | 40 | 20 | 60 |
|---|
| Submitted; publication not yet confirmed | 1 | 1 | 2 |
|---|
| Awaiting your approval | 3 | 3 | 6 |
|---|
How to read these figures: Published replies are a subset of submitted replies. Reviews awaiting approval have not received a reply from us. The two unconfirmed submissions remain on our tracking list.
Reporting cutoff: 1 October 2026. Counts refer to platform reviews, rather than unique guests; the same guest may post on more than one platform.
2. Replies and outstanding work
Completed
- Routine replies were drafted in the agreed tone and checked by a person before submission.
- Replies avoided unsupported explanations, compensation promises and unnecessary personal details.
- Publication was checked separately from submission.
Still open
- Confirm whether the two outstanding submissions appear publicly.
- Obtain your decisions on the six reviews listed below.
- Send reminders where an approval request has been unanswered for two working days.
3. Your approval desk
| Topic | Reviews awaiting approval | What we need from you |
|---|
| Booking mix-ups | 2 | Confirm what happened and any agreed change to booking checks |
|---|
| Unexpected charges | 2 | Confirm the charge and how it was disclosed |
|---|
| Dietary request | 1 | Confirm what was requested and what staff advised |
|---|
| Refund request | 1 | Confirm the facts and the wording you authorise |
|---|
A booking mix-up · Two stars
We booked for a birthday dinner, but our reservation couldn't be found. We eventually got a table, after an awkward wait.
Status: Held for owner approval. Not published.
Question for you: What caused the booking error, and what safeguard will be introduced?
SUGGESTED REPLY, AWAITING YOUR APPROVAL
We're sorry the reservation mix-up disrupted your birthday dinner. We're reviewing how bookings are recorded and checked before service to reduce the chance of this happening again. A special occasion deserves a smoother welcome.
Why approval is needed: The proposed reply commits to reviewing booking checks. We need your confirmation before publishing that commitment.
An unexpected charge · Four stars
A lovely meal overall, but we only noticed the service charge when the bill arrived. It would have been better to know beforehand.
Status: Held for owner approval. Not published.
Question for you: How was the charge disclosed, and what clarification can you commit to?
SUGGESTED REPLY, AWAITING YOUR APPROVAL
Thank you for dining with us. We're glad you enjoyed the meal, and we're sorry the service charge came as a surprise. We'll review how we explain it before guests order, so the total is clearer from the start.
Why approval is needed: A positive overall rating does not remove the need to check a concern about charges.
4. What guests are telling you
| Recurring theme | Reviews mentioning it | Share of 68 reviews | Interpretation |
|---|
| Attentive service — positive | 32 | 47% | A recurring strength worth preserving |
|---|
| Food quality — positive | 27 | 40% | Guests regularly recognise the core dining experience |
|---|
| Delays between courses — concern | 10 | 15% | A repeated issue that deserves a closer check |
|---|
Supporting excerpts
- Service: “Our server noticed we were celebrating and made us feel really welcome.”
- Food: “The fish was beautifully cooked, and the desserts were a highlight.”
- Course delays: “The starters arrived quickly, but there was a long gap before the mains.”
Context: Eight of the ten reviews mentioning course delays described a Friday or Saturday visit. That suggests a weekend pattern worth checking; it does not establish whether the cause was staffing, kitchen capacity or another issue.
Counting method: A review is counted once per theme. One review can mention several themes, so the percentages do not add up to 100%. Public reviews are a partial picture of guest experience, not a survey of every guest.
5. Suggested priorities
| Priority | Suggested action | Evidence and limits |
|---|
| First: check weekend course timing | Compare the relevant review dates with service records and discuss where delays occurred | Ten mentions, including eight weekend visits. The cause is unconfirmed |
|---|
| Next: resolve booking and billing approvals | Answer the factual questions so accurate replies can be published | Four reviews remain unanswered while we await your input |
|---|
| Preserve: attentive service | Share the recurring positive feedback with the team | Service was praised in 32 reviews |
|---|
These are suggestions to assess internally. They do not establish a cause or predict an improvement in ratings or revenue.
6. Next month's review desk
Review Reception will
- Continue checking the agreed platforms every working day.
- Track submitted replies until publication is confirmed.
- Keep sensitive replies on hold until authorised.
- Monitor whether course-delay feedback continues.
Your input
- Resolve the six approval requests.
- Tell us about any confirmed operational changes that should inform future replies.
- Confirm whether checking weekend course timing revealed a pattern.
Questions about this report? Email hello@reviewreception.com.