Don't put bridal clients on the routine reward cycle — use a referral-style campaign instead
A salon should structure loyalty around bridal packages using a hand-picked campaign and referral incentive, not the routine stamp or points cycle everyone else is on. A bride typically books once, spends heavily on a single high-value package, and may not return to a normal visit rhythm for months or longer — a stamp card built around weekly-to-monthly cycles simply doesn't fit that pattern.
The real loyalty opportunity with a bridal client isn't her own repeat visits — it's the referrals she generates. A bride's wedding party, mother, and friends are a captive, high-intent audience already primed to book the same salon. That's where the loyalty mechanic should point.
Enroll her on the standard card anyway, since it costs nothing extra and captures any visits she does make later, but treat the real program as a targeted campaign around her booking, not the everyday reward cycle.
- Bridal clients: one large, infrequent purchase — a poor fit for a routine visit-based reward
- The real audience: her wedding party and family, who are easy to reach through her
- Enroll bridal clients on the standard card anyway, but don't expect the routine cycle to drive her behavior
- Use a hand-picked or referral-style campaign as the primary bridal mechanic instead
Routine stamp cycle vs. bridal referral campaign
These two mechanics are aimed at completely different behaviors — one at repeat visits from the same person, the other at new clients introduced by one.
| Mechanic | Targets | Timing |
|---|---|---|
| Routine stamp/points cycle | The bride's own repeat visits | Weeks to months — doesn't fit a once-a-year event |
| Hand-picked bridal campaign | The bride herself, around her booking date | One-off, tied to the wedding date, not a routine schedule |
| Referral incentive | Her wedding party and family | Triggered by her booking, reaches new clients |
A worked example: a 2,000 SAR bridal package
A bride books a 2,000 SAR bridal hair-and-makeup package for her wedding day. Treating that purchase like a routine stamp-card visit gets her one stamp toward a threshold she may never reach, since she's unlikely to book again soon. Instead, Waya's campaign tools let you send her a hand-picked, one-off message inviting her wedding party to enroll with a specific incentive — a discount on their own booking, tied to her wedding date rather than a routine trigger.
That single 2,000 SAR booking can realistically introduce five or six new potential clients through her party — a far bigger loyalty opportunity than getting her personally to a 5-stamp threshold she may not reach for a year.
Scheduling around the wedding date, not a routine cadence
Bridal-related sends work best pegged to the actual event date rather than a generic weekly or monthly rhythm — a message that goes out two weeks before the wedding, referencing the date, reads as considered rather than automated. Scheduled campaigns respect the shop's working hours, so a send queued outside opening hours simply moves to the next open slot rather than landing oddly timed.
Ramadan and Eid seasons often cluster bridal bookings tightly in Saudi salons, which makes date-linked scheduling even more important than during a normal month — a generic monthly campaign misses the actual rush entirely. See the salon loyalty program guide for how bridal season fits into the wider calendar.
A referral message example
Keep the referral message specific to the occasion rather than a generic promotional line.
For example: "Congratulations again! Share this with your bridal party for a treatment discount." Short, occasion-specific, and gives her a reason to actually forward it.
Free plan is enough to run a bridal campaign, with limits to plan around
Free is 0 SAR forever with 100 messages a month — enough for occasional bridal campaigns at a lower-volume salon, though a busy bridal season may need Growth's 5,000-message allowance if you're running frequent targeted sends alongside routine triggers for everyone else.
One limit worth stating plainly: Waya has no POS or till integration, so a staff member scans the bride's card manually, and there's no SMS channel — the referral message reaches her through the wallet lock screen only, so she needs the card added before you can message her at all.
Set up bridal-package loyalty in four steps
This runs alongside your existing stamp or points card — it's an addition, not a replacement.
- Step 1: enroll bridal clients on the standard card
Costs nothing extra and captures any future visits automatically.
- Step 2: build a hand-picked bridal audience
Tag or list bridal clients separately from routine regulars.
- Step 3: schedule a date-linked referral message
Time it around the wedding date, not a routine monthly cadence.
- Step 4: track referrals through new enrollments
Watch the dashboard for new sign-ups following each bridal campaign send.
Frequently asked questions
Should bridal clients be on the same loyalty card as regular clients?
Enroll them on the standard card anyway since it costs nothing, but don't expect the routine reward cycle to drive her behavior — a bride typically books once and may not return for months, which doesn't fit a stamp or points cycle.
What's the better loyalty mechanic for bridal packages?
A hand-picked, date-linked referral campaign aimed at the bride's wedding party and family, rather than the routine stamp or points cycle. A single bridal booking can introduce several new clients through referrals.
When should a bridal campaign message be sent?
Pegged to the actual wedding date rather than a routine weekly or monthly schedule. Scheduled campaigns respect the shop's working hours, so a send outside opening hours simply moves to the next open slot.
Does a bridal referral campaign use a lot of the monthly message quota?
A single targeted send to one bride uses very little quota. Free's 100 messages a month covers occasional bridal campaigns; a salon running frequent bridal-season sends alongside routine triggers may need Growth's 5,000-message allowance.