Case study / ChromaLabel at KHA 2026

A QR code became the first move in the sales conversation.

How a printed booth QR became a phone-first Plinko experience that gave hospital buyers a reason to play, share, and talk about what they actually label.

1printed QR entry point

0booth screens required

1structured sales conversation

The challenge

Trade-show scans are easy. Useful conversations are not.

ChromaLabel wanted a booth interaction that would attract the right hospital people without creating a line for a giveaway or requiring a monitor, tablet, or complicated staff process.

Design constraint

The experience had to earn a qualified stop, not just a scan. It needed to work on the visitor's own phone, avoid a booth screen, and give staff a simple next step for the conversation.

The campaign flow

The QR was the ticket. The board created the conversation.

The visitor used their own phone. Staff only had to recognize a valid chip code, run the physical Plinko interaction, and record the useful part of the conversation.

01 / Scan

Enter from the banner

A printed QR sent the visitor to a focused campaign page instead of a generic homepage.

02 / Qualify

Make the form earn its place

Name, hospital, department, contact details, and product interest made the lead useful before the game began.

03 / Play

Spin for chips

A short phone interaction awarded one to three chips and gave the visitor something worth showing a colleague.

04 / Talk

Redeem at the booth

Staff recorded the board result and asked one practical question: what labeling problem is costing you time?

05 / Follow up

Keep the context

The flow was designed to carry the hospital, department, interest, pain point, and next step into the follow-up.

The useful data

Every field had a job.

The form was deliberately short. It captured enough context to make the follow-up specific without turning the game into a lead-gen questionnaire.

What the experience was designed to capture

Hospital and department, so the follow-up reached the right buying group.
Email and cell, so the intended follow-up channel was explicit.
Product interest: specimen and lab labels, calibration dots, floor marking, or custom print.
The visitor's own words about the labeling failure or workflow pain.
The board result and redemption state, so the sales team knew what happened next.

Where ScanBlitz fits

Keep the printed QR stable while the campaign changes behind it.

The same pattern works with a ScanBlitz dynamic QR: print once, route scans to the campaign experience, and keep the source and creative measurable. If the destination changes from a game to a booking page or a sample request, the code does not need to be reprinted. Scan data becomes the top of the funnel; the game or form supplies the sales context.

ScanWhich sign, booth asset, or source created the visit?

StartDid the visitor begin the form or leave immediately?

RedeemDid a scan become a real booth conversation?

Follow upDid the lead become a sample, quote, or meeting?

The repeatable lesson

Do not ask a QR code to be the campaign.

A QR code is the entry point. The campaign is the sequence after the scan: a clear promise, a quick qualification, a reason to share, a human conversation, and a measurable next step.

Give your next printed QR a job to do.

Build a trackable campaign that can change destinations, measure scans, and connect the offline moment to the next sales action.

Create a ScanBlitz account

This case study describes the campaign workflow and measurement pattern. The KHA event app was a separate lightweight experience; this page documents where ScanBlitz supplies the QR and measurement layer. It does not publish attendee records or claim a conversion rate that was not measured.