What Should a Booking App Have? A Guide for Salons, Clinics and Consultants

We wrote this guide for hair salons, beauty studios, clinics, fitness studios and consultants. At Talha Aslan and team, our mobile app development projects often cover the booking flow from the first screen to the last reminder. Before you decide anything, put the following checklist on the table:

1. Write down which services you offer, who delivers them and how long each one takes.
2. Decide how many taps a customer should need to finish a booking.
3. Turn reminders, deposits and cancellations into a written business policy.
4. Define who can see what inside the business dashboard.
5. Plan where personal data will live and who can access it.
6. Compare an off-the-shelf platform and a custom app using the same criteria.

How do salons, clinics and consultants differ in their booking needs?

All three follow the same "pick a time, confirm" pattern. However, the rules behind the screen differ a lot. Seeing those differences early saves you from expensive changes later. For example, a salon client may book several services in one visit. A clinic, on the other hand, has to schedule rooms or equipment alongside people.

• Salons and beauty studios: Multiple services per visit, durations that vary by service, a preferred stylist and a dense, short-slot calendar.
• Clinics: Shared resources such as rooms or devices, longer sessions, follow-up visits and stricter data protection.
• Consultants: Video call links, time zone differences, session packages and a short intake form before the meeting.

Therefore, one generic booking screen rarely fits every sector. We start by mapping one full working day of the business. After that, we design the screens around that flow. As a result, the app mirrors how the business really works, not the other way around.

How does the calendar screen get customers to a booking fast?

The calendar is the heart of a booking app, because this is where the customer decides. Its job is to show an open slot with as little thinking as possible. For that reason, a horizontal day strip with time chips below it usually works better than a full month view.

You also need to decide whether to hide booked slots or show them grayed out. Hiding them keeps the screen clean. On the other hand, grayed-out slots signal that the business is in demand. Both approaches work, as long as you stay consistent.

In practice, these principles help:

• Show today's and tomorrow's open slots on the first screen.
• Make time chips large enough for a comfortable thumb tap.
• Keep the duration of the chosen service visible while the customer picks a time.
• Add a single button that suggests the next available slot.

In short, the calendar should not display everything the business knows. Instead, it should answer the customer's one question: "Which open slot suits me best?"

Why is staff-level availability a must-have feature?

Staff-level availability means each employee has their own working hours, days off and list of services. Without it, the app can book a customer with someone who is not actually free. Then both the customer and the staff member end up in an awkward spot.

For example, if only two stylists in a salon do color, the system should not offer color with anyone else. Likewise, lunch breaks, training days and vacations belong in the calendar too. Moreover, when staff can check their own schedule on their phone, the owner spends far less time answering questions.

On the customer side, we recommend two options. The first is "any available staff," where the system assigns the first free person. The second is choosing a specific person, which regular clients usually prefer. This way you serve new customers who want speed and loyal clients who want continuity. The same structure also makes commission and performance reports easier later.

Should staff calendars sync with their personal calendars?

Many professionals, especially consultants and independent stylists, live inside their phone calendar. For them, a link between the booking app and their personal calendar is a big relief. Otherwise, it becomes easy to double-book a private errand and a client.

Sync has two directions. The first sends each booking from the app into the staff member's calendar; this one-way link is fairly simple. The second automatically blocks app slots when the personal calendar shows a busy time. That two-way link adds more value, but it also adds more development and testing work.

So we usually suggest launching with one-way sync and moving to two-way sync once the need is clear. In addition, the dashboard should include bulk closing for public holidays, closure days and special opening hours. That way, you never have to block slots one by one before a holiday or a maintenance day.

How should you set service duration and buffer time?

The most common scheduling problem is a booking that fits on paper but not in real life. Usually, the cause is a single fixed duration per service. In reality, prep work, cleanup and a short pause also take time from the calendar.

That is why we recommend three separate fields for every service:

1. Service time: The real time the client spends in the chair or the room.
2. Prep time: Equipment or room setup that has to happen before the service.
3. Buffer time: Cleanup, note taking or a margin for delays after the service.

Some services also include a waiting gap. For example, while hair color processes, the stylist can take care of another client. An advanced booking app can open that gap for a short service. That said, you do not need this in version one. Get the basic durations right first, then add the finer logic.

How should reminder notifications work in a booking app?

Reminder notifications are the cheapest way to cut missed appointments. Still, setting them up correctly also means following store rules. Guideline 4.5.4 of Apple's App Store Review Guidelines says push notifications must not be necessary for the app to function. The same guideline says promotional pushes need explicit opt-in inside the app and a way to opt out.

On Android, the runtime notification permission introduced in Android 13 applies. Google's notification permission documentation recommends asking in the right context and letting users get familiar with the app first. In a booking app, the most natural moment is right after the first booking confirmation. We cover timing in detail in our guide on when to ask for push notification permission.

We typically recommend two reminders: one the day before and one a few hours before. Also, adding a "reschedule" link inside the reminder turns many no-shows into reschedules.

Does a booking deposit count as an in-app purchase?

No. A deposit for a service delivered in a salon or a clinic falls outside the stores' in-app purchase systems. Guideline 3.1.3(e) in Apple's rules says that for physical goods or services consumed outside the app, you must use other payment methods, such as Apple Pay or traditional card entry.

Google takes a similar line. The Google Play Console payments policy says Google Play's billing system must not be used when payment is mainly for physical services. Therefore, you collect booking deposits by card through a payment provider. However, the rules change if the app sells digital content, such as a paid video course. We compare both paths in our article on in-app purchase vs web payment.

The deposit amount is a business decision. Instead of one flat amount, we suggest deposits that vary by service. That way, you balance the cancellation risk better on long, high-value services.

How should you design cancellation and no-show rules?

A cancellation policy should protect the business without frustrating the customer. The key to that balance is transparency. Before confirming, the customer should clearly see the cancellation window and what happens to the deposit. A surprise rule after the fact is one of the most common causes of bad reviews.

A typical setup follows these steps:

1. Allow free cancellation and one-tap rescheduling up to a set time before the booking.
2. State in advance what happens to the deposit after that window closes.
3. Flag no-shows in the dashboard and require a deposit from repeat no-shows.
4. Reopen a canceled slot instantly and notify the people on the waitlist.

As an example scenario, picture a consulting office. When a client cancels at the last minute, the consultant can offer the slot to waitlisted clients by notification. In other words, a cancellation becomes a new booking instead of a loss. We suggest the business set time windows and amounts based on its own policy and check them against consumer law with a legal advisor.

How does a waitlist fill empty slots?

A waitlist lets a customer queue for a slot that is already taken. In busy businesses, the most valuable times, such as weekend afternoons, often fill up days in advance. When someone cancels, filling that gap by phone takes effort.

The app can automate this. The customer picks a preferred day and time range, and the system notifies them when a slot opens. That said, you need a fair rule. Two common methods exist:

• Queue order: The open slot goes to the first person on the list for a limited time, then moves to the next person.
• First come, first served: Everyone gets the alert at once, and the first person to confirm gets the slot.

Queue order feels fairer, while first come, first served fills the slot faster. So the choice depends on how much weight the business puts on the client relationship. In both cases, alerts should only go to customers who allowed booking notifications.

How do you make reviews and ratings trustworthy?

In-app reviews build trust for new customers; however, a system where anyone can post loses value quickly. That is why we recommend allowing reviews only from customers whose appointment actually happened. As a result, every review ties back to a real visit.

Timing matters too. A short prompt a few hours after the service catches feedback while the experience is fresh. Moreover, keeping ratings per staff member shows the owner who excels at which service.

There is one subtle point. In-app reviews and the store rating measure different things. The store rating judges the app itself, while in-app reviews judge the business's service. Keep the two separate. To ask for a store rating, use the platforms' own system prompts, and do not filter for happy users before sending them there. In addition, letting the business reply to negative reviews from the dashboard builds confidence.

Which jobs should the business dashboard handle on one screen?

No matter how polished the customer app is, a weak dashboard means staff will not use the system. The dashboard is the screen the front desk and the owner keep open all day. Consequently, speed and simplicity matter here too.

A good business dashboard lets you:

• See the daily and weekly calendar with one column per staff member.
• Add a phone booking manually in a few taps.
• Drag a booking to another time or another staff member.
• View client history, notes and no-show records.
• Track deposits, refunds and payment status.
• Message clients who opted in to offers or announcements.

A web-based dashboard is often more practical, because the front desk usually works on a computer. On the other hand, staff members also need to see their own schedule on their phones. Role-based access, meaning each person sees only the data they need, adds both security and order.

Should customers have to create an account?

Mandatory sign-up is the step where most first-time bookings fail. For that reason, consider letting customers book the first time with phone verification and no account. You can then offer the benefits of an account, such as booking history and quick rebooking, on the second visit.

As an example scenario, imagine a regular client. On the first visit, they book with just a phone number. On the second visit, the app asks, "Should we save your details?" and creates an account in one tap. That way, sign-up feels like a time saver rather than a hurdle. It also keeps your account base limited to people who actually come back.

However, once you offer accounts, store rules apply. Apple's guideline 5.1.1(v) says apps that support account creation must also offer account deletion inside the app. Google's Google Play account deletion requirements ask for an in-app path plus a web link. We explain this rule in our post on Apple's mandatory account deletion rule. Plan the deletion flow from day one, because adding it later can cost you an extra review round.

What data protection rules apply to booking data?

A booking app handles names, phone numbers, appointment history and sometimes staff notes. Therefore, privacy law applies, for example the GDPR in the EU and the UK or KVKK in Turkey. In clinics, notes may contain health information, which these laws treat as a special category with stricter protection.

In practice, we suggest planning these points early:

• Make the privacy notice easy to reach inside the app.
• Keep marketing consent separate from booking reminders.
• Limit access to staff notes by role.
• Put your retention period and deletion method in writing.

Also, Apple's guideline 5.1.1(i) requires a privacy policy link both in App Store Connect and inside the app. We collected the matching web steps in our guide on how to build a GDPR compliant website. This section is not legal advice; have a qualified lawyer review your texts.

Off-the-shelf platform or custom booking app?

Your budget and growth plan should drive this answer. Off-the-shelf platforms get you started fast, but your brand stays one listing among many. A custom app runs under your own brand and rules; in return, it brings development and maintenance duties. The table below compares both paths on the same criteria:

As an example scenario, a single-location salon with two stylists may do well on a platform. In contrast, a chain with several locations and a loyalty program gains more flexibility from a custom app over time. We break down the cost drivers in our article on what determines mobile app development cost.

What makes app review hard for booking apps?

One major hurdle for booking apps is the template rule. Apple's guideline 4.2.6 says apps created from a commercialized template or app generation service will face rejection unless the provider of the app's content submits them directly. In other words, a vendor that publishes the same template as hundreds of separate apps for its clients runs into trouble.

That is why it matters to publish a custom app from the business's own developer account. When we build and ship an app, we recommend that the store account belong to the business. As a result, ownership stays clear from the start.

Other issues can also come up during review:

• No working demo account for screens that need a login.
• A missing or broken privacy policy link.
• An app that offers no more value than a basic website.

We gathered the most common rejection reasons in our post on why your app was rejected.

Which features belong in version one?

Building every feature on day one inflates both timeline and budget. Instead, we recommend launching the smallest working product and measuring real use. We explain the general approach in our post on what a mobile app MVP is; here we apply it to bookings.

For the first version of a booking app, we suggest this order:

1. Service and staff selection with a real-time calendar.
2. Fast booking with phone verification and a confirmation screen.
3. A reminder notification before the appointment.
4. Self-service cancellation or rescheduling for the customer.
5. A basic dashboard where staff can add bookings manually.

Deposits, reviews, a waitlist and loyalty points are strong candidates for phase two. For example, if your no-show rate is low, you can safely postpone deposits. That way, version one ships quickly and you pick next steps based on real data.

App, booking website or PWA: which one fits?

Not every business needs an app in the stores. If most of your clients visit once or twice a year, downloading an app is an extra step for them. In that case, an appointment booking website does the same job with less friction.

However, for frequent clients, such as people who get a haircut every month or buy session packages, an app brings real advantages. The home screen icon, saved details and notifications make rebooking much faster. Loyalty programs also feel more natural inside an app.

A progressive web app (PWA) sits in between; it runs in the browser but can live on the home screen. We compare all three in our guide on mobile app or PWA. In practice, many businesses start with a website and move to an app once their base of returning clients grows.

How do you handle multiple locations and staff permissions?

A structure that looks simple with one location gets complex with the second. The customer should choose a location first, then a service and a staff member. Also, a staff member may work at another location on certain days of the week.

So we recommend a multi-location data model from the start, even if version one has a single location. With a solid foundation, adding a location later is just a setting. Otherwise, you may need to rewrite much of the calendar logic.

A simple role structure covers permissions:

• Owner: Sees all locations, reports and settings.
• Location manager: Manages the calendar and staff of one location.
• Staff member: Sees only their own bookings and client notes.

This way, you protect data privacy and give every user a clean screen.

Why do accessibility and language options matter?

Older clients use booking apps as much as younger ones. Small text, low-contrast buttons and icon-only actions make life hard for them. Consequently, accessibility goes beyond good intentions; it directly affects how many bookings you get.

A few rules solve most problems. Text should scale with the phone's system setting, buttons should carry text labels and screen readers should read time chips correctly. Also, color alone should never carry meaning; a taken slot needs a "booked" label, not just a gray tint.

For businesses in tourist areas or with international clients, language options matter too. For example, a beauty studio that serves visitors may see more bookings with an English interface. Planning for this in version one is far easier than pulling strings out of the code later.

Which booking app metrics should you track?

After launch, you need to measure whether the app works. Otherwise, product decisions rely on gut feeling. In our booking app projects, we suggest putting a few core metrics on the first dashboard screen.

• Booking completion rate: The share of people who open the calendar and confirm a booking.
• No-show rate: The share of confirmed bookings where the client never arrives.
• Late cancellations: Cancellations after the free window closes.
• Rebooking: Whether a client books again within a set period.
• Utilization: How much of each staff member's open time gets booked.

For example, a low completion rate usually points to the calendar screen or forced sign-up. If no-shows run high, review reminder timing first, then the deposit rule. That way, every development round ties back to a measurable problem.

How does booking app development work step by step?

The process starts with clear business rules, long before any code. If you skip this stage, even the best design answers the wrong question. Our sequence looks roughly like this:

1. Discovery: We document services, durations, staff, cancellation and deposit rules with you.
2. Flow design: We sketch customer and business screens and count the taps.
3. Interface design: We create the visual design with your brand colors and type.
4. Development: We build the app, the dashboard and the payment integration.
5. Testing: We run a trial week with real staff and volunteer clients.
6. Store launch: We prepare privacy texts, screenshots and review notes.
7. Monitoring: We track metrics in the first weeks and plan version two.

Timeline and budget depend on scope and integrations. That is why we prefer to define the scope together before quoting any number. On the tech side, a single codebase for iOS and Android is enough for most booking projects.

Where should you start your booking app project?

The best starting point is to write down one full day of your business. Which services do you offer, how long do they take and who delivers them? Where do phone bookings end up today? What happens when a client does not show up? The answers define the scope of the app.

Next, compare the platform and custom options using the table above. If you choose an app that runs under your own brand and rules, we can handle the whole process. We build your app, we publish it to the stores, and after launch we plan updates with you.

To get a quote for your scope, fill in the quote form on our mobile app development services page. Share your number of services, staff and locations, plus your payment needs. Then we can come back with a realistic scope and timeline.