One connected operating system
Follow the client from first interest to the next visit.
Rebooking Radar
every client on their own rhythm.
Belom learns when each client normally returns, then brings the right names forward when they are due or overdue-so the next visit does not depend on watching every pattern yourself.
Get started, it is free
No card requiredFree plan included
Solo specialists and teams that live on repeat visits
- Cadence
- Drift
- Due lists
- Reminders
- Kill-switch
- Languages
Return timing without the guesswork.
Without Rebooking Radar
- Every client gets the same fixed reminder interval.
- Regulars drift until somebody notices the quiet.
- Future bookings and recent contact are checked by hand.
- Outreach starts from a blank message each time.
With Rebooking Radar
- Completed visits shape a cadence for each repeated service.
- Due, overdue and at-risk clients arrive in a clear order.
- Future bookings, cooldowns and opt-outs keep the list honest.
- A personal draft uses the service and language on file.
In practice
1 · Rebooking Radar
Completed visits, repeated services and each client’s cadence show who is due, overdue or already booked to return.
2 · Today’s Opportunities
The daily surface places that due-client signal beside requests, waitlist matches and other work that needs a decision.
3 · Automations
Rule-based sending is a separate choice: it applies the enabled channel, consent, cooldown and volume controls after a signal exists.
Availability
Radar can be used without automatic sending. Delivery depends on a usable allowed rail and the workspace plan or add-on entitlement.
A personal rhythm for every returning client.
Real visit history becomes a practical signal, with clear control over when Belom should surface, prepare or send the next step.
Personal cadence
Real visits set the rhythm
Belom groups completed visits by repeated service and learns the gaps between them instead of applying one return rule to everyone.
- Completed visits
- Per service
- Personal gap
Real visits set the rhythm
Completed visits of the same service, and the gaps Belom measures between them.
Mia NakamuraRepeat client24 Apr34d28 May36d3 Jul33d5 Aug37d11 Sep
Personal cadence≈ 35 daysNext duein 3 days
Evidence6 completed visitsScopeThis service onlyFallbackService interval, 28d
Due, then overdue
Drift becomes a useful queue
See who is due soon, overdue or drifting at risk, ordered so the return conversations that matter most come forward first.
- Due soon
- Overdue
- At risk
Drift becomes a queue
The same clients, sorted by how far past their own rhythm they are.
Due soon76
Yuki Sato
Noor Singh
Sofia BrownOverdue45
Sofia Brown
Marco Rossi
Lena HoffmannAt risk33
Mia Nakamura
Amara OkaforDDaniel BrooksA client moves bucket when their own rhythm says so, not on a fixed calendar date.
Personal outreach
A reminder, not a blast
Belom can prepare a short service reminder in the client’s saved language, ready for review or delivery through an allowed channel.
- Service context
- Saved language
- Channel choice
Owner control
You keep the switch
Run radar only, review prepared outreach or allow automatic sending inside your limits, with a client-level marketing switch always available.
- Manual
- Assisted
- Automatic
From history to action
The return engine stays close to the work.
Learn the cadence
Completed visits supply the timing evidence
Each repeated service keeps its own return rhythm. The model becomes more confident as the client builds a repeat history.
- Service intervals or the workspace default cover early history
- Future bookings keep clients out of the chase list
Read the drift
The queue shows who needs attention now
Due, overdue and at-risk signals stay easy to scan, with recent contact and confirmed returns removed before they become noise.
- Urgent return conversations rise first
- Source timing stays attached to each signal
What the queue removes
Signals that are not work never reach the list.
Mia NakamuraAt risk
Camille LaurentDue soonBooked 18 SepMarco RossiOverdueEEmma ReedDue soonContacted 3d ago
Yuki SatoOverduePrepare the nudge
Service context becomes a personal reminder
When outreach is allowed, Belom prepares plain wording from the client, last visit, service and saved language.
- Email is the base; SMS or a connected messenger can sit beside it
- Consent, opt-outs and contact cooldowns apply before sending
The morning loop
Return work meets the rest of the day
Rebooking signals enter Today’s Opportunities beside requests, waitlist matches and follow-ups, with the client context ready to open.
- Manual outreach stays available when automation is off
- A confirmed return lands back in the planner
Today’s opportunities
The return signal lands beside the rest of the day.
Mia NakamuraRebookingReview messageMessage sentCamille LaurentRequestSofia BrownWaitlistNoor SinghEmpty slotYour rules
Automation stops where you tell it to
Choose the operating mode, channel choices and daily limits for the workspace, then disable marketing for any individual client when needed.
- Manual, assisted and automatic modes stay owner-controlled
- Client-level marketing choice overrides automated outreach
Outreach controls
Where automatic sending stops, and who is excluded from it.
Automatic sendingEmailSMSDaily limit20Quiet hours21:00–09:00Client kill-switchLena Hoffmann
Lena HoffmannThe radar keeps this client in view; only automated outreach to them stops.
Per client
return cadence from completed visits
3 modes
manual, assisted or automatic
€0
to start, no card required
1 month
free on annual billing
The safeguards around every signal.
Early-history fallback
Use the service interval or workspace default until a personal pattern exists.
Future-booking suppression
A client with a confirmed return stays out of the chase list.
Contact cooldowns
Recent outreach keeps another reminder from arriving too soon.
Consent and opt-outs
Marketing consent is checked before automatic retention outreach.
Language cascade
Prepare the reminder in the language saved on the client record.
Client kill-switch
Turn marketing messages off for one client without stopping the radar.
Daily limits
Owner settings keep automatic sending inside the chosen volume.
Service-level rhythm
Different repeated services keep different return timing.
The Belom platform
Rebooking Radar is just the beginning
Belom keeps the planner, client history and approved communication connected in one place.
Today’s Opportunities
Return signals in the morning queue
Client Memory
Visits, preferences and cadence source
Messages
Review and deliver the personal nudge
Broadcasts
Separate campaign controls
Planner
Future bookings and confirmed returns
Analytics
Retention patterns
What it doesn’t do
No certainty from thin history
Radar does not pretend an early record is a prediction. It uses a service or workspace fallback until enough completed visits establish a personal cadence.
No duplicate chase
A future booking, recent contact or client opt-out removes or suppresses outreach instead of treating every due signal as sendable.
No automatic message by default
Finding a due client and sending a reminder are separate steps. The owner chooses manual, review-first or rule-based delivery.
Built around your results
Review who is due, then choose whether to prepare or send the next reminder.
The radar still works when automatic sending is off; delivery requires a usable allowed rail.
Every returning client, filled slot and hour saved adds to the value of your subscription.