Push notifications, web and mobile

Web Push API, mobile app push, subscription, quiet hours, A/B campaigns

Push notifications

Two platforms: browser (web push) and mobile apps (Customer and Staff). Push is instant, customer doesn't need to open email.

Web push (browser)

How it works

  • Customer opens the customer portal
  • Enables push ("Allow browser to...?" prompt)
  • Service Worker registers
  • Bookinda sends push via VAPID keys

Where you configure

  • Tenant: /manager/connect/push – you can subscribe too, to get push for salon events
  • Customer: /myaccount/notifications – per-trigger toggles

Trigger types (tenant)

20+ events in 8 categories:

  • Bookings (online, cancellation, reschedule)
  • New customer
  • Payments
  • Packages
  • Reviews
  • Waitlist
  • Meetings

Trigger types (customer)

16+ events in 7 categories:

  • Booking reminder
  • Booking confirmation
  • Loyalty points reward
  • Package expiry warning
  • Promotion
  • Waitlist slot freed
  • Group class reminder

Quiet hours

Time window when no push (e.g., 22:00-08:00). Customer sets it on their profile.

Multiple devices

A customer can subscribe from up to 3 devices (phone, tablet, desktop). Each independently controlled.

Mobile app push

Bookinda Customer app

Customer downloads, gets push for their bookings, loyalty points, promotions.

Bookinda Staff app

Staff downloads, gets push for new bookings, cancellations, shift changes.

Expo SDK

Mobile push goes via Expo SDK. Bookinda stores the token, sends through it.

Push campaigns (SuperAdmin)

/superadmin/push-campaigns page.

Features

  • New campaign: title + body + call-to-action
  • Variant A/B: two text versions, split %
  • Targeting: all customers / by tier / by role / by tenant
  • Scheduling: send now or future date
  • Test send: send to yourself first
  • Stats: sent, delivered, clicked

A/B test logic

  • Variant A: "Don't miss Black Friday!"
  • Variant B: "30% off tonight!"
  • 50/50 split → each goes to half
  • Result: see which won by click rate after a week

When to use it

Scenario 1, salon-internal push (you) Manager → Connect → Push → "New online booking" trigger on. Subscribe at reception → push for every new booking. No need to refresh email.

Scenario 2, customer booking reminder Customer downloads Customer app. Configures: booking reminder 24h before. Push arrives, opens app, confirms.

Scenario 3, marketing campaign Black Friday: 500 subscribers. One push: "30% off tonight, book now." 50% click = 250 booking attempts.

Scenario 4, A/B test Two text versions. 1000 customers, 500-500 split. A week later: A 8% click, B 12% click. → B wins, use it next campaign.

Scenario 5, waitlist slot freed Push: "Slot opened at Monday 10:00 yoga! Book now." Someone books in 1-2 minutes.

Tips

  • Push's strength is immediacy, don't send things that can wait (e.g., monthly newsletter belongs in email).
  • Quiet hours on by default is recommended, 22:00-08:00. Push at night is annoying.
  • Title should be punchy, max 50 chars. Body max 100 chars.
  • CTA must be clear: "Book now," "See more," "Tap here." Not generic.
  • A/B test should run at least a week, less = inconclusive.
  • Smaller segment targeting is even better: Gold-tier only, last 30 active days only. Relevant and not noisy.
  • Web push subscription is rare (1-5% rate), but who stays is engaged. Mobile app rate is better (10-20%).

Related articles

#push#web-push#mobile#expo#campaigns#a-b-test#quiet-hours
💬

Have a question? Ask the AI assistant

The Bookinda AI knows the entire help center and can answer in seconds.

B

Bookinda AI Assistant

Ask anything about features, settings, or integrations.

Hi! I'm the Bookinda assistant. I can answer questions about features, billing, integrations, and more. What would you like to know?

Still need help?

Get in touch with our support team.

Contact us