What happens after a customer taps an NFC review sign
An NFC review sign, or a Google review card with the same chip in a wallet-size format, is a holder with a chip that stores one link. The customer holds an unlocked phone near it, the phone reads the address and opens it in the browser, with no camera and no app. What happens next depends on the link: the Google review form, a service's page, or nothing if the address no longer works
What is actually stored in an NFC tag?
Inside the sign is a small chip with an antenna and no battery. It is powered by the phone itself when the phone comes within a few centimeters. The chip stores a short NDEF record, and for review signs it is almost always a single web address. There is no photo of your business, no name and no "app" in it
Hence the main rule: the sign knows nothing about Google. It only hands the phone a line of text. If the line leads to a review form, that is where the customer lands. If it leads to the page of a service that has shut down, the customer sees an error. The chip "works" equally well either way
What the customer sees after the tap on iPhone and Android
| Step | iPhone | Android |
|---|---|---|
| Does anything need turning on | No: iPhone XS and later read tags in the background | NFC must be on in settings, and some people have it off |
| Screen state | Phone in hand with the screen on, camera and Wallet closed; a locked phone asks to be unlocked | Screen on and unlocked |
| What appears | A notification that has to be tapped | Usually the browser opens right away, or an app picker |
| Where the link opens | In the phone's browser, not in a messenger | In the phone's browser, not in a messenger |
| Where to hold it | The top of the back, near the cameras | Depends on the model, look for the NFC mark or check the manual |
In practice the most common reason for "it didn't work" is not the sign but how the customer holds the phone: they touch it with the screen, use the bottom of the phone or pull it away before it had time to read. One sentence from staff, "hold the top of your phone there for a second", fixes most of these cases
Why an NFC tap never opens a messenger's in-app browser
A link sent in Telegram, Viber or Instagram often opens in the messenger's own in-app browser. The customer is usually not logged in to Google there, and the review form asks them to log in, which is where many people give up. An NFC tap removes this step: the phone's system reads the address, not the messenger, so the page opens in the regular browser
That doesn't guarantee the customer is logged in to Google in that browser. But it is the same browser they use every day
Where should the link on the sign lead?
There are two options, and they behave differently a year later. A direct link to the Google form is written once and works as long as the profile doesn't change. A service link is a short address that decides on the server what to show the customer: a rating, the Google form, a complaint form
| Direct Google link | Service link | |
|---|---|---|
| What the customer sees | The Google review form right away | A page with a rating, then the Google form |
| After a profile change or a move | The tag has to be rewritten or replaced | The target changes on the server, the tag stays |
| Can you see how many taps there were | No | Yes, if the service counts visits from a specific tag |
| If the service disappears | Nothing, Google stays | The tag leads to a dead address |
Pochuto has a separate NFC placement for this: the dashboard gives it its own address of the form /q/code, which you write to an NTAG213 or NTAG215 tag with any NFC app. Visits from that tag show up in statistics as a separate source, and if the customer leaves a complaint after the tap, the Telegram notification shows which sign they came from. We don't sell signs or tags
The tag stores the full address, domain included. If you change the domain of your review page, every tag written earlier points to the old address and has to be rewritten
When an NFC sign won't work
- A phone without NFC or without background reading: not every Android phone has NFC, and iPhones older than the XS don't read tags in the background
- NFC is off on Android, and the customer doesn't know where to turn it on
- The tag is stuck to metal without a special shielding layer: metal can interfere with reading, so test it in place
- A thick case or a metal plate for a car mount between the phone and the tag: the read range is only a few centimeters anyway
- Someone else rewrote the tag: an unlocked tag in a public place can be overwritten with any address from a phone
- The address on the tag no longer works, the sign looks brand new, and nobody notices
So NFC speeds up the path but shouldn't be the only way in. A QR code on the same sign can be read by any phone with a camera, and a customer whose tap didn't work doesn't have to explain anything, they just scan the code
How to test an NFC sign before customers see it
- Read the tag with an app like NFC Tools and make sure it holds exactly the address you wrote
- Tap the sign with two phones, an iPhone and an Android, and go all the way to the review form
- Test it where the sign will stand: on a metal stand the result may differ from a table
- Only then decide whether to lock the tag against rewriting: locking is permanent, and you won't be able to change the address later
- Tap the sign yourself every few months, so you find a dead link before a customer does
You can also write a tag without a separate app: in Chrome on Android, the free QR code generator on our site can do it, and it has sign layouts with a zone for the chip. On iPhone the browser can't write tags, so you'll need NFC Tools or NXP TagWriter
Create a review page and an NFC tagSources
Try it on your business
A rating page, QR code and Telegram alerts in 5 minutes
The first 30 days are free. Cancel any time