Yes — treat it as steady, not seasonal
Visitor traffic in Madinah changes the loyalty approach mainly because it's steady year-round rather than concentrated in a sharp seasonal spike the way Makkah's Hajj and Umrah surges are — a barbershop near the Prophet's Mosque sees a consistent flow of multi-day visitors most weeks, which makes short-stay repeat visits, not long-term loyalty, the more realistic target.
A visitor staying three to five days near the Haram might reasonably get a haircut once early in the stay and once again before heading home — that's a real repeat-visit opportunity a purely seasonal city like Makkah's pilgrim peak doesn't offer as cleanly, because Madinah's flow doesn't concentrate into the same overwhelming short bursts.
Geofence catches the same visitor twice in one trip
Geofence messages fire when a customer's phone comes near the branch, Apple Wallet only, up to 10 locations per card, radius 50 to 500 meters (150 m default), set from the Branches screen, at zero message quota. For a shop near the Haram, that's a way to catch a visitor's second pass by the shop during the same stay, even without a win-back trigger that could fire in time — 14 days is longer than most visits.
A short, specific geofence line works better than a generic one here: "Back near the Haram? Quick trim before you head out." It reads naturally to someone who's already walking past for the second or third time that week.
| Customer type | Typical stay/cycle | Best repeat-visit tool |
|---|---|---|
| Multi-day Madinah visitor | 3–5 days | Geofence during the stay |
| Local Madinah resident | ~3-week cycle | 14-day win-back trigger |
| Single-day visitor | One visit | Enroll opportunistically; no repeat tool applies |
The 14-day win-back trigger still matters for residents
Don't let the visitor pattern crowd out the resident side of the business — local Madinah customers follow the same roughly 3-week haircut cycle as any other Saudi city, and the 14-day win-back trigger, checked daily with a 30-day dedupe, works exactly the same way for them as it would anywhere else.
- Local residents: standard 3-week cycle, 14-day win-back trigger
- Multi-day visitors: geofence during the stay, not a win-back message that arrives after they've gone home
- Keep resident and visitor segments separate when reviewing return-rate numbers on the dashboard
- A shop very close to the Haram will see a higher share of visitor traffic than one further into a residential neighborhood
A visitor-heavy location fills the Free ceiling faster
A shop near the Haram enrolling both residents and multi-day visitors will reach Free's 100-customer ceiling faster than a purely residential-neighborhood shop, simply from higher overall foot traffic. That's not a problem — Free is designed as a real trial, not a permanent home for a busy location — but it's worth planning the move to Growth before the ceiling actually pauses new enrollments.
Set up the split in five steps
Nothing here requires a different product — just deliberately separating two customer types that behave differently.
- Set the geofence radius for the shop's exact location
A shop right on a Haram-adjacent street can use a tighter radius since foot traffic is already dense.
- Write a visitor-specific geofence message
Something short referencing being near the Haram, distinct from the resident win-back copy.
- Turn on the standard win-back trigger for residents
It fires the same way here as anywhere — 14 days, daily check, 30-day dedupe.
- Tag repeat local customers as residents
So campaigns and dashboard review can separate the two segments.
- Plan the Growth upgrade ahead of the ceiling
Watch the customer count and move up before enrollment pauses, given the location's likely higher volume.
The same limits apply regardless of foot traffic
A high-traffic Haram-adjacent shop doesn't get an exception to Waya's core limits: no POS or till integration, so a barber scans every card by hand on an ordinary phone, and no SMS — every message, geofence or trigger, lands on the wallet lock screen only. The Android merchant app is in closed testing, so staff use the web dashboard or the Waya iOS app on the floor either way.
Frequently asked questions
Does visitor traffic in Madinah change how a barbershop should run loyalty?
Yes — Madinah's visitor flow is steady year-round rather than a sharp seasonal spike, which makes short-stay repeat visits during a single trip a realistic target, mainly through geofence, alongside the standard win-back trigger for local residents.
Can geofence catch a visitor who's only in Madinah for a few days?
Yes — geofence fires whenever the customer's phone is near the branch, which can happen more than once during a multi-day stay near the Haram, unlike the 14-day win-back trigger, which is usually too slow to fire before a short visit ends.
Should a Madinah shop treat visitors and residents the same?
No — separate them. Local residents follow the standard 3-week cycle and benefit from the 14-day win-back trigger, while multi-day visitors are better reached through geofence during their actual stay.
Does a Haram-adjacent shop reach the Free plan's ceiling faster?
Often, yes, simply from higher combined resident and visitor foot traffic. Planning the move to Growth before the 100-customer ceiling pauses new enrollments avoids a mid-month scramble.
Does Waya's Android merchant app work for a busy Madinah shop's staff?
The Android merchant app is currently in closed testing, so staff on Android use the web dashboard instead, alongside the Waya iOS app — the same setup as any other Saudi city.