Documents and deadlines
The document list follows the engagement, chasing stops on receipt, and both owner and deadline stay visible. The classic I already sent it gets settled with a record, not a memory.
Karbon
Karbon holds your work items and their owners. A status request is written into Zenvox and routed to the right owner; your ledgers stay out of reach.
7 days, 20 answered calls, no card
Where a status request lands
The request is written into Zenvox: entity, fiscal year concerned, what the call is about, the deadline stated, the owner it is meant for. Karbon keeps the truth of your work items and their statuses. A general ledger is not practice management software: Zenvox stays out of your entries, and closing a work item stays with the firm.
Access uses two-header authentication, with account-level scope. That is exactly what calls for discipline: account scope sees broadly, so internal role filtering gets decided before install, not after. Documented throughput is one hundred and twenty requests per minute, and retry behaviour after refusal remains to be proven.
Karbon holds clients, work items, owners and statuses for bookkeepers and firms tracking dozens of entities; Zenvox answers status requests during peak season, instead of creating one more email.
Read, create, update, cancel
The status below comes from vendor documentation and from what has not been proven: account permissions, rate refusals and the client-request lifecycle.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Client search is documented. That is the foundation of any useful answer to a status request: find the entity, then the work in progress and its owner, without guessing. |
| Create | To qualify | Creating a work item with owner and status is described. Client requests and their attachments need a separate verification: that is a different object, and assuming it would be a mistake. |
| Update | To qualify | Updating a work item is described. The account-level permission boundary and behaviour on rate refusal remain to be tested: without that, a bad retry can duplicate a work item in the middle of tax season. |
| Cancel | Zenvox native mode | Closing a period, withdrawing a work item or cancelling a filing are professional decisions. The receptionist records, tells the owner, and lets the firm settle it. |
What is included, what needs an add-on
Answering, identifying entity and fiscal year, capturing a tax authority letter with its agency and deadline, routing to the right owner and handing you everything belong to your professional services base. Periodic document collection per entity is a named add-on, and it is the one that fixes the real problem of the trade.
The authorisation, and what holds the truth
Account-level scope is powerful and broad. The points below exist so it stays narrow in practice.
- Access rests on firm-side technical authentication; Zenvox asks for no password and for no banking access
- Internal role filtering is decided before install: who sees which entities, and who does not
- Karbon stays the system of record for work: a request captured on the phone is a request, not an approved work item
- The accountant approves treatment and entries; the receptionist files nothing on her own authority
- You withdraw access whenever you want; service carries on in Zenvox native mode
Early March, peak season. The team is producing, the phone rings without stopping. The call is taken by Zenvox; nothing is written into the software.
ClientHi, I got a letter from the provincial tax authority and there is a deadline on it. What do I do?
ReceptionistLet me take your name, a callback number, and the business it concerns. Which agency sent the letter, and what deadline does it state?
ReceptionistI am noting that date and flagging this as priority for the person who owns your file. They will call you back; I cannot read the letter for them.
The firm receives a priority request with the entity, the agency, the deadline and the time of the call. Nobody interrupted production, and the letter did not sit in a voicemail box while the clock ran.
When the connection is not there
The firm keeps its software as the single truth, and the receptionist works in Zenvox native mode.
- The request is created inside Zenvox with entity, period and stated deadline
- Tax authority letters are flagged priority and routed to the owner
- You find the call, its transcript and its reason in the app
- No banking password is ever requested from a client, under any circumstance
- The day an operation becomes qualified, it is added without redoing your setup
Questions about this connection
Does Zenvox touch my ledger entries?
No. A general ledger is not practice management software: Zenvox stays out of your entries, and closing a work item stays with the firm.
Account-level scope is broad — how is it narrowed?
Internal role filtering is decided before install — who sees which entities, and who does not. Access rests on firm-side technical authentication, and Zenvox asks for no password and for no banking access.
Can a call create a duplicate work item during peak season?
That is the risk qualification has to remove. The account-level permission boundary and behaviour on rate refusal remain to be tested, and a bad retry can duplicate a work item; documented throughput is one hundred and twenty requests per minute.
What does she do with a tax authority letter?
She captures the entity, the agency and the deadline, flags the request priority and routes it to the right owner. Nobody interrupts production, and the letter does not sit in a voicemail box while the clock runs.
Is a banking password ever requested from a client?
No banking password is requested from a client, under any circumstance. The accountant approves treatment and entries; the receptionist files nothing on her own authority.
Where to next
See the practice concerned, or the full list of software studied.
Karbon