Integration overview

An integration wires two systems together. Yours holds your organisation and your customers; Voicebot runs the conversations.

The work runs as three phases, in order. Each ends on a condition the next one depends on: Voicebot cannot bind a scenario to an account that does not exist yet.

Different people perform each phase, and scheduling them usually takes longer than the work itself.

	Phase	Performed by	Ends when
1	Onboarding	us, with your telecom team	a test call connects and your tenant key works
2	API integration	your engineers, with us for the validation	the step 7 checklist passes against a real account
3	Configuration	you, through the API or the Account Panel	a test dispatch reaches a real handset

The route

This page numbers the eight steps, and every other page refers to them by that number. Each phase page carries the exit criterion for its own steps.

1. Deployment. We issue cloud tenants on an installation that already runs. On-premise, the installation comes first. Phase 1. Cloud: us. On-premise: you, inside your perimeter, with our team.

2. Voice layer. A trunk between Voicebot and your telephony. Phase 1, us with your telecom team. Longest lead time of anything here, so start it first.

3. Tenant provisioning. Your tenant, its administrator, and the tenant API key you receive. Phase 1, us.

4. Authentication. Your integration service obtains a token to call with. Phase 2, your engineers.

5. Structure mirrored. Accounts, users, numbers and pools created from your system. Phase 2, your engineers.

6. Users signed in. Magic link or provisioned credentials. Phase 2, your engineers.

7. Validation. Both sides work through an explicit checklist. Phase 2, jointly. This is the gate into phase 3.

8. Automation configured. Scenarios, agents, schedules. Phase 3, you, through the API or the Account Panel.

Consumption sits outside the phases and has its own page. You can read outcomes, history and recordings from the first completed call onward, for the life of the integration.

A registered number is not a voice path

Step 2 brings up the voice path; step 5 registers numbers as records. With numbers and no trunk, Voicebot accepts every dispatch and nothing rings. See why a trunk is not a number.

What each phase touches

Phase	Surface	Key
1 — Onboarding	Tenant API	tenant key, held by us then by you
2 — API integration	Tenant API + Account API	tenant key for structure, account keys for work
3 — Configuration	Account API or Account Panel	account key

Where to start

Without a tenant, start at phase 1. If you already hold a tenant key, go straight to phase 2 — or run the first call walkthrough to confirm the plumbing works before you build anything.