If you have a Business App, you can send a message straight to your customers' phones. No inbox to compete with, no spam folder — it arrives on the lock screen.
That directness is exactly why it's worth using carefully.
Sending one
Open the side menu and click Settings.
Under App, click Push Notifications.
Write a Title — up to 40 characters.
Write a Message — up to 150 characters.
Check the Preview.
Click Send.
👀 There's no undo. Once it's sent it's on people's phones. Read it twice — a typo in a push notification is considerably more visible than one in an email.
Who receives it
The Audience panel shows how many devices will get it, split by iOS and Android — "devices which have opted to receive push notifications from your app".
Only customers who've installed your app and allowed notifications are counted. If that number is zero, there's nobody to send to and Styler will tell you so.
💡 Check the number before you write. If your audience is fifteen people, a broadcast may be less use than messaging them individually from their profiles.
Writing one that works
Forty characters and 150 characters are tight, and deliberately so — a push notification is a nudge, not a newsletter.
Lead with the point. Long titles get cut off on the lock screen, and the first few words are what people actually read.
Be specific. "Two spaces left this Saturday" beats "Book now!".
Give a reason to open it. A cancellation, a genuine offer, something time-limited.
💡 Filling a last-minute cancellation is the single best use of this feature. It's immediate, it reaches people who already like you, and it turns an empty slot into revenue.
How often is too often
This is worth thinking about properly, because the cost of getting it wrong is invisible until it's permanent.
People don't complain about too many notifications. They turn them off — or delete the app. And once they have, you've lost that channel for good; there's no way to win them back short of asking them to reinstall.
A reasonable rule of thumb:
No more than once a week, and usually less.
Every message should be useful to the person receiving it, not just to you.
If you can't say what a customer gains from it, don't send it.
💡 A quiet app that sends four genuinely good messages a year is worth far more than one that sends something every Monday.
What you've sent before
The page keeps a history of previous notifications, with Load more for older ones. Worth a glance before sending — it's the easiest way to check you're not repeating yourself or messaging too soon after the last one.
Messaging one person
For a single customer, send from their profile instead — a freed-up slot, or following up a conversation. See the customer profile.
FAQs
❓ A customer says they don't get notifications.
They need your app installed with notifications allowed in their phone's settings, and push enabled on their customer profile. All three have to line up.
❓ Can I target specific customers?
A broadcast goes to everyone with notifications enabled. For anything targeted, message individuals from their profiles.
❓ Can I schedule one for later?
Notifications send when you click Send. Send it when you want it read — a push at 11pm is a good way to get your app deleted.
❓ Do I need consent?
Customers opt in by allowing notifications, and can withdraw at any time. If you're sending marketing rather than service messages, their marketing preferences apply too.