A Telegram QR code works best when it answers a question the customer already has. A code without a caption forces people to guess; a code that says “Questions about your order?” explains the result before they scan.
Use a separate bot start parameter for each placement. The destination can stay the same while receipt_help, counter_help, business_card, and table_menu tell you which printed surface started the conversation.
Choose the placement and promise
A receipt QR should lead to post-purchase help. A counter QR should offer quick assistance in the location. A business card should open a general contact path. A table QR can offer the menu, a service request, or a venue question.
- Receipt: “Questions about your order? Scan to message us.”
- Counter: “Need help? Scan and ask us in Telegram.”
- Business card: “Scan to contact us in Telegram.”
- Table: “Scan for the menu or to ask a question.”
Build a useful destination
Send the scan to a public business bot instead of an employee profile. Add a short welcome message and start menu so the customer immediately sees the next step. Keep the first request small: order number for a receipt, table number for a venue, or a short question for a business card.
Print and test it correctly
Keep strong contrast, leave white space around the code, and do not make it tiny. Test the final printed size with both iPhone and Android cameras before printing a batch. Scan from the distance and angle a customer will actually use.
- Test the exact PDF or image sent to print.
- Check the Telegram link and start parameter.
- Make the caption readable before the customer reaches for a phone.
- Replace damaged table or counter cards.
Keep the website path consistent
Use the same wording on the website Telegram button and the printed QR. A customer who saw “Order help” on a receipt should see the same support path after opening Telegram. Consistent labels reduce hesitation and wrong-topic messages.
Placement plan: what changes for each QR
Do not reuse one vague caption everywhere. Match the visible promise, start parameter, and first question to the physical context.
| Placement | Customer intent | Start parameter | First detail to request |
|---|---|---|---|
| Receipt | Order, payment, return, or warranty help | receipt_help | Order number |
| Counter | A question while visiting the business | counter_help | What they need now |
| Business card | General enquiry or project contact | business_card | Reason for contacting |
| Table | Menu, service, bill, or venue question | table_menu | Table number and request |
Ready copy for the message after scanning
The start parameter can select a matching welcome message. Keep it short enough to read on a phone and tell the customer exactly what to send.
“Hello! Send your order number and tell us what happened. Do not send full card details or payment passwords.”
“Hello! Tell us what you need help with. If you are in our location, add the counter or department.”
“Thanks for getting in touch. Briefly describe your question or project and the result you need.”
“Welcome! Send your table number and choose: menu question, request service, bill question, or feedback.”
A one-day rollout plan
Test one customer journey before producing every placement.
- Choose one high-intent location, such as the receipt or service counter.
- Create a dedicated start parameter and write down the customer intent it represents.
- Configure the matching welcome message and assign the route to a teammate.
- Print one sample at final size and test it with two different phones.
- Ask a person outside the project what they expect before scanning, then compare that answer with the real result.
- Record the approved link, caption, size, and owner so the next print run uses the same specification.
Pre-print QA checklist
Approve the QR only after checking the real artifact, destination, and support flow.
- The CTA says what happens after scanning.
- The code opens the correct business bot, not a personal profile.
- The start parameter matches the placement.
- The welcome message requests only necessary information.
- The code has enough contrast and quiet space.
- The final printed size scans from the expected distance.
- Both iPhone and Android tests succeed.
- A teammate receives the conversation and can reply through the bot.
Create both entry points