Back to WorkCase study

QR review assistant with owner control of what goes public

Scopelyt built a phone-first review flow for local businesses: scan a QR code, rate with stars, tap preset answers, get an AI draft to edit, then submit. High ratings can open a Google review the customer finishes themselves. Lower ratings stay private with the owner.

Industry
Local business reviews
Type
AI-assisted product
Guest path
Public QR flow
Owner path
Authenticated dashboard

01 — Demos

02 — Problem

Local businesses want more reviews without gaming platforms or posting on the customer's behalf. Guests abandon long forms on their phones after a visit. Owners need a fast path that still produces specific feedback, plus clear control over what stays on the platform, what stays private, and what can reach a public review site only when the customer chooses to finish it.

03 — Constraints

  • Guest routes stay public and separate from the authenticated owner dashboard.
  • Submit always persists on the platform first. The server does not post to third-party review sites.
  • Generated copy is reviewed or edited before it is kept. Submit requires the customer's final text.
  • The legacy POST /feedback/generate endpoint is stateless smoke-test tooling only. The QR flow uses Public session endpoints.
  • Google review handoff returns a URL for the customer to complete. The server does not post to Google on their behalf.

04 — Responsibilities

  • Built a QR-driven review assistant: guest scans, rates with stars first, taps preset answers for visit areas, receives an AI draft, edits it, then submits.
  • Owners register, log in, and manage businesses with review settings, logos, tags, and a configurable minimum rating for public handoff.
  • Owners download review QR codes as PNG or SVG and filter submitted sessions by public or private visibility.
  • Owners import assessment templates (general service, salon, restaurant, clinic) or manage departments, questions, and dropdown options.
  • High ratings can offer a Google review URL the customer opens themselves. Lower ratings stay private with the owner.
  • Owners connect their own website or app via webhook or REST with API key, Bearer, or HMAC auth. Connections can be tested, and failed deliveries retried.
  • Owners view basic analytics for the last 30 days from the dashboard.
  • Documented the full API in OpenAPI 3 with JWT bearer auth on owner routes.

05 — Architecture

  • One product surface: a public guest flow and an authenticated owner dashboard.
  • Public session pipeline: create session, generate AI draft from rating and answers, submit with edited text, route visibility by rating threshold, optionally deliver to owner connections.
  • Persistence on the platform before any optional public-review handoff. Google redirect is a client-side URL, not a server-side post.
  • Owner modules for auth (register, login, single-use refresh rotation), businesses, assessment questionnaires, and outbound connections with test and retry paths.

06 — Result

A working review assistant founders can click through today: QR guest path, owner dashboard, and documented API reference. Proof Scopelyt can ship AI-assisted product flows where the business owns what becomes public, what stays private, and how feedback reaches their own site. No adoption metrics published; evaluate the live demos.

07 — Stack

TypeScriptTypeScript
Node.jsNode.js
NestJSNestJS
MongoDBMongoDB
ReactReact
RESTREST
JWTJWT
OpenAPIOpenAPI 3
scopelyt.cta
1
2
3
4
5

> |

// Client builds get the same clarity-before-code bias. Lock scope, then execute.

// Same pod. Weekly demos. You own what ships.

$ Talk AI review flows