What happens when a desktop visitor clicks your phone number
A tel: link on a laptop opens FaceTime, Phone Link, Skype or nothing at all. Here is what visitors actually see, and three ways financial firms can fix it.
· 6 min read · By the CallCeptor team
Open your firm's website on a laptop and click the phone number in the header. Depending on the machine, one of four things happens:
- macOS offers to call through FaceTime or an iPhone nearby, if the visitor has set that up. Many haven't.
- Windows asks which app should open
tel:links, or opens Phone Link, which needs a paired Android phone or iPhone. - A work laptop may hand the link to Teams or a softphone the visitor isn't signed into.
- Nothing happens, because no app is registered for the link.
In every case the visitor now has to find their phone, unlock it and type ten or eleven digits they are reading off another screen. Some do. Many decide to call later.
Why this matters more for financial sites
People read research reports, IPO notes, fund factsheets and PMS strategy pages at a desk. That is where the intent forms: someone has just read your view on a sector and wants to ask a question. The phone number is the one contact option that doesn't work on the device they are using.
The calls that do get through arrive without context. The person answering doesn't know the caller was on the IPO page, came from a Google ad, or is an existing client. They start from zero, often after an IVR menu has already sent the caller to the wrong team.
Three ways to fix it
1. Show the number, don't link it, on desktop
Keep tel: links on mobile and render the number as plain, selectable text on wider screens. It stops the confusing app prompts, but it doesn't make the number any easier to call.
2. Offer a callback form next to the number
A short form (name, mobile, topic) with a promised response time works for visitors who don't mind waiting. It fails the ones who wanted to talk now, and a form without a callback SLA tends to be answered the next day.
3. Let them call from the browser
Browsers have supported voice calls for years through WebRTC, the same technology behind Google Meet. A Call button can ring your team directly from the page, pass along which page the visitor was on, and fall back to a callback if nobody answers. On mobile it works just as well, so one button covers every device.
That is what CallCeptor does. If you want to see how routing by page works for a firm with several desks, read routing website calls by page.
A quick test you can run today
- Open your site on a Windows laptop and a Mac, and click the phone number on each.
- Note what opens, and how many steps it takes to actually hear a ring.
- Check your analytics for the share of sessions on desktop for research and product pages.
- Multiply the two findings together and you have a rough picture of how many visitors hit a dead end.
Written by the CallCeptor team, who build browser calling and call routing for Indian financial firms. Product details reflect what CallCeptor does today; anything on the roadmap is marked as such. This guide is general information, not legal or regulatory advice. Spotted a mistake? Tell us. See how we write.