Let visitors tell you they've arrived
Let a visitor tell you they're here with one tap at the end of your guide. We send the message to your gate & arrival contacts.
The last thing a visitor does is arrive. Turn this on and the final step of your guide gets an I've arrived button. One tap and we send the message for them — they never leave the guide, and there is no second app to press send in.
The message goes to your gate & arrival contacts: the same list the code-approval requests and the ETA messages use, so whoever is actually at the address hears about it. That list is what makes the button work, so it has to have somebody on it — with the switch on and the list empty, leaving the communication screen (and publishing, and turning the guide on from your dashboard) takes you to the list and asks you to add a contact or switch the button back off.
Nothing runs in the background and no location is collected. The visitor taps, and your contacts get a text saying they've arrived.
Turning it on
- 1Open your guide and go to Communication.
- 2Switch on Show an "I've arrived" button at the end. It is off until you do.
- 3Under the switch you'll see who the message goes to. Tap through to Gates & ETA to add or edit that list — at least one contact is needed before you can publish.
💡The message is written in your guide's own language, not the visitor's, so it reads naturally to you even when a guest walked the guide in another language. A signed-in visitor is named in it; everyone else is "your guest".
When it doesn't appear
If the last step of your guide carries a door or gate code, that step keeps its code panel instead. The code is what the visitor came to the last step for, and two large buttons competing in the same place helps nobody. Move the code to an earlier step if you'd rather have the arrival button there.
Looking for something that updates you *before* the guest gets there? That's a different feature: visitor ETA sharing, which asks the guest at the moment they set off.
Last updated Aug 19, 2026