How do I set up geofence notifications for a salon location?

Set the radius from the Branches screen, not the card's address field

Setting up geofence notifications for a salon means going to the dashboard's Branches screen and setting a radius there — anywhere from 50 to 500 meters, with 150 m as the default — which is a separate step from typing your address into the card itself. A common mistake is assuming the address on the card automatically creates a geofence; it doesn't.

Geofence puts your message directly on a client's lock screen the moment her phone comes within that radius of your branch, at zero cost against your monthly message quota — it's the one Waya feature that doesn't draw from your message balance at all.

That zero-cost detail is worth sitting with for a second: every broadcast and every automatic trigger draws from the same shared message balance, but a geofence notification firing a hundred times a day for a busy mall location costs exactly the same as it firing once — nothing.

Where geofence works best for a salon

Geofence is strongest for a salon in a mall or a dense shopping street, where clients are already walking distances measured in meters throughout the day — a genuinely frequent, real proximity event rather than a rare coincidence. See the salon loyalty program guide for more on mall-location salons specifically.

It's weaker for a standalone salon on a quiet residential street, where clients mostly drive directly to and from appointments rather than passing by casually. That doesn't make it useless there, just less likely to fire often — a home-service or residential-street salon may see it trigger a handful of times a week rather than dozens.

• Mall or shopping-street locations get the most value from geofence
• Standalone residential-street salons will see it fire less often
• Geofence is Apple Wallet only — it doesn't extend to Google Wallet clients
• Google Wallet uses its own separate proximity trigger you don't control

What the geofence setup screen shows

The Branches screen shows each of your locations with its own radius slider, ranging from 50 to 500 meters, defaulting to 150 m if you don't adjust it.

This screen is a Growth-plan feature and above — geofence settings aren't available on the Free plan, though the underlying wallet card still works normally without it.

Setting up geofence for your salon in five steps

This takes a few minutes once you're on Growth or above.

1. Open the Branches screen

   Find your salon's location listed with a radius setting, separate from its address text.

2. Set the radius

   Start at the 150 m default unless you have a specific reason to widen or narrow it.

3. Write a short proximity message

   Something specific to walking by, like a same-day slot being open.

4. Confirm the branch address is accurate

   An outdated address means the geofence triggers in the wrong place entirely.

5. Test with your own phone

   Walk near the branch with the card added to confirm the lock-screen message appears.

A message that only makes sense because of geofence

The best geofence message references the fact that she's physically nearby right now, which is exactly the kind of specificity a scheduled campaign or trigger message can't replicate.

Keep it short, since lock-screen space is limited, and make it actionable — a reason to walk in today, not a general reminder about the salon.

Geofence needs Growth — everything else can start on Free

Geofence settings sit on Growth (85 SAR/month or 867 SAR/year) and above, so test your card, staff scanning, and message triggers on the Free plan first, then add geofence once you're ready to pay for a multi-branch or advanced feature set. There's no need to rush into it — a salon with consistent scanning and a working win-back trigger will already be capturing most of the value before geofence enters the picture.

One limit to keep in mind: geofence works only for clients using Apple Wallet — Google Wallet decides its own proximity trigger independently, so don't promise the same lock-screen behavior to Android customers. That's a separate limit from the Android merchant app being in closed testing, which affects staff, not client-side wallet behavior.