One connected operating system
Follow the client from first interest to the next visit.
Broadcasts & Automations
two controlled ways to send.
For a deliberate campaign, NAI can draft wording that the professional reviews and approves. Separately, an owner can enable rule-based reminders or rebooking messages that send by themselves within consent, cooldown and daily-contact limits.
Get started, it is free
No card requiredFree plan included
Approved NAI drafts and owner-enabled automatic rules
- SMS
- Telegram
- Messenger
Campaign scale without the cold-list feeling.
Without Broadcasts & Automations
- A mailing list drifts away from the client record.
- Every audience is rebuilt in a spreadsheet.
- Reminders depend on someone remembering to send them.
- Language, consent and channel rules are checked by hand.
With Broadcasts & Automations
- Campaign recipients come from owner-scoped client data.
- Groups, tags, status and recorded fields shape the audience.
- Booking and rebooking rules prepare repeatable outreach.
- Delivery checks consent, reachability, quotas and language.
In practice
Mode 1 · NAI drafts, the professional approves
A professional selects an eligible audience, asks NAI for a first message, edits the wording and approves the campaign before delivery starts.
Mode 2 · A configured rule sends
For a repeatable event such as a timed reminder or due rebooking client, an owner-enabled rule can send without a fresh approval for every message.
Built-in sending limits stay active
Consent, opt-outs, reachability, contact cooldowns, plan quotas and the configured daily client cap are checked before automatic outreach.
The outcome stays visible
Queued, sent, skipped and failed results remain in the delivery history instead of disappearing into a background job.
The client record powers every send.
Campaigns handle a deliberate audience. Automations handle a repeatable event. Both keep the relationship in the decision.
Campaign composer
Start with a draft, then approve the real send
Choose email or SMS, narrow the owner’s client directory, use NAI for a first draft when useful and preview eligible and excluded recipients before approval.
- NAI draft
- Audience preview
- Professional approval
Client data
Audience rules stay attached to real records
Build from all clients, saved groups or exact selections, then narrow by status, tags and the presence of fields such as visit history or contact details.
- Groups
- Tags
- Visit history
Repeatable timing
Automations act on the event, not a calendar note
Booking confirmations, cancellations, timed reminders and rebooking outreach use stored rules, client reachability and the owner’s enabled channels.
- Booking events
- Reminders
- Rebooking
Controlled delivery
Consent, language and quota stay in the path
Broadcasts enforce marketing consent and opt-outs. Automated delivery follows enabled channels and uses the client’s saved language before the workspace default.
- Consent
- Language
- Quota
From memory to message
One campaign or rule, with the relationship intact.
Compose
Choose email or SMS, then preview before sending
Start from the client directory, select the campaign channel, write the message and see how many matched clients are eligible before delivery begins.
- Exact recipients and exclusions stay visible before send
- Personal fields resolve from each selected client record
Select
Groups, tags, status and fields replace the cold list
Use all clients, saved groups or a specific selection, then add filters from owner-scoped Client Memory without exporting a second database.
- Filter on status, tags, contact fields and visit history
- Marketing consent and channel opt-outs remain enforced
The audience is records, not a list
Built in place, so it is never out of date.
Camille LaurentGel services
Mia NakamuraGel servicesDDaniel BrooksGel servicesNothing was exported to build this segmentThat is why a consent flag set five minutes ago is still respected.
Return
Measured return timing becomes outreach
When Rebooking Radar marks a client due, overdue or at risk, the enabled rule can prepare outreach while contact cooldowns, consent and reachability stay in force.
- The signal comes from the client’s own visit history
- Deduplication and daily limits protect repeated contact
Measured return timing becomes outreach
The signal comes from the client’s own rhythm.
Amara OkaforRuleRebooking outreach · needs approvalChannelEmail · her saved language
Draft prepared — waiting for your approvalContact cooldown: not messaged in the last 14 daysThe cooldown is what stops two automations contacting the same person in one week.
Reach
Use the reachable channel in the client’s language
Email remains the required base for core booking automations, while enabled SMS and connected Telegram, Instagram, Messenger or WhatsApp routes can join the rule when the client is reachable.
- Client channel preference orders the available delivery routes
- Saved client language falls back to the workspace default
Transparent capacity
Campaign broadcasts use the allowance already in the plan
Every tier includes a monthly email quota that can be used for campaigns. One-off email and SMS packs add capacity without changing the audience workflow.
- Email top-up €2.90 per 1,000
- SMS packs from €5.99 per 100 segments
70
emails per month on Free · campaigns included
500
emails per month on Pro · campaigns included
5,000
emails per month on Studio 15 · campaigns included
€2.90
email top-up per 1,000 · one-off
The controls that keep scale personal.
Marketing consent
Only clients opted into marketing enter a broadcast audience.
Channel opt-outs
Email and SMS preferences are checked again at delivery.
Eligible preview
See matched, eligible and excluded recipients before sending.
Exact selections
Choose named clients when the campaign should stay focused.
Templates hub
Keep wording by event, channel and supported language.
Quiet controls
Timing rules, daily limits and cooldowns govern automation.
Delivery log
Sent, queued, skipped and failed outcomes remain visible.
One-off capacity
Top up email or SMS without replacing the core plan.
The Belom platform
Broadcasts & Automations is just the beginning
Belom keeps the planner, client history and approved communication connected in one place.
Client Memory
Groups, tags, consent and language
Rebooking Radar
Due, overdue and at-risk timing
Messages
Connected routes and delivery history
Templates hub
Wording by event, channel and language
Analytics
Campaign and delivery outcomes
What it doesn’t do
No cold-list permission
Belom does not turn an imported address into marketing consent; eligibility and opt-outs still decide who can receive a broadcast.
No unlimited automation
Built-in sending limits, cooldowns, quotas and daily client caps protect the relationship even after an owner enables a rule.
No delivery guarantee
A queued message can still be skipped or fail when a channel, entitlement, address or provider is unavailable.
Built around your results
Approve one client campaign-or enable one carefully bounded rule.
NAI-assisted campaigns wait for approval. Automatic rules run only after an owner enables them and remain inside sending protections.
Every returning client, filled slot and hour saved adds to the value of your subscription.