Customers

The regulars are the business. Keep their history.

A returning customer is worth more than a new enquiry, and the difference between the two is whether anyone remembers the last visit. BookLah keeps appointment history, conversation context and payment activity on one customer record that the whole shop can see — within the permissions you set.

Create your workspace See plans

History that survives staff turnover

Past appointments, services taken and payment records stay on the customer, not in one stylist's phone. A new team member opening the record sees what the last one knew.

No-show and deposit signals

Booking status tracking makes repeat no-shows and unpaid deposits visible where the next booking is being made, so the decision to ask for a deposit is an informed one rather than an awkward guess.

Branches and permissions

Multi-branch accounts keep each branch's schedule and staff distinct while the customer record stays shared. Role-based permissions decide who can see financial detail and who can only work the schedule.

Customer records with appointment and payment history
Booking status tracking across the day
Branch, service and staff structure
Role and permission controls per team member

Questions

Can staff be limited to their own branch?

Yes. Access is permission-aware and scoped, so a team member sees the branches and data their role allows.

What happens to customer data if a customer asks to stop messages?

A stop request is recorded, but it does not by itself guarantee that every connected system immediately blocks or deletes the record. The privacy policy sets out what BookLah does and what remains the business's responsibility.

Keep reading

WhatsApp bookings

Keep WhatsApp enquiries, appointments and customer history in one workspace. Link a number, use templates, and keep AI replies under staff control.

Invoicing and payments

Issue invoices, take FPX payments through Billplz, and share receipts by link. Every document stays connected to the booking that created it.