Connect your software, or use ours

Three modes exist, and each promises something different. One system keeps the record of your calendar, and Zenvox does not build a second one behind your back.

Guide published by Zenvox · Zenvox: the method behind the receptionist

Do you have to change software?

No. If a tool already holds your customers, your work orders or your appointments, your software keeps the record: Zenvox reads there and writes there, action by action, as you authorise from your account.

Three modes exist, and they are named so you know which one applies. In Zenvox: the action happens inside your Zenvox app, which keeps its record. In your software: the action happens inside your software, with its confirmation. Request only: where the vendor does not allow a direct write, the request is captured, documented and handed to your team.

One rule runs through all three: a single reference per object. A calendar, a price list, a file, an order, a payment, a customer-relationship state each have one system that keeps the record, and only one.

Where you probably are

Either you run a management tool and fear a second system will contradict it. Or you run nothing, working from a shared calendar and text messages, and fear having to buy full software before starting.

Both fears are sound, and both have an answer. In one case your software stays the reference. In the other, the Zenvox app is enough to begin: contacts, requests, tasks, availability and simple follow-up.

Three modes, and what each promises

In Zenvox: Zenvox holds the object. The calendar in your Zenvox app handles resources, durations, buffers between visits, service zone and time zone, with a lock preventing two appointments from overlapping. Booked means an appointment truly exists.

In your software: your software holds the object, and Zenvox acts inside it. Booked then requires confirmation from your system rather than from ours. Google Calendar or a Microsoft calendar can hold that role for a simple flow; a practice system holds it whenever it owns appointments.

Request only: where the vendor does not allow a direct write, the request is captured in full, attached to the right file, and handed to your team along with whatever is missing to finish it.

One reference, even when things break

An outage in your software creates no second calendar and no parallel order behind your back. Zenvox keeps the request and shows its real status, including a write that did not reach your software.

After an interrupted write, Zenvox checks your software before retrying, so one appointment is not created twice. Where the check is not conclusive, the request is shown as such rather than guessed.

A read-only calendar shows availability; it gives no permission to write. Permission to read does not become permission to book, to charge or to cancel.

Why some actions stay a request

Every software has its own page, stating action by action what the connection does: read, create, change, cancel. Each write is permitted separately, from your account.

On the trades side: with Jobber, the connection you authorise from your account finds the customer and their past jobs and, with the write permissions you give, creates a new client record. The page for that software sets out the rest action by action rather than showing a logo.

On the health side: Jane rules out AI scheduling tools and direct calendar posting. In a clinic running Jane, the receptionist therefore takes the request and passes it on; your front desk enters the appointment in Jane.

If you run no software

Your Zenvox app covers essentials: contacts, incoming requests, tasks, availability and simple follow-up. Staying there for a long time is a reasonable decision.

Moving to a richer tool should answer an identified need rather than an anxiety. Replacing full accounting, a practice record, an advanced dispatch system or an enterprise CRM is a separate programme, and integration is not a word that covers it.

Either way, one criterion holds: you must be able to configure, test, use, change, stop and export your data without anybody building your flow by hand.

Related pages

Pages detailing what each connection does.

Frequently asked questions

Do we have to change software to get started?

No. Your Zenvox app is made for exactly that: the receptionist keeps requests, customers and appointments in your workspace, with nothing plugged in. You connect later, if and when a connection genuinely adds something. Nobody has to migrate a history in order to receive a call.

Why do some actions stay a plain request?

Because a read permission does not become a booking permission. Every connected software has its own page, stating action by action what the connection does: read a record, create a request, move an appointment, cancel one. Where an action is not permitted, the receptionist notes the request and your team carries it out.

Which software keeps the record, and why choose one?

It is the software that wins when two systems disagree. Without that rule, a cancellation made on one side comes back to life on the other, and nobody knows which version is right. You choose it when connecting, and the rule holds even when the connection drops.

What if our software is not on your list?

Tell us. Your Zenvox app does the job, and your data exports so it can be picked up elsewhere.

Does a connection give access to all of our software?

No. Each authorisation is bounded and you grant it yourself from your account. The receptionist reads what serves the conversation and writes what you authorised. Anything outside that perimeter stays out of reach, and the authorisation is removed in the same place it was granted.

What happens when the connection drops?

Reception carries on. The call is answered, the request is written, and the action that depended on the software is held rather than lost. When the connection returns, the action resumes where it stopped, and an action already performed is not replayed twice.

What if we have no software at all today?

That is a common case and the product is built for it. Requests, customers and appointments live in your workspace, readable by your team. You do not buy a management system in order to answer the phone, and you stay free to take one later.

Can we use both, our software and the Zenvox app?

Yes: the receptionist reads your software to recognise a customer, and writes into your workspace what the connection does not write. The rule of one software keeping the record then stops the two from contradicting each other.

Do we have to import our customer history?

No, and nothing requires it to get started. The receptionist recognises a customer by their number and by what they say; a record is created at the first conversation. If you later connect software holding the history, reading that software enriches what the receptionist knows — without you having had to move anything.

Who decides what a connection is allowed to write?

You do, action by action, when you authorise it. Each software page states what the connection does for all four actions: read, create, modify, cancel. An action the connection does not allow is not offered in your settings.