My software is not in the list

Your tool has no page here: the result is written into Zenvox, with every feature. What it takes to connect it, and what runs with nothing connected.

7 days, 20 answered calls, no card

Where your result lands

The result is written into Zenvox: the request, the appointment, the reason for calling, the recording and the transcript. The full service runs with nothing connected at all. Your software keeps the truth of what it already holds, and the receptionist hands you the work where you are.

What an owner is not asked for comes down to three things: no key to create, no connector to program, no development written to order. When your software publishes an interface, the connection runs under an authorisation you give and your own rules, limited to what you allow.

One rule guides what follows: a general category is not enough to connect anything — you need a named product, its edition, and the person who holds the account. And a portal that opens in a browser is not an interface: a screen built for a human being is not a permission.

Read, create, update, cancel

For software that has no page of its own, here is what the connection does, action by action: what it reads and writes in your tool, and what Zenvox takes care of — because that is the real question an owner asks when they do not see their tool in the list.

ActionWhat that means
ReadZenvox reads your software through its published interface, with the authorisation of the person who holds the account and the access your edition gives. Three answers open the reading: the product, its edition, and the account holder.
CreateZenvox writes into your software the objects its interface lets it create, after reading and in that order. Every request carries an identifier, so a repeated send does not create the same object twice, and a refusal from your software is flagged to you.
UpdateUpdating lives in your workspace: the request changes state there, with its history, and you carry it across to wherever you work. That also avoids the worst case, which is two tools editing the same file without knowing about each other.
CancelCancelling touches states that your software controls, and sometimes that carries billing consequences. Zenvox records the cancellation request, flags it and passes it to you. Driving a portal built for a human being automatically is not the default behaviour: an approved import or a human step takes its place.

What is included, what needs an add-on

Your whole base works without connecting anything at all: answering, qualifying, taking the appointment, sending the summary, routing it to the right person. No capability in the base depends on third-party software, and that is deliberate. What does need an add-on is assembling your own rules and wiring up your own applications.

Add-ons that work with your software

Custom automations

Triggers, conditions, delays, approvals, versions, tests and a stop, and your own applications linked under an authorisation you give — under the same action rules as everywhere else, with a readable diagnostic when something jams.

Centralised sign-in for my organisation

For an organisation that manages access from its own identity provider: a guided setup, your directory groups matched one by one, an access removed on your side removed in Zenvox too, and a standard audit export.

The authorisation, and what holds the truth

Here is what you are asked for to connect your software, and the limits that are set in advance.

  • Name the product, its edition and the person who holds the account: a general category cannot be connected
  • A portal that opens in a browser does not count as an interface: it takes a published interface and an authorisation that can actually be granted
  • When no interface exists, or your vendor does not open it, an import you approve or a human step replaces the automation, and that remains a good outcome
  • Your workspace holds the truth for the request and its history; your software keeps its grip on whatever it already runs
  • Buying an interface does not open access to everything: the rights stay the ones you grant

A business whose order tracking lives in an in-house system with no published interface. Nothing is connected: the receptionist works in Zenvox and routes the request.

CustomerHi, I am calling to find out where my order stands.

ReceptionistLet me take your name and a callback number first, in case we get cut off. Do you have an order number or a date?

CustomerI ordered about three weeks ago, I do not have the number.

ReceptionistNo problem, I am writing down what you have given me and passing it right away to the person who has the file in front of her. I will not commit to a date myself — she is the one who will confirm it.

The request reaches the right person with the name, the callback number, the order period and the exact question. The in-house system is not touched; the person who opens it answers with the real status, and the customer gets a call back instead of a wait.

If no connection is possible

That is an ordinary situation, and it stops nothing: the full service runs in your Zenvox workspace.

  • The requests, the appointments and the messages live in your workspace, with their history and their register
  • You see them in the app on your phone, and you answer from there
  • An export lets you carry the data into your own software at your own pace
  • Connecting your software later changes neither your setup nor your habits

Questions about this connection

My tool is not on the list — can I still start?

Yes. The full service runs with nothing connected: the request, the appointment, the reason for calling, the recording and the transcript live in your workspace.

What does it take to connect my software?

A named product, its edition, and the person who holds the account: a general category cannot be connected. With those three answers, the connection runs through your tool's published interface, under an authorisation you give.

My software has a web portal — does that count?

No, a portal that opens in a browser is not an interface. A screen built for a human being is not a permission, and automating a portal is not the default behaviour.

What if my vendor says no?

An import you approve or a human step then replaces the automation, and that remains a good outcome: the request, the appointment and the follow-up live in your workspace.

Do I have to program anything?

No: no key to create, no connector to program, no development written to order. When your software publishes an interface, the connection runs under an authorisation you give, limited to what you allow.

Does buying an interface open access to everything?

No: the rights stay the ones you grant, action by action.

Where to next

See the software that has its own page, how your own data feeds the receptionist, or your own workflows.

My software is not in the list

Your tool has no page here: the result is written into Zenvox, with every feature. What it takes to connect it, and what runs with nothing connected.

Start your free trial7 days, 20 answered calls, no card