One connected operating system
Follow the client from first interest to the next visit.
Client Memory
the context the next visit needs.
Visits, preferences, formulas, notes, conversations and return timing kept on one client record, visible to the people who should see it and nobody else.
Get started, it is free
No card requiredFree plan included
The record that makes the next visit easier
- Visits
- Preferences
- Service details
- Notes
- Threads
- Cadence
A relationship, not a row in a calendar.
Without Client Memory
- Preferences live in a notebook or a memory.
- A new team member starts from zero.
- The same question is asked every visit.
- Nobody knows when the client is due back.
With Client Memory
- Every visit adds to one record.
- A new hire reads what they are allowed to read.
- Preferences and service details arrive with the booking.
- Return timing comes from the client’s own rhythm.
In practice
Before the visit
The professional opens the appointment and sees permitted visit history, preferences, notes and contact details on the linked client record.
During the visit
They update the details that matter next time-such as equipment, sensitivities, timing preferences or a private note-without creating a second record.
After the visit
The completed visit joins the history and can inform the client’s return cadence for Rebooking Radar.
Availability
Client records are part of the core workspace. Team visibility follows role, assignment and field-level permissions.
What the record keeps.
Enough context to run the visit well, without collecting things that age badly.
History
Every visit, in order
Services, prices, duration and who performed the work, so the pattern is visible without a spreadsheet.
- Visits
- Services
- Specialist
Detail
Preferences and service details
The specifics that make a repeat visit easier to run: equipment, sensitivities, preparation and timing preferences.
- Equipment
- Sensitivities
- Timing
Cadence
A client-specific return rhythm
Return timing is measured per client, so a six-week regular and a twice-a-year visitor are never treated the same.
- Cadence
- Drift
- Signals
One rhythm per client
A five-week regular and a twice-a-year visitor are never treated the same.
Mia Nakamura34d36d33d≈ 35 daysDue in 3 days
Marco Rossi172d181d168d≈ 174 daysDue in 6 weeksA single reminder interval would chase one of them too often and lose the other entirely.
Boundaries
Visible to the right people
Roles decide who reads notes, money and contact details. Private notes stay with the specialist who wrote them.
- Roles
- Private notes
- GDPR tools
On the record
One client, one page.
History
Visits
Every completed visit with service, price and specialist, newest first.
- Linked to the planner entry
- Exportable per client
Detail
Preferences
Structured fields for the things you must not guess twice.
- Custom fields per service type
- Shown at booking time
Conversations
Threads
The conversation history that belongs to this relationship, across channels.
- Permission-aware access
- Consent state per channel
Return
Cadence
The rhythm Belom measured, and the drift that makes a reminder worth sending.
- Source facts attached
- Feeds rebooking opportunities
Control
Data
A client can ask for their data or ask to be forgotten. Both are one action.
- CSV export per client
- Full deletion across records
One record
per client relationship
Role-based
visibility of notes and money
€0
to start, no card required
GDPR
export and erase built in
The safeguards that keep client context useful.
Private notes
Stay with the specialist who wrote them.
Permissions
Scope client detail per role and per location.
Decisions log
Every change to a record is attributable.
Merge duplicates
Two records for one person become one history.
Assisted migration
CSV export is self-service; confirm any inbound client-list migration with Belom before switching.
GDPR export and erase
Answer a data request without a support ticket.
The Belom platform
Client Memory is just the beginning
Belom keeps the planner, client history and approved communication connected in one place.
Planner
Visits and appointments
Messages
Threads per client
Rebooking Radar
Cadence signals
Today’s Opportunities
Daily queue
Analytics
Retention patterns
CSV export
Clients and subject-access bundles
Booking page
Fields collected once
Team roles
Visibility scope
Data boundaries
What is stored
The record can hold visit history, preferences, notes, contact details and the communication or cadence context linked to that client.
Who can see it
The professional and permitted team members can see owner-scoped client data. Another business cannot browse or inherit this client base.
Export and delete on request
A permitted professional can export the client bundle and permanently erase the client's data when responding to a client request.
What it doesn’t do
Belom does not share the client base with other businesses, and it does not message clients on its own without an approval or configured rule.
Built around your results
Create the client record now, then carry its context into the next visit.
Client records are available in the core workspace; team access remains permission-controlled.
Every returning client, filled slot and hour saved adds to the value of your subscription.