One connected operating system
Follow the client from first interest to the next visit.
Requests & Waitlist
every ask gets an answer.
Bring booking requests and waitlist demand into one queue, decide with the client’s history in view, and leave a shared activity trail the team can trust.
Get started, it is free
No card requiredFree plan included
Owners and front desks that decide the day
- Requests
- Approvals
- Waitlist
- Offers
- Decisions
- Alerts
Every ask, one visible path to an answer.
Without Requests & Waitlist
- Requests wait in DMs, notes and separate inboxes.
- The client history disappears from the decision.
- Freed time is matched back to demand by hand.
- The next shift cannot see what was promised.
With Requests & Waitlist
- Every request enters one queue with a clear state.
- Service, timing and client context stay together.
- Waitlist preferences follow each live offer.
- Decisions and delivery attempts share one feed.
In practice
1 · The client asks
A client submits a requested service and time through the public profile or booking flow, with contact details for the reply.
2 · The team checks context
The queue keeps the requested service and slot beside visit counts, future bookings and the owner-scoped client record.
3 · One decision leaves the queue
Approve after a live slot check, propose another service or time, or decline. The decision and delivery attempt stay in Activity.
Availability
Public booking is included with every core plan. Email is the reply baseline; enabled usable channels may be added by the workspace rules.
One demand inbox, from first ask to final answer.
Requests, waitlist entries and slot offers stay connected as demand moves between the client and the team.
One queue
Requests arrive with their context
Requested service and time sit beside visit counts, future bookings and a direct client-record link, so the team can decide without opening another workspace.
- Requested service
- Requested time
- Client record
The request arrives with its client
What was asked, and the relationship behind the ask.
The ask
Camille LaurentRequested serviceGel extensions · 90 minRequested timeThu 18 Sep · 15:00SourcePublic profile
Camille LaurentRequested serviceGel extensions · 90 minRequested timeThu 18 Sep · 15:00SourcePublic profileThe client
Visits7 since Feb 2025Last visit21 Aug · RefillNext bookingNone yet
Open client recordGuarded decisions
Approve, propose or decline
Confirm a valid request, decline it or propose another service and time. Approval rechecks the slot before it creates an appointment.
- Approve
- Propose
- Decline
Demand retained
The waitlist keeps the real preference
Service, specialist, location, preferred days and preferred time remain attached while an entry moves from open demand to an offered slot.
- Service
- Specialist
- Time window
The waitlist keeps the real preference
Everything the client told you travels with the entry.
Noor SinghServiceGel extensionsSpecialistSofia BrownLocationOld Town
Preferred datesTueWedFriPreferred timeAfternoon
Nothing is retyped when the entry becomes an offer — only the status moves.
Shared accountability
Every decision leaves a trail
Approvals, declines, proposals, reschedules, offer events and delivery attempts land in the same permission-aware activity feed.
- Decision log
- Delivery state
- Team alerts
From ask to outcome
Every state has a clear next action.
Pending to decided
Pending becomes confirmed, proposed or declined
A client request enters with the requested service and slot. Approve it to create the appointment, decline it or send an alternative when the original ask cannot work.
- Pending requests stay in the needs-action group
- Approval rechecks the slot before creating the appointment
Pending becomes confirmed
One request, one path, one guard in the middle.
Camille LaurentPendingSits in Needs action until somebody answers.Slot recheckThe requested time is checked against the live calendar.ConfirmedThe appointment exists and the client is told.
Declining or proposing another time ends the same request — nothing stays half-open.
Open to closed
Open demand gets first claim on freed time
A waitlist entry starts open, moves to offered when a matching slot is sent and closes when the demand is finished.
- Declined or expired offers return the demand to attention
- The first valid acceptance claims the live appointment window
Open demand claims freed time
The waitlist gets first call on a window that just opened.
Mia NakamuraThe first valid acceptance takes the window.
Client beside ask
The decision pane keeps the relationship in view
Requested service and time stay beside visit counts, future bookings and the client record, so the answer fits both the calendar and the client.
- Direct client-record link when the request is resolved
- Decision permission stays separate from revenue visibility
Shared history
Who decided what stays visible to the right roles
The Activity view combines delivery and audit events for the whole workspace or one selected item.
- Approval, decline and proposal events remain attributable
- Delivery state stays beside the decision that triggered it
Who decided what
Every event keeps its actor and its delivery.
Approved a booking requestDelivered
Offered a freed slotSent
Proposed another timeQueuedRoles that cannot decide still see what was decided.
Where asks begin
Different entry points, one operational inbox
Profile booking, booking links, profile requests, growth leads and booking-change flows all preserve their source as they enter the workspace.
- Public enquiries and slot offers join as their own queue types
- Source stays attached while the request moves to an outcome
Five doors, one inbox
The entry point stays attached all the way to the answer.
Public profileBooking linkPage requestGrowth leadClient reschedule
Amara OkaforBooking linkPendingSource is data, not a label somebody types in later.
3 outcomes
confirm, propose or decline a request
3 states
open, offered and closed waitlist demand
1 feed
for decisions, delivery and audit
€0
to start, no card required
The controls around every decision.
Slot recheck
Approval validates the target again before creating a booking.
Alternative proposals
Offer another service and time when the original ask cannot work.
Preference detail
Keep specialist, location, days and time window with waitlist demand.
Offer recovery
Expired or declined offers return the entry to attention.
Team alerts
New requests and waitlist joins lead back to the shared inbox.
Scoped permissions
Let the front desk decide without exposing finance by default.
Delivery trace
Confirmation and decline delivery attempts remain visible.
Focused activity
Read the whole workspace feed or the history of one selected item.
The Belom platform
Requests & Waitlist is just the beginning
Belom keeps the planner, client history and approved communication connected in one place.
Online Booking
Requests from public booking flows
Planner
Live slot checks and confirmed appointments
Empty Slot Matcher
Guarded offers for freed time
Messages
Questions, proposals and delivery state
Client Memory
History beside every decision
Team roles
Decision access without finance exposure
What the client sees
After approval
A booking confirmation names the service, date and time. Email is the required baseline; enabled connected channels can carry the same lifecycle update.
After a new-time proposal
The client receives the proposed service, date and time with a private link to accept or decline the alternative.
After decline
The client receives a short cancellation message stating that the requested booking will not go ahead.
What it doesn’t do
Belom does not guarantee a reply inside the browser or source surface. Delivery needs a resolved client and a usable contact rail, and remains best-effort after the decision commits.
Built around your results
Open the request queue, decide the oldest pending ask and send a clear answer.
The request stays visible even when a best-effort delivery attempt needs attention in Activity.
Every returning client, filled slot and hour saved adds to the value of your subscription.