Inbound calls
Decide what happens when a number rings — the agent answers, the call rings through, is rejected, forwarded, or handed to your own system.
Every number has an inbound behaviour: what happens the moment a call arrives.
| Behaviour | What happens |
|---|---|
| Answer | The agent assigned to the number answers |
| Let ring | The call rings without Kilevel answering it |
| Deny | The call is rejected |
| Forward | The call is forwarded to a phone number you enter |
| External | The call is handed to an external system at a webhook URL you provide |
Answer is the default, and the one you want for an AI receptionist.
Answering with an agent
The number's agent answers with its flow. Everything the flow needs about the caller — their number, and anything your telephony attached to the call — is available from the first turn, so the agent can look the caller up before it says hello.
To put a person first and the AI second, set the agent to ring a human and fall back to the AI — see Flows and agents.
Capacity
Inbound calls count against the number's concurrency and your workspace's lines. Keep inbound numbers separate from the ones your campaigns call from, so a busy campaign never blocks your main line. See Phone numbers.
Knowing a call happened
Add a session webhook with OnSessionBegin to hear
about inbound calls as they start, or OnAIAnalysisReady to receive the outcome once the
call is over.