A long call
A twelve-minute conversation ending in an appointment counts as one call, exactly like a two-minute one.
What gets counted
One call is one answered conversation, whatever its length. Here is the rest, counted with the same plain honesty.
7 days, 20 answered calls, no card
What this page settles
The question an owner asks ahead of every other is simple: what gets counted, and from which point does it cost more. A vague answer there is reason enough to walk away, and a fair one.
A call, at Zenvox, is an answered conversation. Length changes nothing: two minutes or twelve minutes, it is one call. Every base includes fifty Standard calls a month and one local number, across all eight industries, and setting up costs nothing.
The rest is counted separately, and that separation is deliberate. What a receptionist answers to you does not consume the same reserve as what it answers to customers. Service messages do not blend into written conversations. Capacity bought for a task does not unlock that task: it only adds volume to whatever you already hold.
How a month is counted
- During the month
Each conversation sits in its own reserve
An answered call counts as a call. A written conversation with a customer counts in the customer reply reserve. A question you put to your receptionist counts in yours.
- At any moment
Current usage is available on request
Usage can be read in your workspace, and it can also be asked for in writing. The answer comes from the real meters on an account.
- After an incident
A technical retry does not count twice
Where a delivery or a job is retried after an incident, it is the same work: it gets reconciled and counted once. Content and version are deduplicated.
- At the next period
What resets, and what stays active
Monthly meters restart at each billing period. Active capacities — a website, a connected store, a connection — do not reset: they describe what exists at the same time.
What is settled, and included in your base
Those decisions are made and they hold across all eight industries.
- Fifty Standard calls included each month
- One local number included
- A call is an answered conversation, whatever its length
- No setup fee, no activation fee
- Service messages — summary, confirmation, reminder, text after a missed call — sit in the base
Reserves are separate, on purpose
Blending them would make an invoice unreadable and let one kind of use eat another.
- What a receptionist answers to you has a reserve of its own
- What it answers to customers has another, shared across written channels you buy
- Message segments and service email are counted apart
- Voice calls stay metered on a base, independently of written channels
- How many team accounts and bookable resources a base covers is set by an offer
Counting rules, stated once
They come from catalogue rules, and nearly all of them work in your favour.
- A transfer extends the current conversation: it creates no second call
- An automation counts one run per trigger and per version, whatever its steps
- A delivery to an application counts per confirmed destination, rather than per attempt
- Asking a receptionist to draft a text adds no second charge for returning that action
- Audio inside a presentation session is included in that session
What is not settled, and therefore not shown
Three mechanisms exist in catalogue research, and none of them is decided.
- Whatever happens beyond the calls included: the rule is unsettled, so no price is published
- Extra volume formats — calls, messages, email, seats, numbers — carry no price here
- The price of optional tasks, which is under study
While a rule is unsettled, the only honest move is to say what is included and to promise nothing beyond it.
What that means in practice
Four everyday situations, read with the rules above.
A transferred call
A conversation continuing with somebody on your team stays the same conversation. It counts once.
A customer writing after calling
The call counts on a base. What follows in writing counts in the customer reply reserve of whichever channel was bought.
A delivery retried after an incident
The same message replayed after a technical failure does not count twice: usage is reconciled ahead of billing.
Questions
What happens once the included calls are used?
The rule is unsettled by a founder, and no price is published while it stays that way. It is a pending decision, written here as one rather than filled with a provisional figure.
Does a cold call count?
Calls filtered as abusive cold calling do not consume a reception allowance. Protection against flooding belongs to the base.
Can usage be seen ahead of an invoice?
Yes. It can be read in a workspace at any time, and asked for in writing from the receptionist.
Does buying volume unlock a function?
No, and that is a catalogue rule: capacity adds units to a task already held, without granting any new right.
Where to next
Voices and what they consume, or tasks carrying meters of their own.
What gets counted