Okafor Logistics
Engineering team
Dispatch software needs to know when a driver call starts, ends and what was agreed.
Set upA webhook for the call events, with the summary and next steps stored against the job.
Developer API
Place, route and record calls from your own code.
The same network over a REST API, with a signed webhook for every call event.
- For
- Engineering teams
- Interfaces
- REST · webhooks · in-app calling
- Billing
- Per second, no minimums
What’s included.
Interfaces
- REST APICalls, numbers and recordings are available over REST.
- Signed webhooksEvery call event, such as started, answered and ended, is sent to your endpoint with a signature you can verify.
- In-app callingYour own site or app can offer calling from a browser or a mobile device.
Building and paying
- Sandbox accountA sandbox account comes with test numbers.
- Per-second usageUsage is billed per second with no minimums.
- Same network as the phonesCalls placed through the API run on the same network and numbers as the other products.
Connecting your systems
- Business systemsCRM and helpdesk lookups come in, and calls, summaries and ticket updates go back.
- Call summaries in eventsThe webhook for a finished call can carry the summary and next steps.
- Identity providerUsers and teams come in through SAML SSO and SCIM, and account changes stay in your provider.
Subscribe once. Every call reports back.
The same platform your team uses, over a REST API. Connect calls to your CRM, your helpdesk or your own product.
Talk to an engineer- Your codePOST /v1/webhooksonce
- Daniel callscall.started00:00.0
- Agent answerscall.answered00:11.2
- Call endscall.ended04:32.0
- Your application200 OKsummary stored
curl https://api.tizbo.example/v1/webhooks \
-H "Authorization: Bearer $TIZBO_KEY" \
-d url=https://example.com/hooks/tizbo \
-d events=call.started,call.answered,call.ended- Signed webhooks you can verify
- Test numbers in a sandbox account
- Per-second usage with no minimums
POST https://example.com/hooks/tizbo
Tizbo-Signature: t=1791288000,v1=5c1e…
{
"type": "call.ended",
"call_id": "cal_8f2k1q",
"duration_sec": 272,
"summary": "Porting all 40 numbers. Cutover overnight.",
"next_steps": ["Send letter of authorization"]
}How it fits together.
Customers reach you through phone lines, desk phones, browsers and SMS. One platform handles them and keeps your business systems in step.
Customers
- Callers
- People who text
- Web and app users
Access
- Phone lines
- Desk phones
- Browser and app calling
- SMS
Tizbo
- Routing
- Business phone
- Contact center
- AI receptionist
- Messaging
- Recording and notes
- REST API and webhooks
Business systems
System Into Tizbo Back to the system CRM Contact and account lookup Calls, summaries, next steps Helpdesk Open tickets for the caller Ticket updates Identity provider Users and teams via SAML SSO and SCIM Account changes stay in your provider Your application REST requests Signed webhooks for call events
How it works.
Subscribe to events
Your code posts to the webhooks endpoint with the call events it wants.
A call starts or is placed
Calls arrive on your numbers or are placed over REST, and your app can offer calling from a browser or a mobile device.
Events arrive signed
Tizbo sends call.started, call.answered and call.ended to your endpoint.
Your code verifies them
The Tizbo-Signature header lets you check each request before you act on it.
You write to your system
The summary and next steps from a finished call are stored in your application.
Who uses it.
Examples with fictional companies, set up the way a real team might.
Lumen Retail
Web team
Shoppers should be able to call from the site without dialing a number.
Set upA browser call from the site that the AI receptionist answers and that creates a new CRM contact.
Halcyon Dental
Operations engineer
Call history should sit on the helpdesk ticket without anyone copying it over.
Set upTicket lookups on the way in, and calls, summaries and ticket updates sent back.
Getting started.
You can build before any real number moves.
- Day one
Sandbox
Use the sandbox account and its test numbers to place calls and subscribe a webhook endpoint.
- Build
Verify and store
Check the signature on each webhook and store the call summary in your application.
- Move numbers
Port when ready
Numbers move in a window you choose, usually overnight, and calls keep arriving on the same routes.
- First month
Tune
We review call data with you and adjust routing, hours and greetings.
Also on the same network.
Every product shares the same numbers, routing and customer record, so adding one needs no migration.
Business phone
Desk, mobile and browser calling on one number
View business phoneContact center
Queues, live supervision and reporting
View contact centerAI receptionist
Answers, routes and hands off with notes
View ai receptionistQuestions teams ask before switching.
Not answered here? Send us the question and we will answer it for your own setup.
Contact usHow do we verify a webhook?
Each webhook carries a Tizbo-Signature header, so your code can check the request came from Tizbo before acting on it.
Can we build before moving any numbers?
Yes. The sandbox account has test numbers, so you can build against the API before anything is ported.
Talk to the team that will set it up.
You have seen the workspace, the wallboard and the plan. Bring your current call flows and we will walk through them using your own numbers.
- Within one business dayWe reply to book a time that suits your team.
- On the callThirty minutes on your call flows, with someone who has moved systems like yours.
- AfterwardsA written porting plan and pricing for your team size.