Every call answered.
Every caller remembered.

Company phones, a contact center and an AI receptionist on one platform. Calls reach the right person, and the caller’s history is on their screen before they say hello.

Animated illustration of the Tizbo agent workspace: a support queue, a live call whose transcript appears line by line with context from the caller’s previous calls, and AI notes written during the call.

Start with phones, a contact center or the API.

All three run on the same platform, so adding the next one later needs no migration and no new numbers.

Business phone

One number per person, on every device they use.

One phone system for the whole company, replacing desk-phone hardware and mobile workarounds.

  • Desk phones, desktop, mobile and browser
  • Auto attendant, business hours and holiday schedules
  • Ring groups, hunt groups and call forwarding
  • Voicemail transcribed and sent to email
  • Keep every number you already have
For
Everyone in the company
Numbers
The numbers you already have
Explore business phone

Contact center

Queues that send each caller to the person who can help.

Support and sales lines with routing, live supervision and reporting, on the same numbers as everyone else.

  • Skills, language and priority routing
  • Callbacks instead of long holds
  • Listen, whisper and take over live calls
  • Recording that pauses for card payments
  • Reports by queue, agent and hour
For
Support, sales and service teams
Shares
Numbers with business phone
Explore contact center

Developer API

Place, route and record calls from your own code.

The same platform over a REST API, with a signed webhook for every call event.

  • REST API for calls, numbers and recordings
  • Signed webhooks for each call event
  • Calling from a browser or your own app
  • Sandbox account with test numbers
  • Per-second usage, no minimums
For
Engineering teams
Interfaces
REST · webhooks · in-app calling
Read the API overview

Every channel lands on one customer record.

Calls, texts and browser calls arrive in different ways. Tizbo identifies the customer, routes the contact and writes it to the same history.

Diagram: a customer reaches you by voice, SMS or a browser call. Each passes through Tizbo, which identifies the customer, applies routing and records the interaction, then reaches an agent or the AI receptionist and is written to a ticket or CRM contact.
  1. Tue 10:14Call · 3:05Asked about moving 40 numbers. Ticket #4821 opened.
  2. Tue 10:19SMS sentTicket number and porting checklist sent to Daniel.
  3. Thu 16:02SMS received“Will send the phone bill Friday.” Added to #4821.
  4. Fri 09:42Call · 4:32Recognized on arrival. Cutover booked for Tue 01:00–03:00.
  5. Fri 09:46AI summarySummary and 3 next steps written to #4821.
  6. NextActionSend letter of authorization.

Team leads see every queue as it happens.

Who is waiting, for how long, and which agents are free. A queue that passes its wait target is flagged before callers start hanging up.

Wallboard · Support floorLive 14:32
Waiting
7
across 4 queues
Longest wait
2:51
target 2:00
Agents free
4 / 12
5 on calls
Answered in 30 s
91%
today, sample
Queues right now, with longest wait against a 2:00 target
QueueWaitingLongestAgainst targetFree
Support · EnglishBehind target32:51143%1
Support · Spanish10:4840%1
Billing21:1260%1
Porting10:3529%1
  1. 14:31:55Ivo is free
  2. 14:31:38Dev ended a call · wrap-up
  3. 14:31:20Chloé is free
  4. 14:31:09Support · English passed its 2:00 target
On a call 5
Ana4:32
Ben1:05
Eli7:18
Hana0:51
Jo3:44
Free 4
Chloé0:40
Femi2:10
Ivo0:05
Lea5:30
Wrap-up 2
Dev0:22
Kai1:02
Away 1
Gus12:00

Illustration with sample data.

Listen, whisper, take over
Join any live call from the board
Target alerts
A queue is flagged when its longest wait passes target
Reports
By queue, agent and hour of day

Daniel’s call, second by second.

The AI receptionist answers and works out why someone is calling. Routing picks a person by skill, language and priority. When the call ends, the summary is already on the ticket.

Call log · Halcyon Dentalcall_8f2k1q · 4:32
TimeEventActorResult
00:00.0Incoming callSystem000-000-0134 → main line
00:00.3Customer identifiedSystemDaniel Kim · Halcyon Dental · ticket #4821 open
00:00.9AI answeredAI receptionist“Thanks for calling. Is this about your number transfer?”
00:06.4Intent detectedAI receptionistPorting follow-up · English · returning caller
00:06.6Skill matchedRoutingSupport queue · skill: porting · priority: high
00:11.2Agent answeredAgentTicket, last call and AI notes already open
04:20.5ResolvedAgentCutover booked for Tue 01:00–03:00
04:32.0Summary savedAI notesSummary and 3 next steps on ticket #4821

Every conversation enters through a number, a channel or the API. Tizbo decides where it goes, puts the history in front of whoever answers, and records what happened.

The AI receptionist works inside your call flow.

It answers with your customer data and your rules. When a request is outside those rules, it hands the call to a person along with everything it learned.

AI hands off

Okafor Logistics · customer lineSam Reyes · 000-001-0187
  1. AIThanks for calling Okafor Logistics. How can I help today?
  2. CallerI need to change the delivery date on my order.
  3. AII can help with that. I found order 58213, due Monday. Which day works instead?
  4. CallerTomorrow, if possible.
  5. AITomorrow needs dispatch approval, so I’m putting you through now. They’ll see what we’ve discussed.
Intent
Change delivery date
Customer
Matched by phone number · order 58213
Rule
AI may move a delivery 2+ days out; sooner needs dispatch

Set up the way your callers actually call.

Four common setups. Yours will differ, so the conversation starts from your own call flows.

Patients reach a person, or get a booked callback.

Example routes
  1. Urgent, after 18:00
  2. AI receptionist
  3. On-call line
  1. Routine, after 18:00
  2. AI receptionist
  3. Callback list for 08:00
  • One main number across every location
  • Appointment and prescription calls routed separately
  • Missed calls become a callback list for the front desk

Your admins decide how every call moves.

Numbers, queues, hours, users and routing live in one console. Change a rule and the next call follows it.

Admin · your account

Routing · Main line

Published · edited Fri 08:55 by Jordan Lee
When does the call arrive?
Who is calling?
Is their ticket owner free?

ResultThe call rings the ticket owner, with the ticket and last call already open.

  • StartIncoming call000-000-0100 (on this call's path)
    • CheckBusiness hours?From the Business hours screen (on this call's path)
      • Open
        CheckCaller recognized?Phone number in CRM (on this call's path)
        • Yes
          RouteTicket owner, if freeContext opens with the call (on this call's path)
          • Busy
            QueueSkill queueAfter 2:00: backup team, then callback
        • No
          AIAI receptionistAsks the reason for the call
          • Found
            QueueMatching queueSame overflow rules
      • Closed
        AIAI receptionistAfter-hours greeting
        • Urgent
          RouteOn-call line
        • Other
          EndCallback listCalled back from 09:00

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
  1. Your codePOST /v1/webhooksonce
  2. Daniel callscall.started00:00.0
  3. Agent answerscall.answered00:11.2
  4. Call endscall.ended04:32.0
  5. Your application200 OKsummary stored
1 · Subscribe to call eventsPOST /v1/webhooks
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
2 · What your application receivescall.ended
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.

  1. Customers

    • Callers
    • People who text
    • Web and app users
  2. Access

    • Phone lines
    • Desk phones
    • Browser and app calling
    • SMS
  3. Tizbo

    • Routing
    • Business phone
    • Contact center
    • AI receptionist
    • Messaging
    • Recording and notes
    • REST API and webhooks
  4. Business systems

    SystemInto TizboBack to the system
    CRMContact and account lookupCalls, summaries, next steps
    HelpdeskOpen tickets for the callerTicket updates
    Identity providerUsers and teams via SAML SSO and SCIMAccount changes stay in your provider
    Your applicationREST requestsSigned webhooks for call events

Moving your numbers, week by week.

A typical move for up to a hundred numbers. Larger moves follow the same steps over a longer plan, and no calls are missed during cutover.

  1. Week 1

    Plan

    Done when Routing plan signed off

    Tizbo
    List every number and call flow you have today, then draw up the new routing together.
    Your team
    Send a recent phone bill and sign the porting authorization.
  2. Week 2

    Build and test

    Done when Every route test-called

    Tizbo
    Set up queues, hours and the AI receptionist on temporary numbers you can call.
    Your team
    Install the apps and test-call every route.
  3. Cutover night

    Move the numbers

    Done when All numbers ring on Tizbo

    Tizbo
    Move numbers in a window you choose, usually overnight, and watch every route as calls arrive.
    Your team
    Nothing. Desk phones and apps switch over on their own.
  4. First month

    Tune

    Done when Routing reviewed together

    Tizbo
    Review call data with you and adjust routing, hours and greetings.
    Your team
    Tell us what callers keep asking for.

Security controls.

What your IT team will ask about first.

Payment-safe recording
Recording pauses while a card number is read out, then resumes.
Pause and resume
Company sign-in
Staff sign in through your identity provider; accounts are created and removed from it.
SAML SSO · SCIM
Signed webhooks
Every webhook carries a signature header so your systems can verify it came from Tizbo.
Signed webhooks

Questions teams ask before switching.

Not answered here? Send us the question and we will answer it for your own setup.

Contact us
Can we keep our current phone numbers?

Yes. We move your existing numbers and you choose the cutover window, so no calls are missed.

Do we need new desk phones?

No. Tizbo works with most desk phones you already own, plus the desktop app, the mobile apps and any modern browser.

How does the AI receptionist hand off to people?

It answers, asks why the person is calling and routes them to the right queue. Callers can ask for a person at any time, and the agent sees the AI’s notes before picking up.

Can we start with the phone system and add the contact center later?

Yes. Both run on the same platform, so adding queues and agents later needs no migration.

Is call recording safe for card payments?

Recording pauses automatically while a payment is taken, so card numbers never reach the recording.

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.

  1. Within one business dayWe reply to book a time that suits your team.
  2. On the callThirty minutes on your call flows, with someone who has moved systems like yours.
  3. AfterwardsA written porting plan and pricing for your team size.

Contact us

About a minute
What are you looking for?

We will only use these details to reply to your message.