QR route updated
Use the right review or referral QR card route.
This page keeps older QR card links working while preserving source intent between standard review/referral requests and storm-specific proof follow-up.
Standard review QR card
Use for completed jobs, invoices, leave-behinds, and local review routing.
Storm review QR card
Use only when storm source, job type, city, proof owner, and post-storm review ask are explicit.
Product fit boundary
LocalKit fits review QR, referral, invoice, GBP, profile, and booking-link routes when the next action is local and one-click. Webzaz fits only when QR traffic needs a website proof destination, project gallery, service page, or testimonial placement path.
After the route
Choose whether the next repair is trust cleanup or publishable proof.
Review and referral QR traffic often confirms the ask worked but leaves the team guessing about the next job. Some operators still need tighter request timing, reply ownership, and complaint recovery. Others already have happy customers and need a cleaner path into testimonial proof, service-page placement, and city-level trust.
Trust repair first
Separate review velocity from broader reputation control.
Use the reputation path when the real leak is request timing, second-touch follow-up, low response rates, review replies, complaint handling, or mixed profile trust after the QR scan.
Proof reuse first
Turn happy jobs into proof that sells the next one.
Use the testimonial path when the QR route already works and the next fix is permissioned quotes, before-and-after proof, service-page placement, referral proof loops, or city-specific trust blocks.