QR-driven opt-in

A QR opt-in turns a physical touchpoint into a consented conversation: the scan opens the recipient's messaging app with a pre-filled message, and sending it creates the contact and the consent record together. This guide covers creating the code, writing consent text that holds up as evidence, and confirming the scan routes correctly into the inbox.

Step 1 — Create the QR opt-in

In Contacts → QR opt-ins, create a new code. Choose the destination channel — WhatsApp is the most common, using its click-to-chat link format, but SMS and other supported channels work the same way — and write the pre-filled message the scan will send. Keep the pre-filled message short and specific to the placement, e.g. "Hi, I'd like updates from [location/campaign]", since it helps you distinguish sources later.

Step 2 — Write the consent text

The wording displayed next to the code is your evidence of what the person agreed to, so it needs to say plainly what they're opting into (marketing messages, order updates, a specific programme) and on which channel. Vague wording like "scan to chat" is not consent evidence for marketing sends — say what will be sent and how often, if that's known.

Step 3 — Confirm the auto-reply

The first automated reply after the scan does two things: it confirms the opt-in to the person, and it writes the consent record to their contact profile, including the source (this QR opt-in), the timestamp, and the wording that was live at the time. This is what makes the flow a double opt-in — a scan alone is not consent, the confirmed message exchange is.

Step 4 — Publish and place the code

Publish the opt-in to generate the final code image, then place it wherever the consent wording will be visible alongside it: packaging, receipts, signage, screens or printed collateral. A code with no visible consent text next to it, even if the underlying flow is compliant, is weak in practice — the person scanning should be able to read what they're agreeing to before they scan.

Step 5 — Verify end to end

Scan the code yourself before rolling it out. Confirm the pre-filled message sends, the auto-reply fires, the consent record appears correctly on the test contact, and the resulting conversation lands in the inbox routed the way you expect (assigned to the right team, or picked up by the right automation).

Keep the evidence clean

How this differs by connection status

Every client owns and connects their own Infobip account for the destination channel; QR opt-in setup and consent wording are always your own responsibility.

Costs to expect

Creating and publishing QR opt-ins is included in the optional $50/month Arino Core connection, which also covers Arino support, management, updates and WebRTC. The pre-filled message that opens the conversation, and any messages sent afterwards, are billed as normal message/conversation costs against your own Infobip account, metered separately and not covered by the $50 — see billing-and-plans for current figures.

Steps at a glance

1. Create the QR opt-inIn Contacts → QR opt-ins, create a new code and choose the destination channel (WhatsApp, SMS or another supported channel) and the pre-filled message the scan will send.
2. Write the consent textWrite the consent wording that will be displayed next to the printed or on-screen code — this is the record of what the person agreed to.
3. Confirm the auto-replySet the automated first reply that confirms the opt-in to the contact and writes the consent record, including source and timestamp, to their profile.
4. Publish and download the codePublish the QR opt-in and download the code image for print or on-screen use.
5. Place the codePut the code on packaging, receipts, signage, screens or printed materials where the consent wording will be visible alongside it.
6. Verify the conversation lands in the inboxScan the code yourself to confirm the pre-filled message sends, the auto-reply fires, and the resulting conversation appears in the inbox correctly routed.

Frequently asked