Text your agent like you text anyone else.
Give it a number of its own. Call it and your agent picks up; when it has something for you, the message arrives in the app the way a message from a person does.
+003-01-04412-00001
+003 is the realm for bots, models and autonomous services. An agent number is an ordinary address in it, and everything that works on an address works on this.
Four things
Sign up, take a number, point it, talk to it
There is no integration in the middle of this. The number is issued to your account and the screen that configures it is the one you land on afterwards.
- 01
Create an account
Email and a password. Nothing to install, and nobody to get past first.
- 02
Take a number
Pick one in +003 and take it. Nothing to pay and no card, and it is held on your account while you try it.
- 03
Point it at your agent
One screen. Say where calls land, what gets through, and what may speak as the number. Or hand it a SIP URI and wire it yourself.
- 04
Talk to it
Open the Dial app and your agent is a thread in it, the same as a person. Call the number and your agent picks up.
Where it lands
You choose what happens when the number is used
One destination, changed whenever you like. Known callers ring through, strangers are screened and the middle of the night goes to voicemail, until you say otherwise.
Your agent, in your messages
The default, and the one that needs nothing from you. Your agent gets a thread in the app, and that thread is where it reaches you first.
Your own stack
A SIP URI you control. Asterisk, FreeSWITCH, FreePBX and 3CX all take a plain peer, and so does every voice-agent platform worth pointing a number at.
Another agent
One agent hands off to the next by address. Escalation is a destination, not an integration you build.
Your regular phone
Reaching the public network is the gateway interconnect add-on: an authorized identity is presented at the boundary, because a +0 address is never valid caller ID out there.
Channels
Voice and text on one address
Calls and messages resolve to the same number rather than to two things that happen to match. Each channel below is a switch on the rules screen, with what it carries and what it is waiting on.
A +0 address is a private overlay. It does not place or receive calls on the public telephone network on its own and cannot reach emergency services; reaching them is what the gateway interconnect add-on is for, and it presents an authorized identity at the boundary.
Bring your own stack
Whatever answers a trunk answers this
The number terminates as SIP and as policy, so the agent behind it is your choice. Paste a credential once and the switchboard keeps it. The browser never sees it again, and the gateway is the only thing that can spend it.
Agents that answer
Carriers and trunks
Rooms it can join
Where it reports
| Over SIP | Reach | What it takes |
|---|---|---|
| Softphones, desk phones, PBX | included | Register a client against this number, or forward it to a SIP URI you already run. Asterisk, FreePBX, FreeSWITCH and 3CX all take a plain SIP peer. |
| Voice agents | included | Vapi, Retell, LiveKit and ElevenLabs all answer a SIP trunk, so a call to this number can be picked up by an agent rather than a person. |
| Cisco Webex | included | Webex answers a plain SIP call, which makes it the one big meeting platform with nothing in the middle. |
| Carrier trunks | add-on | Twilio, Telnyx, Bandwidth, Vonage and Plivo will all terminate a trunk for you. What they carry to the public network is billed by them, not here. |
| Zoom | add-on | Reachable through Zoom's own room connector, which is a paid feature on the Zoom side. |
| Microsoft Teams | add-on | Reachable through a certified video interop provider, or by Direct Routing from a carrier trunk. Either way it is bought from them. |
| Google Meet | no | Meet publishes no SIP endpoint. It can be reached only through an interop gateway, so a SIP call cannot join a Meet link on its own. |
| Public telephone network | no | A +0 address is a private overlay. It does not place or receive calls on the public network and cannot reach emergency services. |
One each
Every agent gets its own address
A block is a run of numbers, so the agents in it differ by the last digit. Each one is reachable on its own, silenced on its own, and provably yours.
Everybody has an assistant that can talk. Nobody else hands you an address for it, lets you prove the answer came from yours, and lets you switch that one off without touching anything else you run.
Price
The number is free. You pay when you attach something.
Take it, point it at the Dial app, and there is nothing to pay and no card to leave. The charge starts when you attach a SIP route, which is what lets the number answer calls from outside Dial.
More than one agent is a block, registered for the year the way a domain is, and the rate falls with the size of it.
Straight answers
What people ask first
Is this a phone number?
It is an address on a private network, in the same shape as one. Dial it, message it, hand it out. What it is not is a line on the public telephone network, so it cannot reach emergency services. Crossing to that network is a gateway you add on purpose, never something that happens quietly.
Do I have to run anything?
No. Point the number at the Dial app and you are finished. Your own SIP endpoint, your own agent platform, a webhook: all there when you want them, and out of the way when you do not.
Which agent can I use?
Yours. The number terminates as SIP and as policy, so anything that answers a trunk or takes a webhook answers this. The switchboard ships knowing the common ones so a credential is the whole integration.
What if the agent goes wrong?
Switch that number off. Each agent holds its own address under your block, so revoking one is one number, not your main line and not the other agents.