Collect restaurant feedback with a QR code

01

Create one campaign, then separate every restaurant placement

A campaign defines the mode, form, language, appearance, review destination and low-score threshold. Create it first, then add a distinct placement wherever the feedback request appears.

A table card, receipt, bill folder, pickup counter and delivery insert may share the same form, but each needs its own QR code. That separation shows which surface creates scans and which one produces completed responses.

• Table or table-area placement
• Receipt or bill-folder placement
• Pickup-counter placement
• Delivery-packaging placement

02

Ask only after the experience being rated

Timing gives the score meaning. Put dine-in feedback beside the bill after service, pickup feedback where the order is handed over, and delivery feedback inside the package where the customer can judge condition and accuracy.

Keep feedback separate from the menu QR: a menu scan happens before most of the experience. Use explicit prompts such as “Rate today’s visit”, “How was your pickup?” or “Tell us about this delivery” instead of “Scan me”.

03

Use questions the restaurant can act on during a shift

Start with one primary CSAT question: “How satisfied were you with today’s visit?” Follow it with a short reason list such as speed of service, staff, order accuracy, food temperature, cleanliness or atmosphere, then an optional comment.

For a broader relationship measure, use a separate NPS campaign. Mosaqo supports up to ten questions, but the useful restaurant default is one score, one reason and optional contact details with separate follow-up consent.

04

Turn low scores into a service-recovery workflow

Set the low-score threshold before launch. New responses enter the shared inbox with their campaign, placement, answers and form version; the team can assign them and move them from new to in progress and resolved.

If the guest voluntarily leaves contact details and consents to follow-up, the team can respond directly. Anonymous answers still carry placement and timing context, making repeated problems at a pickup point or table area visible.

• Enable low-score alerts
• Review the answer with its placement context
• Assign an owner in the inbox
• Record progress through resolution

05

Combine private feedback and public reviews without gating

Public-review mode opens one external destination directly. Private-feedback mode opens the restaurant survey. Combined mode can collect structured feedback and offer a Google, Tripadvisor, Facebook, Trustpilot or custom review destination.

The public-review action must remain available to every respondent regardless of score. Mosaqo records the external review click, but never describes it as proof that a review was published.

06

Compare the full funnel, not raw scan totals

Read each placement as a funnel: scans, hosted views, starts, submissions and external review clicks. A busy receipt placement may generate more scans while a pickup-counter prompt produces a higher completion rate.

Compare results with covers or order volume only when that context is available in your own systems; Mosaqo does not connect to the POS. Low starts can indicate unclear prompt copy, low completion can indicate a long form, and repeated low scores with the same reason point to the guest experience.

07

Test in the real restaurant environment before publishing

Scan the final printed proof rather than relying only on the editor preview. Test small receipt print, glossy or wet table surfaces, dim lighting, scanning angle and the distance from a standing guest at the counter.

Complete a test response, confirm the language and form version, check the low-score workflow and verify the public destination. Publish only when the QR, mobile journey and response workflow work together.