TL;DR: We built Phone Supported with the tagline "Skip the phone menus, get directly to an agent." Turns out that's not what we actually do, and it's not what makes us unique. Here's what we're changing and why.
The Problem With Promising an Agent
When we launched Phone Supported, we positioned it as a shortcut to human support. The hero on our homepage said: "Skip the phone menus. Get directly to an agent."
It was aspirational. It was also not true.
Our scraper maps phone trees. It calls a number, presses buttons, records audio, and uses AI to build a structured map of every menu, option, and dead end. That's genuinely useful. But we can't guarantee you'll reach a human, because:
- Account verification walls. Many phone trees require a valid account number, SSN, or other personal info to proceed past the first few menus. Our scraper doesn't have accounts with these companies, so we can't map what's behind those walls.
- Menus change. Companies restructure their IVRs without notice. The path to an agent that worked last Tuesday might dead-end today.
- Some paths don't lead to humans at all. Plenty of phone tree branches terminate in automated systems, voicemail, or just hang up.
Promising "get to an agent" when we can't reliably deliver it is a recipe for disappointed users. And disappointed users don't come back.
What We Actually Do (That Nobody Else Does)
Here's the thing we kept overlooking: nobody else maps phone trees.
Think about it. When you search for "PG&E customer service," Google shows you the phone number. Done. When you search for "how to reach a human at Xfinity," GetHuman gives you a few tips. But nobody shows you the actual menu structure... what happens after you dial, what options exist, where each path leads.
That data is invisible. Companies don't publish their IVR structures. When they change them, there's no record. You call, listen to prompts, press buttons, and hope for the best. Every single time.
We're the only ones capturing this data programmatically. That's our actual moat, and we've been burying it under a generic promise about reaching agents.
The New Framing: See Before You Call
We're repositioning Phone Supported around a simpler, more honest idea:
See what happens when you call... before you pick up the phone.
This is what we actually deliver. You can see the full phone tree for a company: every menu, every option, every dead end and agent connection. You know what to expect before you dial. You can plan your path, skip the trial-and-error, and make an informed decision about whether calling is even worth it.
This framing is:
- Honest. We show you the phone tree. That's it. No false promises about guaranteed human contact.
- Unique. Nobody else does this. Not Google, not GetHuman, not the companies themselves.
- Useful in ways we didn't expect. People use our maps to find department-specific numbers, understand what issues a company actually supports by phone, and discover options they didn't know existed (like callback features or direct extensions).
The Archive Vision
We touched on this in a previous post about building a time machine for phone trees, but now it's becoming central to what we do.
Phone trees are infrastructure that evolves silently. Companies add departments, remove options, restructure menus, and change hours... and none of it is documented anywhere. We're building a historical record of these changes.
Every time we scrape a phone tree, we save a versioned snapshot. Over time, this creates an archive: you can see not just what a company's phone menu looks like today, but how it's changed. Did they remove the refund option? Did they add a new department? When did they start routing you to a chatbot instead of a human?
Think of it as the Wayback Machine, but for phone systems.
We're not there yet... this is what we're building toward. But the foundation is already in place: versioned scrapes, timestamps, and the ability to diff menu structures over time.
What This Means For the Product
We're making several changes to reflect this new direction:
Content over promises. Our pages will lead with the actual phone tree data... what menus exist, what options are available, what you'll be asked for. Less marketing speak, more useful information.
Transparency about limitations. If we can't map past an account verification step, we'll say so clearly rather than pretending it doesn't exist. If a scrape is outdated, you'll see when it was last updated.
Every company page becomes a reference. When you search for "what happens when I call Delta Airlines," we want our page to be the definitive answer... with the full menu structure, the phone number, the options available, and when we last verified it.
What We're NOT Doing (Yet)
We've been tempted to add community features... letting users upload their own call recordings to help us map past account verification walls. It's an interesting idea, but it adds complexity we're not ready for. Right now, we need to make the core product findable and useful before we layer on community features.
The priority for 2026: make the data we already have discoverable, and keep expanding our coverage.
This is our first real strategic pivot, and we wanted to share it openly because we committed to building in public. If you've ever called a company and wished you could just see the menu before sitting through it... that's exactly what we're building.
Follow our progress at @PhoneSupported
Team PhoneSupported