A business is decided between the visits.

A calendar can be full while the business quietly shrinks. Someone who came every five weeks comes at seven, then at eleven, then stops. Nobody cancels. Nothing looks broken. The month simply earns less than the last one, and no report explains why.

Booking software treats the appointment as the finish line. What follows - remembering the formula, answering the message that landed in a different app, noticing that a good client is four weeks overdue - falls to a person who is also doing the work with their hands. That labour is invisible, it never fits inside the day, and it is precisely the labour that compounds.

We wanted to know how much of it the industry actually handles, so we read the public documentation of eight booking products on one narrow question: what happens when a client simply does not arrive. We found eight different answers. In some it is a status of its own. In one it is a tick box inside cancelling. In another it is a colour the calendar turns on its own. In a fourth it is a label the reports never read. One of the eight publishes a formula for the rate. One removes no-shows from its performance reports rather than counting them.

So we built the half that was missing. One record per client holds the visits, preferences, conversations and return rhythm, and booking, messages and rebooking all read from it. When Belom says someone is due back, it names the interval it measured from that person’s own history and links the visits behind the number.

The decision stays with the person doing the work. The assistant drafts and you approve; automations run only inside rules you switch on, with consent and quiet hours enforced on every channel. We also stay out of the money: deposits run through the professional’s own Montonio account, and Belom takes 0% of what a client pays. Solo specialists, shared front desks and multi-location teams all use it - the same problem wearing three different shapes.