The issue on site
In multi-branch businesses every location behaves like an island. The same customer verifies by SMS in Istanbul and fills in the same form again in Ankara the next day. Guests get frustrated, marketing data splits in two, loyalty cannot be measured and one person appears as several visitors.
Check these first
- 01
Are your locations managed under one organisation or as separate accounts?
- 02
Decide which verification (SMS, PMS, corporate account, social login) recognises a guest and for how long.
- 03
Make sure your privacy notice covers cross-location recognition.
- 04
Define which locations join the roaming group (whole chain, region, brand).
HotSpot / LogIQ approach
MintyRoaming keeps guest identity at organisation level, independent of location. Once verified, the guest is recognised across the roaming group and, per your rule, either connects directly or continues with a short welcome screen. Verification records and 5651 logs are still kept completely for each location; roaming never bypasses legal logging.
Guest and team outcomes
For guests: no form and no waiting at the second branch. For the business: one customer, one visit history, real cross-location loyalty and correct counting of returning visitors.
Frequently asked question
Does MintyRoaming remove verification entirely?
No. The first verification happens; recognition elsewhere is valid within the duration and rules you set. When it expires or policy requires, re-verification is requested.
Do randomised phone MAC addresses break roaming?
HotSpot is designed to stay resilient when MAC randomisation would otherwise break recognition. The method is not disclosed; guests do not need to change device settings.
This content supports technical assessment, not legal advice. Verify scope against product, version and institutional policies.