Kilevel
Dashboard

Language / Sprache

KILEVEL © 2026

Overflow and contact centres

A second line for the calls your team cannot take

Keep your team as the first answer and let an AI agent take the calls that would otherwise wait, drop or go to voicemail, and pass back what needs a person.

This page inEnglishDeutschTürkçe

The problem

Call volume does not arrive evenly. Peaks, campaigns and seasons leave callers waiting, and some of them hang up. Staffing for the peak leaves people idle the rest of the time.

Many calls are routine: a status, a booking, an opening time. Those are the calls that keep a queue long while harder cases wait.

Who it is for

  • Contact centres: Absorbing peaks and handling routine calls so agents can work the harder ones.

  • Support teams: Keeping a line open outside working hours.

  • Sales and booking desks: Taking enquiries when everyone is on another call.

  • Seasonal businesses: Covering peaks without staffing for them all year.

What it handles

  • Human first, AI second

    An inbound agent can ring a person first and let the AI take over as a fallback.

  • After-hours cover

    The AI answers while nobody is on shift, and your team reads the records in the morning.

  • Routine calls

    Status questions, bookings and information, handled with your knowledge base and tools.

  • Warm hand-offs

    The person picking up hears a generated summary before the caller is connected.

  • Supervision

    Listen to calls live, follow captions, have the agent say something, or take the call in the browser softphone.

How it works

  1. Decide what overflows

    After a number of rings, outside hours, or specific call types.

  2. Build the second line

    A flow for the calls it should finish, and transfers for the ones it should not.

  3. Route the calls

    Inside Kilevel, use a human-first agent. With an existing phone system, send overflow calls to a Kilevel number or over a SIP trunk.

  4. Set the hand-off

    Choose blind or warm transfers, and where calls go if nobody answers.

  5. Watch and adjust

    Review what the AI finished, what it passed on and why.

What you need

  • A phone system that can forward or transfer calls, or numbers in Kilevel
  • The rule for when a call overflows
  • The call types the AI may finish, and the ones it must pass on
  • Knowledge and any tools those calls need
  • Numbers or extensions for hand-offs

What it connects to

  • Phone systems: SIP trunks to your carrier or PBX, plus Twilio and Telnyx. Custom SIP headers can be carried through a transfer.

  • Your team: Human agents in Kilevel, working from the browser softphone.

  • Your systems: Custom HTTP tools, webhooks and the API.

What to expect

  • Fewer calls wait or end unanswered during peaks.
  • Routine calls are finished without taking your team away from harder ones.
  • The person who picks up already knows what the call is about.
  • You can see what was handled, what was passed on and why.

Limits

  • Capacity is finite. Numbers and workspaces have concurrency limits, and those need sizing for your peak.
  • If you keep your phone system, the overflow rule lives there, and it has to be able to pass calls on.
  • A warm transfer needs someone to answer. If it fails, the assistant tells the caller and carries on, so decide what it should offer instead.
  • Some calls should reach a person directly. Decide which, and do not route them to the AI.

How to evaluate it

  • Start after hours: It is the lowest-risk slot: those calls had no answer before.

  • Then one call type: Pick a routine type and let the AI finish it.

  • Measure your own numbers: Compare abandoned calls and hand-off rates before and after, in your own phone system and in Kilevel's analytics.

  • Check hand-offs: Ask your team whether the summaries actually help.

Questions

Do we have to replace our phone system?

No. Calls can reach Kilevel over a SIP trunk or a forwarded number, and your phone system keeps deciding what overflows.

Can a person take over during a call?

Yes. Your team can take calls in the browser softphone, and the agent can transfer to a number or a SIP address at any point the flow allows.

What does the person picking up hear?

With a warm transfer they hear a generated summary or a message you define. The caller does not hear it and is connected once it is done.

What if the transfer fails?

The assistant tells the caller and carries on rather than leaving them on a dead line.

Does this work for outbound calls too?

This page is about inbound overflow. Keep inbound numbers separate from campaign numbers, so that a busy campaign never blocks your main line.

See it on your own calls

Start with a test number and a small set of real questions. Nothing has to change on your main line until you decide it should.