Why I Built Fissible Phone
Why I'm building a business phone app for iPhone around your own Twilio account, multiple businesses, and fewer spam calls.
I didn't set out to build another phone app. I wanted a business line I could trust.
Fissible Phone is an iPhone business phone app that runs on a Twilio number you own in your own Twilio account.
The day my own business line finished porting to Twilio, the old phone app that used to ring my cell stopped being part of the setup. That's exactly what I wanted: the number had moved into an account I controlled. It also made the tradeoff obvious. Twilio had the number, but I still had to make it behave like a real phone line again.
That meant wiring call forwarding, SMS routing, voicemail, outbound calling, and a way to understand what happened when a call didn't go through. It was fine for me as a developer. It wouldn't be fine for most owners who just need the phone to work.
That gap is why I'm building Fissible Phone.
What is Fissible Phone?
It's a business phone app for owners who want the convenience of an iPhone app without putting the whole phone system inside someone else's account.
Hosted apps like OpenPhone or Google Voice can be the right fit when you want a finished phone account immediately. The part I didn't like was what tends to come with that convenience. The number may be portable in theory, but the routing, voicemail behavior, call history, configuration, and operating habits live in the vendor's product.
I wanted a different default:
- a number in my own Twilio account
- iPhone-first calling that works with iOS instead of fighting it
- spam defense with visible outcomes
- separate lines for separate businesses
- voicemail that is easier to review
- a documented setup path instead of a telecom scavenger hunt
Your Twilio account. Your number. Your exit plan.
Why isn't call forwarding enough for a business line?
Forwarding calls to your cell is useful, but it's a thin business phone system.
Unknown calls are the problem. Some are customers. Some are spam. Some are vendors. Some are carrier weirdness that looks like a person calling and hanging up.
When every business call lands in your personal recents list, you lose context. If the call fails, gets screened, hits voicemail, or never rings your phone, you often don't know why. For a side project, that might be annoying. For a real business line printed online, in Google Business Profile, or on a truck, it's a leak.
Fissible Phone is built around the idea that a business line should defend itself and leave a record. If a caller rang through, failed a screen, went to voicemail, or was blocked, you should be able to see that without digging through carrier logs.
How do you manage phone numbers for multiple businesses?
I don't think the one-owner, one-company, one-phone-number model matches how many small businesses get built now.
You might have an LLC, a local service offer, a consulting line, and a product experiment that isn't ready for a full team. Those lines shouldn't all share the same rules, voicemail, caller context, or follow-up workflow. They also shouldn't require carrying extra phones.
Fissible Phone is meant to keep those business identities separate while still letting one owner run them from one iPhone.
Why build on Twilio instead of hiding it?
Twilio is powerful because it's programmable. It gives developers phone numbers, APIs, webhooks, call routing, recordings, messages, and programmable voice.
That power is also the problem for a normal owner. Twilio is not, by itself, a finished phone product. If you want it to ring your phone, store messages, handle voicemail, support outbound calling, and explain call outcomes, you have to assemble those pieces.
Fissible Phone sits on top of that infrastructure. Early access starts with a documented Twilio setup guide and hands-on onboarding where needed. Over time, more of that setup should move into the product, but I don't want to pretend a one-click wizard exists before it does.
What ships first?
The first version is intentionally practical:
- business numbers on iPhone
- native-feeling calling within the limits of iOS
- multiple businesses and lines in one app
- per-line call defense
- transparent recent-call outcomes
- voicemail review
- documented setup for owners who bring their own Twilio account
The bigger vision is a planned AI receptionist for small businesses: something that can screen calls, ask useful questions, summarize intent, detect urgency, and route callers without pretending every owner has a front desk.
But the foundation comes first. A phone line has to be reliable before it gets clever.
Who is this for?
Fissible Phone is for entrepreneurs, solo operators, and small teams who want a serious business line without renting their business identity from a phone app.
It's also for owners with more than one business, more than one line, or more than one reason to protect their attention.
I'm starting with iPhone because that's where I need it first. If the problem is familiar, the early access list is open.
Fissible Phone uses Twilio-powered communication infrastructure. It is not affiliated with, sponsored by, or endorsed by Twilio.
Frequently asked questions
Do I need a Twilio account to use Fissible Phone?
During early access, yes. Fissible Phone is designed around a Twilio number you own in your own Twilio account.
Is Fissible Phone iOS only?
Yes. The first version is focused on iPhone. Android interest is being tracked, but it is not part of the first build.
Can I leave and keep my number?
That's the point of the product direction. Your number and Twilio infrastructure stay in your own account instead of being locked inside a hosted phone vendor.
Is Fissible Phone affiliated with Twilio?
No. Fissible Phone uses Twilio-powered communication infrastructure, but it is not affiliated with, sponsored by, or endorsed by Twilio.