The estimate is the bottleneck
Where visits happen fast and pricing waits until evening, the useful task is whichever prepares the file and follows the estimate sent.
What gets added to your base, what each addition genuinely brings, and what is not settled yet — said as it stands.
7 days, 20 answered calls, no card
Your base handles reception: answering, qualifying, passing on requests, texting callers who could not get through and arranging appointments under the applicable rules. Each industry defines useful information and resources: unit and mandate, vehicle and shop, patient and practitioner, student and available place. A booking depends on your industry’s rules and access to the relevant calendar.
An optional task is another thing: extra work a receptionist takes on, carrying its own rights, its own meters and its own reason to exist. Preparing an estimate, collecting a deposit, dispatching field work across crews, keeping a public listing current: each has a page, and each can be removed without touching the others.
Nothing is switched on by default. That is a design rule rather than a courtesy: an add-on silently preselected is a price nobody chose. And while a founder has not settled the price of a task, that price is not shown — it is under study, and this page says so instead of floating a figure that would move.
Part of what people assume they must add is already included: answering around the clock, qualifying, booking, alerting on your rule, writing after a missed call. Starting there avoids buying the same thing twice.
Every task is described by what it does for you and by the decision it leaves you. Where its page says nothing to you, it is of no use to you — and that is a valid answer.
A task carries meters of its own, apart from base calls. Fees from an outside provider — message transport, a payment provider, a registrar, an advertising budget — stay billed by them.
Removing a task leaves the base and other tasks intact. That is what makes trying an add-on reversible, rather than a commitment in disguise.
Those decisions are made, and they appear on the pricing page.
Those values exist in catalogue research under a proposed status. Publishing them would announce a price nobody decided.
While those decisions are pending, the purchase path does not offer them: a simulation authorises no purchase and no commitment.
The catalogue carries non-overlap rules, and they work in your favour: they prevent selling you the same right twice.
Four situations drawn from catalogue industries. They are reasons to add, rather than sales recommendations.
Where visits happen fast and pricing waits until evening, the useful task is whichever prepares the file and follows the estimate sent.
Where part of the demand comes from a platform or a partner, the useful task is whichever deduplicates, assigns an owner and matches outcome to source.
Where an empty slot cannot be resold, the useful task is a deposit asked for during the conversation, with the cancellation rule stated then.
Where several crews or locations share the work, the useful task is whichever assigns it and shows where requests pile up.
Because it is not settled. The eight base prices are decisions taken; task prices are design proposals. Showing a proposal as a price would be a promise nothing backs.
Yes. Removal leaves the base and other tasks intact, and task data stays exportable under the rules of an account.
No. Answering, qualifying, booking, alerting and handing over are included in all eight bases. A task adds extra work; it does not unlock reception.
Yes, and that is a settled decision: no base carries a setup fee or an activation fee. Whatever a third party still bills — a carrier, a payment provider, a registrar — is named on the page of the task concerned.
See what is metered, or choose by need rather than by name.
Optional tasks