All Insights
Articles
Handle Inbound Call Centre Calls with AI: Resolve the Routine, Route the Rest
How an AI voice agent answers your inbound queue first: which calls it resolves, how it routes and hands over, the limits, and what a pilot measures.

Last updated 9 October 2026. First published 22 March 2025. Product facts checked against Brilo documentation on 8 October 2026; prices checked against brilo.ai/pricing on 9 October 2026.
An AI inbound call centre puts an AI voice agent first on your inbound queue. It resolves routine calls end to end (answers from your own material, bookings, look-ups), routes the rest by what the caller says, and hands over to a person with a summary. Brilo's paid plans take 15 simultaneous calls (Brilo docs: Limits, read 8 Oct 2026).
Brilo is an AI voice agent that answers and places phone calls. It sits in front of the phone system you already have. It is not a CCaaS suite, a workforce-management tool or a replacement for desk phones. This page covers the main inbound queue during staffed hours: which calls to give the AI, how routing and handover work, where it plugs in, its limits, and how to tell whether it is working.
Who runs an inbound queue, and what each call costs today
Inbound queues are run by support desks, service teams and order lines, and the people answering are mostly customer service representatives. The US Bureau of Labor Statistics counts 2,666,000 customer service representative jobs in 2025, at a median wage of $21.53 an hour ($44,770 a year) in May 2025 (BLS Occupational Outlook Handbook, read 8 Oct 2026). The largest employers are retail trade (15%), insurance carriers (12%) and business support services (8%).
BLS lists the duties as answering questions, giving product information, taking orders, processing billing, reviewing accounts, handling returns and referring customers to supervisors. Much of an inbound queue is that list, repeated all day. BLS projects employment will fall 5% from 2025 to 2035: "there is expected to be less demand for customer service representatives, especially in retail trade, as their tasks continue to be automated."
We have not found a primary-source cost-per-call or abandonment benchmark we would stand behind. Take both figures from your own ACD or phone-system reports before you change anything, because they are the baseline every later comparison depends on.
Which inbound calls an AI agent should take first
Start with the inbound calls that follow a script you could already write down. Brilo's What your agent can do page (read 8 Oct 2026) supports four groups:
Questions from your own material: hours, policies and product details from your uploaded documents, website or FAQs.
Bookings and reschedules: the agent checks Google Calendar, books during the call and confirms by text or email.
Look-ups: order status from Shopify, or a booking or balance from your own system through a custom action, which takes about an hour of developer time.
Messages and callbacks when nobody can take the call now.
Some calls stay with your team. A Brilo agent cannot take a card payment on a call; it sends a payment link by text instead. Disputes and complaints that need judgement also stay human, as does any process you never wrote down. Brilo's documentation is blunt about that last group: if you did not describe it, the agent "will improvise, and improvising is where agents go wrong."
How an AI agent works an inbound queue, in four steps
A Brilo inbound deployment has four parts. For how inbound fits with outbound, analytics and staffing, see the AI call centre guide.
Step 1: Point the line at the agent
Forward your existing number from any provider that supports forwarding (minutes), import a number held at Twilio, Telnyx or Plivo (about 15 minutes, adds texting) (Use your existing number, read 8 Oct 2026), or connect a SIP trunk to your PBX or carrier with Brilo's onboarding team (SIP trunking, read 8 Oct 2026).
Step 2: Write instructions and load knowledge
Upload documents, add your website and FAQs, and write instructions in your callers' words. The agent does not learn on its own.
Step 3: Add actions
Transfer, Google Calendar booking, HubSpot or Salesforce updates, texts and custom look-ups. An action your instructions never mention may never be used.
Step 4: Review calls every week
Read summaries, transcripts and scores. Brilo's documentation says the first week matters more than the first hour.
Replacing the IVR menu with one spoken question
A keypad IVR makes the caller do the routing; an AI voice agent asks what they need and routes on the answer. Brilo documents two set-ups (Route calls to the right team, read 8 Oct 2026):
Several transfers on one agent | A number and agent per department | |
|---|---|---|
Routed by | What the caller says | The number dialled |
Greeting | Same for everybody | Different per department |
Best for | One business, several teams | Separate locations or services |
Cost | One number | One number per department |
Start with the first. Describe each destination in customers' words ("my order hasn't arrived"), not internal team names. Brilo's suggested instruction ends: "If you are not sure which is right, ask one short question to find out. Never guess between two departments." Move to one number per department when you find yourself writing contradictory instructions into one agent. Before go-live, test a deliberately vague request and check that the agent asks rather than guesses. See how Brilo can route calls by what the caller says.
Handing inbound calls to your agents with context
When an inbound call needs a person, the handover is what the caller remembers. Brilo offers three transfer styles (Pass the call to a person, read 8 Oct 2026):
Style | What your colleague hears | Use it when |
|---|---|---|
Cold transfer | Nothing | Speed matters more than context |
Warm transfer with message | A fixed message you wrote | You want a consistent heads-up |
Warm transfer with contextual summary | A summary of this call | Your team needs to know why the caller is ringing |
In a contact centre, a warm transfer with context means your agent picks up already knowing who is calling and why. Give every transfer a fallback number; if neither answers, the AI returns to the caller and follows your instructions, for example scheduling a callback. Transfers can be limited to availability hours. Brilo warns that "a caller who has asked twice for a human and been refused is the worst experience this product can produce," so instruct the agent to transfer on request. One limitation: a colleague cannot silently join a live AI call; transfer is the only route.
Where the AI sits in your existing contact-centre stack
A Brilo AI voice agent goes in front of your contact-centre stack, not in place of it. Brilo's documentation: "It is not a phone system. It answers numbers you point at it. It does not replace desk phones, extensions, or your internal call flow."
Three documented routes connect it: call forwarding from any provider that can forward a number (RingCentral included), number import from Twilio, Telnyx or Plivo, and a SIP trunk to your PBX or carrier. Over SIP, Brilo's help centre says the agent answers and "either resolves the call or routes it back to your contact-center/PBX or a human agent." For data it connects to HubSpot, Salesforce, Shopify and Google Calendar, and to anything else through custom actions or webhooks (Supported integrations, read 8 Oct 2026).
Brilo's integrations documentation lists no named connector for Genesys, Five9, NICE, Avaya or Cisco. If your ACD is one of these, the documented routes are SIP or forwarding; confirm details with Brilo before planning around them. More on how the AI reaches your phone line.
Hear an AI agent answer your own inbound line. Book a 15-minute call and we will show a Brilo agent answering, routing and warm-transferring on your call flow. See AI inbound calling
Worked example: what an inbound pilot should measure
Brilo has not yet published a named inbound customer result, so this page does not quote one. Instead, here is what a pilot on your own inbound line should measure, so the before-and-after is your evidence rather than a vendor's.
Record each figure from your phone system or ACD before the pilot and from the Brilo call record during it:
Volume and intent mix: monthly inbound calls and the share of your top five intents (Brilo AI call tags give the "during" side).
Calls ending without a transfer, read against each call's Resolution score.
Transfer outcomes: connected, rang out, voicemail or declined, which Brilo's call record tells apart.
Minutes per call: Brilo rounds each call up to the next minute, and calls of 10 seconds or less count as zero. The median tells you which plan fits.
Pulse Score distribution and safety flags for hallucination, compliance or off-script behaviour.
Answer and abandonment rates against your pre-pilot baseline.
Starting with call forwarding keeps the pilot reversible "in a minute," per Brilo's documentation.
Before and after: the inbound queue with an AI answering first
This table compares a typical inbound queue behind a keypad IVR with the same queue when a Brilo AI voice agent answers first. The right-hand column comes from Brilo's documentation (read 8 Oct 2026); the left describes the common set-up, not measured results.
Before: IVR plus staffed queue | After: Brilo AI voice agent answers first | |
|---|---|---|
First response | Menu, then a wait for a free agent | Agent answers and asks what the caller needs |
Routing basis | Keypad choice | What the caller says, with one clarifying question |
Routine questions | Take agent time | Answered from your documents, website and FAQs |
Bookings | Agent books by hand | Booked in Google Calendar during the call |
Handoff context | Agent starts cold | Warm transfer with a contextual summary |
Simultaneous calls | One per staffed agent | 15 on paid self-serve plans |
Call record | Whatever your ACD logs | Summary, transcript, tags, extracted details, Pulse Score |
Card payments | Taken by an agent | Not taken by the AI; payment link by text, or transfer |
Card payments and undocumented processes stay with your human team in both columns, so your staffing plan still needs to cover them.
How to tell whether the inbound AI is working
Brilo scores every eligible call automatically with Pulse Score, a 1–5 rating that appears about a minute after the call ends (Pulse Score, read 8 Oct 2026). It combines Resolution (did the caller get what they called for?), Clarity (were answers accurate?), Effort (how hard did the caller work?) and Sentiment. Pulse also flags Hallucination, Compliance Concern and Off-Script Behavior.
Read transfers carefully. Under Brilo's scoring, a smooth transfer the AI starts because the call needs a human counts as a good resolution; a caller demanding a human because the AI kept failing counts as poor. So the transfer rate alone tells you little; the reason for each transfer tells you a lot.
A practical weekly routine: sort the call log by lowest Pulse Score, listen to the bottom ten calls, and fix the instruction or knowledge gap behind each. Use AI call tags to watch the intent mix. Set targets against your own pre-launch baseline, not a published benchmark. Our guide to scoring every call covers QA in depth.
Limits to plan around before you switch the queue over
These are Brilo's documented limits as of 8 Oct 2026 (Limits, Plans, Supported languages):
Calls at the same time: 2 on Free; 15 on paid self-serve plans; agreed on Custom. The limit is per workspace, not per number or per agent, and it is shared between inbound calls and outbound campaigns, so a campaign running at full concurrency takes capacity from inbound callers (How many calls at once and Control how fast a campaign dials, read 8 Oct 2026). A caller who arrives at the limit "does not reach your agent." More than 15 needs a Custom plan.
Minutes: when the monthly allowance runs out, the agent stops taking calls unless extra usage is on. Extra usage is off by default.
Languages: 21, one per agent; no mid-call switching except the Multilingual option for workspaces in India.
Learning: the agent does not change its own instructions.
Data controls: recording and retention are set per agent; HIPAA support and recording consent controls are Custom-only.
What you need to get started with inbound AI
Have these ready before an inbound pilot:
A line to point at the agent: a number your provider can forward, a number held at Twilio, Telnyx or Plivo, or SIP access to your PBX or carrier.
Your top inbound intents by volume from your ACD or call logs, with the answer or process written down for each.
Transfer destinations, one per team, each with a fallback number and availability hours.
Systems the agent must read from: Shopify, HubSpot and Salesforce connect directly; anything else needs a custom action.
An owner for weekly call review, plus pre-pilot baseline figures: volume, intent mix, answer rate and abandonment rate.
A plan: Brilo's pricing page lists Free (10 minutes a month), Pro at $149 a month (600 minutes, 16 cents per extra minute), Growth at $499 a month (2,500 minutes, 14 cents per extra minute) and Custom for more than 5,000 minutes, priced on request. Annual billing saves 10% (brilo.ai/pricing, read 9 Oct 2026).
For the finance case, see AI call centre costs and ROI.
Related inbound jobs: after-hours, overflow, peaks and outbound
This page covers AI answering first on the staffed inbound queue. Neighbouring jobs have their own pages:
After-hours: covering the line while you are closed uses different instructions and transfer hours. See after-hours call cover.
Overflow: AI picking up only the calls your agents cannot reach is the reverse of AI-first. See overflow call handling.
Seasonal peaks: whether 15 simultaneous calls covers your busiest hour is capacity planning, covered in sizing for seasonal peaks.
Outbound: reminders, follow-ups and campaigns run on the same Brilo agent on a paid plan; Brilo's documentation says outbound calling is not available on Free (Plans, read 9 Oct 2026). See outbound AI calling.
Customer service beyond the phone: see AI in customer service.
Use cases by department: a catalogue of AI call centre use cases is a separate topic, not covered here.
Inbound AI call centre FAQ
Can one AI platform handle both inbound and outbound calls?
Yes. A Brilo agent answers incoming calls on any plan and makes outgoing calls on paid plans (not on Free), singly or as a campaign. Inbound and outbound share the same simultaneous-call pool, so do not schedule a campaign into your busiest inbound hour. Outbound planning, including consent rules, is a separate job with its own Brilo page.
Can an AI agent handle high-volume inbound calls?
Brilo's paid self-serve plans take 15 calls at the same time across the whole workspace, shared with any outbound campaigns; Custom plans agree a higher figure. A caller arriving at the limit does not reach the agent, and capacity frees up as each call ends. Plan for peak, not average: Brilo's documentation notes that forty calls in two minutes "is a different problem" from forty spread over an hour.
Do we need to replace our phone system or contact-centre platform?
No. Brilo answers numbers you point at it, by forwarding, import from Twilio, Telnyx or Plivo, or a SIP trunk. Desk phones, extensions and internal call flow stay as they are. Brilo publishes no named connectors for Genesys, Five9, NICE, Avaya or Cisco, so confirm the SIP or forwarding design for those platforms with Brilo first.
What happens when a transfer is not answered?
The agent tries your fallback number. If that also fails, it returns to the caller and follows your instructions, such as scheduling a callback or taking a message. The call record shows whether the transfer rang out, went to voicemail or was declined.
Does a transferred call count twice towards minutes?
No. Brilo's documentation says the minutes your agent was on the call count once. Each call is rounded up to the next whole minute, and calls of 10 seconds or less count as zero.
Put an AI voice agent first on your inbound queue. See how a Brilo agent answers, resolves routine calls and hands the rest to your team with a summary, then book a 15-minute call to try it on your own line. Explore AI inbound calling
Twilio, Telnyx, Plivo, RingCentral, HubSpot, Salesforce, Shopify, Google Calendar, Genesys, Five9, NICE, Avaya and Cisco are trademarks of their respective owners. They are named only to identify compatibility or the absence of a documented connector; no affiliation or endorsement is implied.
All Insights
Articles
Handle Inbound Call Centre Calls with AI: Resolve the Routine, Route the Rest
How an AI voice agent answers your inbound queue first: which calls it resolves, how it routes and hands over, the limits, and what a pilot measures.

Last updated 9 October 2026. First published 22 March 2025. Product facts checked against Brilo documentation on 8 October 2026; prices checked against brilo.ai/pricing on 9 October 2026.
An AI inbound call centre puts an AI voice agent first on your inbound queue. It resolves routine calls end to end (answers from your own material, bookings, look-ups), routes the rest by what the caller says, and hands over to a person with a summary. Brilo's paid plans take 15 simultaneous calls (Brilo docs: Limits, read 8 Oct 2026).
Brilo is an AI voice agent that answers and places phone calls. It sits in front of the phone system you already have. It is not a CCaaS suite, a workforce-management tool or a replacement for desk phones. This page covers the main inbound queue during staffed hours: which calls to give the AI, how routing and handover work, where it plugs in, its limits, and how to tell whether it is working.
Who runs an inbound queue, and what each call costs today
Inbound queues are run by support desks, service teams and order lines, and the people answering are mostly customer service representatives. The US Bureau of Labor Statistics counts 2,666,000 customer service representative jobs in 2025, at a median wage of $21.53 an hour ($44,770 a year) in May 2025 (BLS Occupational Outlook Handbook, read 8 Oct 2026). The largest employers are retail trade (15%), insurance carriers (12%) and business support services (8%).
BLS lists the duties as answering questions, giving product information, taking orders, processing billing, reviewing accounts, handling returns and referring customers to supervisors. Much of an inbound queue is that list, repeated all day. BLS projects employment will fall 5% from 2025 to 2035: "there is expected to be less demand for customer service representatives, especially in retail trade, as their tasks continue to be automated."
We have not found a primary-source cost-per-call or abandonment benchmark we would stand behind. Take both figures from your own ACD or phone-system reports before you change anything, because they are the baseline every later comparison depends on.
Which inbound calls an AI agent should take first
Start with the inbound calls that follow a script you could already write down. Brilo's What your agent can do page (read 8 Oct 2026) supports four groups:
Questions from your own material: hours, policies and product details from your uploaded documents, website or FAQs.
Bookings and reschedules: the agent checks Google Calendar, books during the call and confirms by text or email.
Look-ups: order status from Shopify, or a booking or balance from your own system through a custom action, which takes about an hour of developer time.
Messages and callbacks when nobody can take the call now.
Some calls stay with your team. A Brilo agent cannot take a card payment on a call; it sends a payment link by text instead. Disputes and complaints that need judgement also stay human, as does any process you never wrote down. Brilo's documentation is blunt about that last group: if you did not describe it, the agent "will improvise, and improvising is where agents go wrong."
How an AI agent works an inbound queue, in four steps
A Brilo inbound deployment has four parts. For how inbound fits with outbound, analytics and staffing, see the AI call centre guide.
Step 1: Point the line at the agent
Forward your existing number from any provider that supports forwarding (minutes), import a number held at Twilio, Telnyx or Plivo (about 15 minutes, adds texting) (Use your existing number, read 8 Oct 2026), or connect a SIP trunk to your PBX or carrier with Brilo's onboarding team (SIP trunking, read 8 Oct 2026).
Step 2: Write instructions and load knowledge
Upload documents, add your website and FAQs, and write instructions in your callers' words. The agent does not learn on its own.
Step 3: Add actions
Transfer, Google Calendar booking, HubSpot or Salesforce updates, texts and custom look-ups. An action your instructions never mention may never be used.
Step 4: Review calls every week
Read summaries, transcripts and scores. Brilo's documentation says the first week matters more than the first hour.
Replacing the IVR menu with one spoken question
A keypad IVR makes the caller do the routing; an AI voice agent asks what they need and routes on the answer. Brilo documents two set-ups (Route calls to the right team, read 8 Oct 2026):
Several transfers on one agent | A number and agent per department | |
|---|---|---|
Routed by | What the caller says | The number dialled |
Greeting | Same for everybody | Different per department |
Best for | One business, several teams | Separate locations or services |
Cost | One number | One number per department |
Start with the first. Describe each destination in customers' words ("my order hasn't arrived"), not internal team names. Brilo's suggested instruction ends: "If you are not sure which is right, ask one short question to find out. Never guess between two departments." Move to one number per department when you find yourself writing contradictory instructions into one agent. Before go-live, test a deliberately vague request and check that the agent asks rather than guesses. See how Brilo can route calls by what the caller says.
Handing inbound calls to your agents with context
When an inbound call needs a person, the handover is what the caller remembers. Brilo offers three transfer styles (Pass the call to a person, read 8 Oct 2026):
Style | What your colleague hears | Use it when |
|---|---|---|
Cold transfer | Nothing | Speed matters more than context |
Warm transfer with message | A fixed message you wrote | You want a consistent heads-up |
Warm transfer with contextual summary | A summary of this call | Your team needs to know why the caller is ringing |
In a contact centre, a warm transfer with context means your agent picks up already knowing who is calling and why. Give every transfer a fallback number; if neither answers, the AI returns to the caller and follows your instructions, for example scheduling a callback. Transfers can be limited to availability hours. Brilo warns that "a caller who has asked twice for a human and been refused is the worst experience this product can produce," so instruct the agent to transfer on request. One limitation: a colleague cannot silently join a live AI call; transfer is the only route.
Where the AI sits in your existing contact-centre stack
A Brilo AI voice agent goes in front of your contact-centre stack, not in place of it. Brilo's documentation: "It is not a phone system. It answers numbers you point at it. It does not replace desk phones, extensions, or your internal call flow."
Three documented routes connect it: call forwarding from any provider that can forward a number (RingCentral included), number import from Twilio, Telnyx or Plivo, and a SIP trunk to your PBX or carrier. Over SIP, Brilo's help centre says the agent answers and "either resolves the call or routes it back to your contact-center/PBX or a human agent." For data it connects to HubSpot, Salesforce, Shopify and Google Calendar, and to anything else through custom actions or webhooks (Supported integrations, read 8 Oct 2026).
Brilo's integrations documentation lists no named connector for Genesys, Five9, NICE, Avaya or Cisco. If your ACD is one of these, the documented routes are SIP or forwarding; confirm details with Brilo before planning around them. More on how the AI reaches your phone line.
Hear an AI agent answer your own inbound line. Book a 15-minute call and we will show a Brilo agent answering, routing and warm-transferring on your call flow. See AI inbound calling
Worked example: what an inbound pilot should measure
Brilo has not yet published a named inbound customer result, so this page does not quote one. Instead, here is what a pilot on your own inbound line should measure, so the before-and-after is your evidence rather than a vendor's.
Record each figure from your phone system or ACD before the pilot and from the Brilo call record during it:
Volume and intent mix: monthly inbound calls and the share of your top five intents (Brilo AI call tags give the "during" side).
Calls ending without a transfer, read against each call's Resolution score.
Transfer outcomes: connected, rang out, voicemail or declined, which Brilo's call record tells apart.
Minutes per call: Brilo rounds each call up to the next minute, and calls of 10 seconds or less count as zero. The median tells you which plan fits.
Pulse Score distribution and safety flags for hallucination, compliance or off-script behaviour.
Answer and abandonment rates against your pre-pilot baseline.
Starting with call forwarding keeps the pilot reversible "in a minute," per Brilo's documentation.
Before and after: the inbound queue with an AI answering first
This table compares a typical inbound queue behind a keypad IVR with the same queue when a Brilo AI voice agent answers first. The right-hand column comes from Brilo's documentation (read 8 Oct 2026); the left describes the common set-up, not measured results.
Before: IVR plus staffed queue | After: Brilo AI voice agent answers first | |
|---|---|---|
First response | Menu, then a wait for a free agent | Agent answers and asks what the caller needs |
Routing basis | Keypad choice | What the caller says, with one clarifying question |
Routine questions | Take agent time | Answered from your documents, website and FAQs |
Bookings | Agent books by hand | Booked in Google Calendar during the call |
Handoff context | Agent starts cold | Warm transfer with a contextual summary |
Simultaneous calls | One per staffed agent | 15 on paid self-serve plans |
Call record | Whatever your ACD logs | Summary, transcript, tags, extracted details, Pulse Score |
Card payments | Taken by an agent | Not taken by the AI; payment link by text, or transfer |
Card payments and undocumented processes stay with your human team in both columns, so your staffing plan still needs to cover them.
How to tell whether the inbound AI is working
Brilo scores every eligible call automatically with Pulse Score, a 1–5 rating that appears about a minute after the call ends (Pulse Score, read 8 Oct 2026). It combines Resolution (did the caller get what they called for?), Clarity (were answers accurate?), Effort (how hard did the caller work?) and Sentiment. Pulse also flags Hallucination, Compliance Concern and Off-Script Behavior.
Read transfers carefully. Under Brilo's scoring, a smooth transfer the AI starts because the call needs a human counts as a good resolution; a caller demanding a human because the AI kept failing counts as poor. So the transfer rate alone tells you little; the reason for each transfer tells you a lot.
A practical weekly routine: sort the call log by lowest Pulse Score, listen to the bottom ten calls, and fix the instruction or knowledge gap behind each. Use AI call tags to watch the intent mix. Set targets against your own pre-launch baseline, not a published benchmark. Our guide to scoring every call covers QA in depth.
Limits to plan around before you switch the queue over
These are Brilo's documented limits as of 8 Oct 2026 (Limits, Plans, Supported languages):
Calls at the same time: 2 on Free; 15 on paid self-serve plans; agreed on Custom. The limit is per workspace, not per number or per agent, and it is shared between inbound calls and outbound campaigns, so a campaign running at full concurrency takes capacity from inbound callers (How many calls at once and Control how fast a campaign dials, read 8 Oct 2026). A caller who arrives at the limit "does not reach your agent." More than 15 needs a Custom plan.
Minutes: when the monthly allowance runs out, the agent stops taking calls unless extra usage is on. Extra usage is off by default.
Languages: 21, one per agent; no mid-call switching except the Multilingual option for workspaces in India.
Learning: the agent does not change its own instructions.
Data controls: recording and retention are set per agent; HIPAA support and recording consent controls are Custom-only.
What you need to get started with inbound AI
Have these ready before an inbound pilot:
A line to point at the agent: a number your provider can forward, a number held at Twilio, Telnyx or Plivo, or SIP access to your PBX or carrier.
Your top inbound intents by volume from your ACD or call logs, with the answer or process written down for each.
Transfer destinations, one per team, each with a fallback number and availability hours.
Systems the agent must read from: Shopify, HubSpot and Salesforce connect directly; anything else needs a custom action.
An owner for weekly call review, plus pre-pilot baseline figures: volume, intent mix, answer rate and abandonment rate.
A plan: Brilo's pricing page lists Free (10 minutes a month), Pro at $149 a month (600 minutes, 16 cents per extra minute), Growth at $499 a month (2,500 minutes, 14 cents per extra minute) and Custom for more than 5,000 minutes, priced on request. Annual billing saves 10% (brilo.ai/pricing, read 9 Oct 2026).
For the finance case, see AI call centre costs and ROI.
Related inbound jobs: after-hours, overflow, peaks and outbound
This page covers AI answering first on the staffed inbound queue. Neighbouring jobs have their own pages:
After-hours: covering the line while you are closed uses different instructions and transfer hours. See after-hours call cover.
Overflow: AI picking up only the calls your agents cannot reach is the reverse of AI-first. See overflow call handling.
Seasonal peaks: whether 15 simultaneous calls covers your busiest hour is capacity planning, covered in sizing for seasonal peaks.
Outbound: reminders, follow-ups and campaigns run on the same Brilo agent on a paid plan; Brilo's documentation says outbound calling is not available on Free (Plans, read 9 Oct 2026). See outbound AI calling.
Customer service beyond the phone: see AI in customer service.
Use cases by department: a catalogue of AI call centre use cases is a separate topic, not covered here.
Inbound AI call centre FAQ
Can one AI platform handle both inbound and outbound calls?
Yes. A Brilo agent answers incoming calls on any plan and makes outgoing calls on paid plans (not on Free), singly or as a campaign. Inbound and outbound share the same simultaneous-call pool, so do not schedule a campaign into your busiest inbound hour. Outbound planning, including consent rules, is a separate job with its own Brilo page.
Can an AI agent handle high-volume inbound calls?
Brilo's paid self-serve plans take 15 calls at the same time across the whole workspace, shared with any outbound campaigns; Custom plans agree a higher figure. A caller arriving at the limit does not reach the agent, and capacity frees up as each call ends. Plan for peak, not average: Brilo's documentation notes that forty calls in two minutes "is a different problem" from forty spread over an hour.
Do we need to replace our phone system or contact-centre platform?
No. Brilo answers numbers you point at it, by forwarding, import from Twilio, Telnyx or Plivo, or a SIP trunk. Desk phones, extensions and internal call flow stay as they are. Brilo publishes no named connectors for Genesys, Five9, NICE, Avaya or Cisco, so confirm the SIP or forwarding design for those platforms with Brilo first.
What happens when a transfer is not answered?
The agent tries your fallback number. If that also fails, it returns to the caller and follows your instructions, such as scheduling a callback or taking a message. The call record shows whether the transfer rang out, went to voicemail or was declined.
Does a transferred call count twice towards minutes?
No. Brilo's documentation says the minutes your agent was on the call count once. Each call is rounded up to the next whole minute, and calls of 10 seconds or less count as zero.
Put an AI voice agent first on your inbound queue. See how a Brilo agent answers, resolves routine calls and hands the rest to your team with a summary, then book a 15-minute call to try it on your own line. Explore AI inbound calling
Twilio, Telnyx, Plivo, RingCentral, HubSpot, Salesforce, Shopify, Google Calendar, Genesys, Five9, NICE, Avaya and Cisco are trademarks of their respective owners. They are named only to identify compatibility or the absence of a documented connector; no affiliation or endorsement is implied.
Latest Insights
All Resources
Articles
Case Studies
Tutorials

Articles
8 Best AI Voice Agents for Salesforce in 2026, Compared Field by Field
Best AI voice agent for Salesforce in 2026? We compare 8 tools on caller lookup, Task write-back, custom fields, Flow triggers and editions, with Brilo's gaps included.

Articles
How to Connect an AI Voice Agent to Salesforce: External Client App, Run As User and a Test Call in 10 Minutes
Connect an AI voice agent to Salesforce with an External Client App, a least-privilege Run As user and a scripted test call. No developer needed, about ten minutes.
Load More
Latest Insights
All Resources
Articles
Case Studies
Tutorials

Articles
8 Best AI Voice Agents for Salesforce in 2026, Compared Field by Field
Best AI voice agent for Salesforce in 2026? We compare 8 tools on caller lookup, Task write-back, custom fields, Flow triggers and editions, with Brilo's gaps included.

Articles
How to Connect an AI Voice Agent to Salesforce: External Client App, Run As User and a Test Call in 10 Minutes
Connect an AI voice agent to Salesforce with an External Client App, a least-privilege Run As user and a scripted test call. No developer needed, about ten minutes.
Load More
Automate your business with AI phone Agents
Automate your business with AI phone Agents
Automate your business with AI phone Agents
Automate your business with AI phone Agents
Call automation for healthcare, real estate, logistics, financial services & small businesses.
Call automation for healthcare, real estate, logistics, financial services & small businesses.
Join Discord
Connect with our community, ask questions, and stay updated on product news.
Book a Call
Schedule a quick call with our team to explore solutions for your needs.
Get started
Industries
Usecases
Integrations
Legal & Community

Join Discord
Connect with our community, ask questions, and stay updated on product news.
Book a Call
Schedule a quick call with our team to explore solutions for your needs.
Get started
Industries
Usecases
Integrations
Legal & Community

Join Discord
Connect with our community, ask questions, and stay updated on product news.
Book a Call
Schedule a quick call with our team to explore solutions for your needs.
Get started
Industries
Usecases
Integrations
Legal & Community

Join Discord
Connect with our community, ask questions, and stay updated on product news.
Book a Call
Schedule a quick call with our team to explore solutions for your needs.
Get started
Industries
Usecases
Integrations
Legal & Community

