Your agent can deploy in seconds but cannot get a phone number. Dial fixes that - one API call and it gets a real one in about 10 seconds. It places and receives voice calls, sends and receives SMS in 200+ countries, and messages over iMessage. It can even read inbound verification codes, so phone-gated signups stop being a dead end. Works via REST API, CLI, MCP servers, and SDKs. Free credit on signup, no card.
Last year we were building an AI agent that needed to sign itself up for a service. It got all the way through the form, hit "we've texted you a code," and just... stopped. Dead. There was no workaround. A fully autonomous agent, defeated by six digits sent to a phone it didn't have.
This isn't an AI that answers your phone. It's a phone number that belongs to your AI.
Every agent framework has gotten very good at giving agents tools. But the moment an agent needs to exist in the physical world - verify an identity, call a human, receive a text - it hits a wall that was built for people:
- No way to provision a number programmatically - Registration paperwork that takes weeks before the first text sends - Per-seat pricing that makes no sense when you have 100 agents - No way for an agent to read an inbound code - Webhooks you have to host and route yourself
So we built the thing we wanted: one API call, and your agent has a real phone number in about 10 seconds.
What it can do: - Place and receive voice calls, with real-time transcription, using your own LLM or ours - Send and receive SMS in 200+ countries - Message over iMessage from its own number, with automatic RCS/SMS fallback - Read inbound codes, so phone-gated signups stop being a dead end - One webhook, one format, every channel
The fastest way to see it: paste this into Claude Code, Cursor, Grok Bot, Codex or any agent -
Get yourself a Dial phone number and call me. Say hello and that setup is working, then ask if I have any questions. Follow https://getdial.ai/skills.md
It signs itself up, provisions its own number, and your phone rings. No dashboard, no human in the loop. That's the whole pitch, and you can verify it in about 30 seconds.
We'll be here all day. What's the first thing you'd have your agent call or text? Genuinely curious - the answers to this are how we've picked most of the roadmap so far.
Giving an agent its own phone number feels weirdly obvious after seeing this 😅
Really smart infrastructure layer. Curious how you’re handling number reputation and spam detection as usage scales?
This is a really clean use case for agents. Giving them a real number in seconds feels like a missing piece. Congrats on the launch!
@galdayan The first thing I'd wire up isn't a signup, it's the agent telling me it's stuck. My biggest time sink this year is a long Codex run that quietly blocks on a question and sits there for half an hour while I assume it's working. A text when it needs a decision would recover more of my week than anything it's ever got wrong. The thing I'd want to know before building on it is what happens when a number goes bad, whether I get told or whether my agent just silently stops receiving codes and looks broken.
Interesting. I see on the website that it’s $3 per number. Is that the same in every country, or does the price vary by country?
If I don’t actually need a number but need to make calls in different countries for bookings, do you offer a calling service without having a number associated with it? If so, how much does it cost?
Seen that product being built from the ground up! Instead of stitching together a bunch of legacy solution - twilio,vapi and the alikes - you can spin up a number within minutes. The 10DLC feature is the killer capability imop
Pretty Dope @galdayan , This is a sign we are about to go full on Sci Fi and define what the new Sci Fi looks like. I know gated estates that uses a GSM module where the ternants calls the Sim Card attached to the Entrance. Imagine if My agent can handle this when I am a ternant.
Deliveries, Visitors will be able to be handled. Ofcourse this is one of the many usecases.
the dial wait-for message.received bit is the actual unlock, not the number itself. does the agent see the whole sms or just the extracted code?
Love this product so much, from the moment I started reading the docs!
The simplicity, the reliability, the call quality and the customization capabilities are very impressive!
Ofek here, one of the builders
the moment that still get me:
1. you tell your agent to get a phone number, 2. register with a OTP in chat 3. walk away 4. boom a minute later your own phone rings. No dashboard, no signup form, no one clicking anything,
Been using this since the early builds. I don't sit and wait for Claude to finish anymore- it just texts me when it's done, or calls if it needs a decision from me🔥🧑🏻💻
Hey guys, this is a super interesting product for a super real problem - makes me question the existence of AI voice agents entirely (and the whole VAD-STT-LLM-TTS stack). Are you using a speech to speech model's API for this?
I'm Omri, Co-Founder & CTO of Dial. 👋
A quick look under the hood, because "give your agent a phone number" turned out to be far less of a thin wrapper than we assumed. Three things were genuinely hard:
1. Making the agent the user, not you. No dashboard step, no API key to copy. The agent fetches a skill doc, signs itself up, provisions its own number and starts using it. Everything a human would click, it does over the same API.
2. One shape for every channel. A voice call, an SMS, an iMessage and a WhatsApp message are four completely different beasts underneath. They all come back to a single webhook in one format, so your agent handles one thing instead of four.
3. Letting an agent wait. dial wait-for message.received blocks until the text lands and hands the code back. That is what turns a phone-gated signup from a dead end into just another step.
I'm around all day. Especially curious what people want the webhook payload to carry that it does not yet.
About Dial on Product Hunt
“Give your AI agent a real phone number in 10 seconds”
Dial launched on Product Hunt on September 2nd, 2026 and earned 199 upvotes and 34 comments, placing #5 on the daily leaderboard. Your agent can deploy in seconds but cannot get a phone number. Dial fixes that - one API call and it gets a real one in about 10 seconds. It places and receives voice calls, sends and receives SMS in 200+ countries, and messages over iMessage. It can even read inbound verification codes, so phone-gated signups stop being a dead end. Works via REST API, CLI, MCP servers, and SDKs. Free credit on signup, no card.
Dial was featured in Productivity (659.7k followers), Messaging (52k followers) and Artificial Intelligence (477.6k followers) on Product Hunt. Together, these topics include over 289.2k products, making this a competitive space to launch in.
Who hunted Dial?
Dial was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Dial stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
Hey Product Hunt 👋
I'm Gal, founder of Dial.
Last year we were building an AI agent that needed to sign itself up for a service. It got all the way through the form, hit "we've texted you a code," and just... stopped. Dead. There was no workaround. A fully autonomous agent, defeated by six digits sent to a phone it didn't have.
This isn't an AI that answers your phone. It's a phone number that belongs to your AI.
Every agent framework has gotten very good at giving agents tools. But the moment an agent needs to exist in the physical world - verify an identity, call a human, receive a text - it hits a wall that was built for people:
- No way to provision a number programmatically
- Registration paperwork that takes weeks before the first text sends
- Per-seat pricing that makes no sense when you have 100 agents
- No way for an agent to read an inbound code
- Webhooks you have to host and route yourself
So we built the thing we wanted: one API call, and your agent has a real phone number in about 10 seconds.
What it can do:
- Place and receive voice calls, with real-time transcription, using your own LLM or ours
- Send and receive SMS in 200+ countries
- Message over iMessage from its own number, with automatic RCS/SMS fallback
- Read inbound codes, so phone-gated signups stop being a dead end
- One webhook, one format, every channel
The fastest way to see it: paste this into Claude Code, Cursor, Grok Bot, Codex or any agent -
Get yourself a Dial phone number and call me. Say hello and that setup is working, then ask if I have any questions. Follow https://getdial.ai/skills.md
It signs itself up, provisions its own number, and your phone rings. No dashboard, no human in the loop. That's the whole pitch, and you can verify it in about 30 seconds.
We'll be here all day. What's the first thing you'd have your agent call or text? Genuinely curious - the answers to this are how we've picked most of the roadmap so far.
you can also reach us directly at [email protected]
discord channel - https://discord.com/invite/tEmpesw6GW