Bring your own business number

The number customers already dial is one of your most valuable assets. It's on your storefront, your invoices, your Google listing, your years of business cards. So the right question when adding a phone agent isn't "what new number do I get?" — it's "how do I put an agent on the number people already call?" This guide covers bringing your own business number to Agent Vani: why it matters, how connecting a line works at the level you actually need to understand, and how to go live without a single dropped or mishandled call.

We'll stay at the outcomes level — what you control and what to watch for — not the plumbing. What matters to you is that your identity stays yours, your routing stays under your control, and the switch to live is careful and reversible.

Why your existing number matters

It's tempting to think a phone agent means a fresh number, but that throws away the thing that makes the phone valuable: recognition and reach.

• It's already everywhere. Directories, listings, printed materials, customer contacts. A new number means updating all of it and losing the calls that keep coming to the old one.
• It carries trust. Callers recognize a local or familiar number. An unfamiliar one gets ignored or treated as spam.
• It's continuity. Customers who've called you for years shouldn't have to learn a new number because you changed how the line is answered. The change should be invisible to them — they dial the same number, and now it's answered better.

The goal of bringing your own number is exactly that invisibility: nothing changes for the caller except that the line is now reliably, competently answered.

What "connecting a number" means for you

You don't need to become a telecom engineer. At the level that matters to you, connecting a business number to Agent Vani means: the line that used to ring your desk (or a voicemail, or an IVR) now routes to your organisation's Agent Vani, so the right workspace answers. You attach the numbers customers dial, and those lines point to your agent.

The practical implications you do need to hold onto:

• Your org owns the association. The numbers you attach route to your workspace's agent, configured with your persona, knowledge, hours, and escalation — not a generic shared bot.
• You choose which numbers. You might connect one line, or several, and decide which ones the agent owns. A number you don't attach isn't touched.
• Routing stays yours. When and how the agent answers, and when it hands off to a person, is your configuration — covered in how to set business hours and escalation.

The specifics of how a given line gets connected depend on how that number is currently set up, and the console walks you through attaching it. What you should focus on is the configuration and the go-live, which is where the caller experience is won or lost.

Connect your phone account

You keep using the phone provider you already have. In the TaskNinja workspace, open Integrations and connect the account that holds your business numbers — today that means Exotel, Plivo, or Twilio. After the account is linked, attach the numbers callers already dial to your Calling agent.

If you want a live handoff to a teammate when the agent cannot finish the call, turn on Transfer to human under the agent’s Tools settings and set the human number. The Integrations screens include short how-to steps for each provider; Exotel needs one extra step in its call flow for transfer, which the Exotel connect screen explains.

Then follow the going-live checklist: configure fully, test on the attached number, and only then let production traffic through.

Keep your identity intact

Bringing your own number is what lets the agent sound like your business, not a generic service. The caller dials your familiar number and reaches an agent configured with your persona, your voice, your approved facts, and your handoff rules. Combined with the persona work in how to write a phone agent script, the effect is that callers experience a better version of calling you — same number, same brand, better answered — rather than a jarring handoff to something that feels external.

Why the two-way feel still matters here

Connecting your number is table stakes; what happens once the call connects is what callers judge. Putting a turn-based, robotic agent on your trusted number is worse than not answering, because now your recognizable line is the one that frustrates people. The whole point of routing your number to an agent is that the agent holds a real, interruptible conversation — so the caller's experience of your familiar number gets better, not worse. That two-way, realtime quality is the reason any of this is worth doing; the background is in two-way realtime vs turn-based AI calls.

Going live carefully — the part that matters most

This is where teams either succeed quietly or fail loudly, because it's your real customers on your real number. The rule is simple: test thoroughly before production traffic, and keep the change reversible.

A careful path:

1. Configure fully first. Persona, voice, knowledge, hours, and escalation rules all set before any live traffic. A live number in front of a half-configured agent is how you get bad calls at scale. See how to write a phone agent script.
2. Test on the attached number. Dial it yourself and run real scenarios — interrupt it, ask off-script questions, request a human, try after-hours behavior. You're testing on the actual line, the way a customer will hit it.
3. Try to break it. Test the two-way feel and interrupt recovery deliberately (see the buying guide tests). Better you find the rough edges than a customer.
4. Go live deliberately. When you're satisfied, let production calls flow — knowing you can adjust or pull back if something's off.
5. Watch the first real calls. Review completed calls closely in the early days — who called, how long, how it ended — and tune quickly. The first days of live traffic teach you more than any amount of testing.

The full sequence is in the going-live checklist. The point of bringing your own number carefully is that the switch is invisible to callers and reversible for you.

Common concerns, answered honestly

"Will I lose calls during the switch?" The point of a careful go-live is that you don't. Configure and test first, switch deliberately, and watch the early calls. Because it's your existing number, callers keep dialing exactly as before.

"Can I put the agent on just one line to start?" Yes — you choose which numbers to attach. Many teams start with one line, prove it out, and expand.

"What if I want to pull it back?" Keep the change reversible. If something's off, you adjust the configuration or routing rather than being stuck.

"Do callers need to do anything different?" No. That's the whole point. Same number, better answered.

What you control

Bringing your own number doesn't hand control to us — it keeps it with you. You decide which numbers the agent answers, how it sounds, what it knows, when it's on, and when it hands off. You review completed calls and tune over time. The number stays yours; the configuration stays yours; the caller experience stays yours to shape.

One honest note on scope: Agent Vani answers inbound calls at launch — the calls coming to your connected numbers. Outbound dialing from your number uses the same agent in a later release. So bringing your own number today is about answering your inbound lines beautifully.

One number or several — how to think about it

Businesses rarely have just one phone number, and deciding which lines the agent should own is a real decision, not a technicality. A few patterns work well:

• The main line first. The number on your listings and storefront is where the volume is. Putting the agent there first delivers the most value and gives you the clearest signal on how it performs.
• A department line as a pilot. If you're cautious, connect a lower-stakes line — a secondary support number, say — prove the agent out on real but less critical traffic, then move it to the main line.
• Multiple lines, one agent, different behavior. You might attach several numbers that all route to your workspace's agent, while shaping the persona, knowledge, and hours to suit each. A sales line and a support line can feel different even though the same agent answers both.
• Leave some lines untouched. A number you don't attach isn't affected at all. Direct desk lines, personal numbers, or a dedicated human-only line can stay exactly as they are.

The right shape depends on where your risk tolerance and your call volume are. Start where the value is highest and your ability to watch closely is best — usually one important line — then expand deliberately.

Don't degrade a trusted asset

The reason to go slowly is that your existing number is a trusted asset, and trust is asymmetric: it takes years to build and one bad week to dent. A brand-new number that answers poorly costs you little, because nobody was relying on it. Your main line answering poorly costs you real customers who dialed a number they trusted and got something worse than before. That asymmetry is the whole argument for careful configuration and thorough testing before production traffic — the downside of rushing lands squarely on your most valuable line.

This is also why the two-way, realtime quality of the agent matters more, not less, when it's on your own number. On an unfamiliar number a robotic experience is merely disappointing. On your recognized line it's actively brand-damaging, because callers expected you. Connect your number only once the agent behind it holds a conversation you'd be proud to have callers associate with your business.

After you connect: watch, then expand

Bringing your own number is not a one-time switch — it's the start of an operating rhythm. In the first days after a line goes live, review the completed calls closely: who called, how long the calls ran, how they ended, and whether the agent handled or escalated appropriately. This early traffic on your real number teaches you things no test call can, because real callers ask things you didn't anticipate.

Feed what you learn back into the configuration — fill knowledge gaps, adjust escalation triggers, refine the persona — and only then consider attaching more lines. The teams that succeed treat the first connected number as a proving ground and expand once they trust what they hear. The going-live checklist covers this rhythm in full, and measuring phone agent quality covers what to listen for.

Frequently asked questions

Can I use my existing business number, or do I need a new one? Use your existing number. That's the point — it's already on your listings and known to customers. You attach the numbers customers already dial so the same line is now answered by your agent.

Do customers have to call a different number? No. They dial the same number they always have. The only change is that it's now reliably and competently answered.

Can I connect more than one number? Yes. You choose which numbers to attach and which ones the agent owns. Start with one line if you prefer and expand once you're confident.

Will I lose calls when I switch over? Not if you go live carefully — configure and test fully first, switch deliberately, and watch the early real calls. The change is designed to be invisible to callers and reversible for you. See the going-live checklist.

Does the agent sound like my business or like a generic bot? Like your business. The numbers you attach route to your workspace's agent, configured with your persona, voice, knowledge, and handoff rules.

Can it make outbound calls from my number? Inbound is available at launch — answering calls to your connected numbers. Outbound dialing uses the same agent in a later release.

Should I connect my main line or a smaller one first? Either works. The main line delivers the most value fastest and the clearest performance signal. A smaller department line is a lower-stakes pilot if you're cautious. Just start where you can watch the results closely, and expand once you trust what you hear.

Does bringing my own number change anything for how the agent is configured? No. Whichever numbers you attach route to your workspace's agent with the persona, knowledge, hours, and escalation you set. The number is the front door; the configuration behind it is the same one you built. See how Agent Vani works.

What if I only want a human-only line to stay human? Leave it unattached. A number you don't connect isn't touched at all, so you can keep a dedicated human line exactly as it is while the agent covers other lines.

Where to go next

• Going-live checklist — the careful path to production
• How Agent Vani works — configure persona, knowledge, hours, and numbers
• Security & trust — how call data is handled