Phase 1 — Infrastructure and connection

We drive this phase and run it with you. Our telecom engineers coordinate the connection with your side, and we create your tenant and hand you the key that opens it; under the on-premises option you run the installation itself, in step 2.

What follows is here so you can plan it and staff it: what we need from you, what we do, where the calendar goes, and what you hold when it is done.

The connection and the tenant run on separate clocks

The connection carries by far the longest lead time. The tenant is usually issued early, because it is what a demonstration runs on. Neither waits for the other.

Step 1 — Review the requirements

Two questions get settled before anything is built: what the installation needs from your environment, and what we need from your side to carry calls. Your engineers and ours work through both together.

This is the first conversation that is not a commercial one. It is where an on-premises deployment gets sized, and where a cloud deployment establishes what has to reach what.

Done when neither side has an open question that would change the shape agreed during alignment.

Step 2 — Install Voicebot

On our cloud, nothing happens here: your tenant is issued on an installation that already runs.

On-premises, this is the installation itself. You agree sizing, network topology and the installation procedure with our team, and run it inside your perimeter. Those are settled directly rather than documented here, because they follow your environment.

Done when the installation that hosts your tenant is running. No API call observes this, so the same conversation that agreed it confirms it.

Both options converge here

Phases 2 and 3 are identical under either deployment option. Only who runs the installation changes.

Step 3 — Set up the SIP trunk

Once step 2 settles the installation parameters, a SIP trunk links Apifonica and your telecom infrastructure.

On our cloud, that trunk runs between the two of us. On-premises, it stays inside your own deployment, and it still needs provisioning: Voicebot’s SIP side reaches only what a trunk names.

Done when a call connects over the trunk.

Step 4 — Set up the tenant

We create your tenant with a single tenant_admin user and issue that user’s first API key.

Your integration starts from that key. It opens the Tenant API, and identity and access covers where it belongs.

Done when the key authenticates.

What phase 1 leaves you with

The connection is proven when a call connects in each direction you agreed. The tenant is usable as soon as the key opens it.

Phase 2 begins on the key alone. The connection is what check 6 of the validation list needs, which is why it starts first and runs alongside.