How should a barbershop schedule loyalty messages around Friday prayer timing?

Queue Friday sends before Jummah or after Asr

Schedule Friday loyalty sends to land before the Jummah rush or after Asr, and mark the prayer-and-lunch closure as closed in the shop's working hours — Waya's scheduled campaigns respect those hours automatically, so anything queued during the closed window simply waits and sends at the next open slot instead of landing mid-prayer.

Friday carries a shape no other day does for a Saudi barbershop: a pre-Jummah wave of men wanting a fresh cut before prayer, a dead stretch through the closure, and a second wave from late afternoon into the evening. A generic weekday send schedule ignores that shape completely and risks a message arriving right as customers are heading to the mosque.

The mechanics are simple once the working-hours field is set correctly: Waya's campaign tools let you pick a send time, and the dashboard does the rest. Pair that with the barbershop guide's 3-week cycle timing and Friday becomes a planned spike instead of a scramble.

The shape of a Friday, hour by hour

Most single-chair and multi-chair barbershops see roughly the same pattern on Fridays, even if the exact hours shift by 30 to 60 minutes from shop to shop. Map your own hours against this shape before scheduling anything, rather than reusing a Monday-to-Thursday send time.

Write two message drafts, one for each wave

Write a separate line for each Friday wave instead of reusing one message for both — the pre-Jummah customer is planning ahead, the post-Asr customer is deciding on the spot, and a single all-day message reads stale by the second wave.

• "Fresh cut before Jummah? 3 chairs open until 11."
• "Evening slots open after Asr — book your usual chair."
• Keep both under 100 characters so the full line shows on the lock screen
• Avoid one message meant to cover the whole day — write two shorter ones instead

Quiet hours are a dashboard setting, not a guess

The prayer-and-lunch closure isn't something you work around by guessing a safe gap — it's the shop's working-hours setting in the dashboard, the same field every scheduled campaign checks against. Set it once for Friday and every future campaign inherits it automatically, so nobody has to remember the cutoff by hand.

Automatic triggers — welcome on enrollment, stamp added, reward redeemed, and the 14-day win-back message — fire on real events rather than a fixed schedule, checked daily with a 30-day dedupe on the win-back message, so they aren't governed by the working-hours field the same way scheduled campaigns are. Keep trigger copy generic enough that firing at an odd Friday hour doesn't feel out of place.

Why Friday needs two campaigns, not one

A single Friday message covering both waves under-serves whichever wave it wasn't written for. Running the pre-Jummah and post-Asr messages as two separate scheduled campaigns needs enough concurrent-campaign headroom to hold both live at once.

Campaign concurrency scales with plan: the Free plan can't run a scheduled campaign at all, Growth allows 2 active campaigns at a time, and Premium is unlimited. A shop wanting both Friday waves running as separate campaigns every week needs at least Growth.

Build a Friday-safe campaign in five steps

None of this requires new tooling — it's the same campaign screen used for any other send, just pointed at Friday's shape.

1. Set Friday's working hours

   Mark the prayer-and-lunch closure as closed in the dashboard so every scheduled send checks against it.

2. Draft two messages

   Write one line for the pre-Jummah rush and a separate line for the post-Asr wave.

3. Pick the audience

   Send to everyone, a lifecycle segment, or a hand-picked list depending on how targeted the Friday push needs to be.

4. Schedule both sends

   Queue the pre-Jummah message for the morning and the post-Asr message for late afternoon.

5. Check the campaign log

   Confirm after Friday that neither send landed inside the closed window, and adjust the hours if it did.

Plan around the message and campaign ceilings

Waya has no SMS channel — every message here lands on the wallet lock screen, on Apple Wallet or Google Wallet — and the Free plan can't run a scheduled campaign at all. Growth's 5,000 messages a month and 2 concurrent campaigns cover a weekly two-wave Friday schedule comfortably for most single- and multi-branch shops; Premium removes both ceilings entirely.

If a shop is still on Free and under 100 customers, the automatic triggers (welcome, stamp, reward, 14-day win-back) still run — it's only the scheduled Friday campaign that needs Growth or above.