FAQ
The questions properties ask.
Short answers, all of them on this page. If something here is missing, write to support@gotouchtags.com.
For your guests
Do guests need an app?
No. They tap and the page opens — an alternative to a hotel guest app, with nothing to download and nothing to sign in to.
Does it work on any phone?
Phones with NFC open the page with a tap, on iOS and Android alike.
Do you identify guests?
No. Nobody signs in. A tap is counted against a random device ID, which is replaced with a one-way digest after 30 days. If you connect your property system, it supplies a first name for the greeting and nothing more.
Do you text guests?
No. A guest who signs up chooses email and text separately, neither is ticked for them, and the exact wording they agreed to is stored with the time.
For your team
What does our team have to learn?
Taking a request with “I've got this” and closing it with “Mark handled”. That's it.
Who installs it?
We do, in person. Installation is quoted with your hardware.
What if we have several buildings?
Each property has its own tags, its own figures and its own team. Seeing every property in one place is part of Enterprise.
Does it connect to our property system?
Read-only — first names and checkout dates, so the Guest Hub can greet the right person. Nothing is written back. Mews, Cloudbeds, Apaleo and StayNTouch.
Hardware and data
What if a tag is damaged or taken?
A replacement takes over the old tag's page and history, so your figures carry on and nothing else needs reprinting.
Does every piece tap?
Yes. Every piece carries an NFC chip, so one tap opens the page.
Who owns the data?
You do. Export everything as CSV or JSON at any time.
What properties push back on
The objections we actually hear on a first call, answered straight. Where the answer is “not yet,” it says so.
We tried QR codes and nobody used them.
So did everyone. These are not QR codes: a guest holds their phone near the mark and the page opens — no camera, no aiming, no app. There is no QR code printed on any piece, on purpose, and the artwork check refuses a file that has one.
What about a guest whose phone won't tap?
The Guest Hub is an ordinary web page, so the desk can send the same address to a guest who can't tap. A tap that never happened is simply not counted; nothing is estimated to fill the gap.
Won't this make more work for the front desk?
Requests arrive in one queue with the room already on them, because the piece on the wall knows which room it is in — nobody types a room number. You choose which kinds of request guests are offered, and you can turn any of them off.
We already have an app.
Then the Hub can point at it. The Hub is a page with your own sections and links on it, and it asks a guest to install nothing, so it sits alongside what you have rather than replacing it.
Will you ask our guests for reviews before we're ready?
Nothing sends itself. A review tap happens when a guest taps the Review tile, and nothing is scheduled behind your back. We also never sort guests by how happy they seem: everyone reaches the public review option, and a low rating additionally gets a private line straight to the manager.
Can our GM change it without involving IT?
Yes. Offers, links, which request types are offered and the wording on the page are all changed in Settings by whoever you give the role to, and the change is live when they save it. No deploy, no ticket, nothing to reprint.
Running it day to day
For whoever a GM forwards this to — operations, IT or legal.
Replacing a tag
A damaged or missing tag is replaced with a new one that keeps the same page and the same history, so your numbers don't break and nothing needs reprinting elsewhere.
Roles and access
Each property has three roles. Owners invite people and change any setting. Managers can change tags, offers and settings, and see everything, but not the team or the timezone. Front desk handles requests and sign-ups, with no settings.
Your property system
Read-only. First names and checkout dates come across so the Guest Hub can greet the right person by name. Nothing is written back to your property system. You connect it yourself in Settings; without it, the Hub simply doesn't use a name. Which systems are built, and what state each one is in, is further down this page.
- Mews
- Cloudbeds
- Apaleo
- StayNTouch
Your data is yours
Export everything as CSV or JSON at any time: daily taps for every tag, every sign-up with the consent wording and the time it was agreed, every request with its timings, every offer claim and redemption. A guest can delete their own details from the link on your guest pages; it's done when they confirm by email.
What we don't do
We don't ask guests to sign in. We don't market to your guests. We don't estimate figures we can't measure, and we don't attribute a review or a booking to a tap.
Retention periods and the list of outside companies involved are on how GoTouch handles data.
What GoTouch connects to
Only what is built. A system that is not on this list is one we have not written yet — and where something is built but not switched on, the row says so rather than showing you a logo.
Your Google review page
Working todayThe Tile's Review version opens the review page for the listing you confirm. We open it. We never post to it, reply on it, or flag anything on it.
Reviews on Google, Booking.com and Expedia
Working todayRead into your dashboard through a licensed data provider, so the reviews you already have sit in one place with the themes guests keep raising. Read-only, and shown only inside your signed-in dashboard — never republished on a public page.
Your property system
- What we read
- A guest's first name and the dates of their stay, so the Guest Hub greets the right person and an offer can be timed to the stay.
- What we write back
- Nothing. Not a note, not a charge, not a work order. The connection is read-only in the code, and every adapter refuses a write.
Mews
Built, not switched on yetBuilt, and run read-only against the demo environment Mews publishes. Switching it on for a property needs our Mews client token in place on the server.
Cloudbeds
Built, waiting on themBuilt to Cloudbeds' documented API. We are waiting on a sandbox account from their marketplace to run it against.
Apaleo
Built, waiting on themBuilt, using a client you create inside your own Apaleo account. Listing it in Apaleo's store — the tidier route — needs their certification first.
StayNTouch
Built, waiting on themBuilt to StayNTouch's documented API. We are waiting on a sandbox account and the API address they issue with it.
Thank you — we have it.
We'll write back to the address you gave and tell you honestly where that system sits.
That didn’t send. Check the fields and try again, or write to support@gotouchtags.com.