Phone and Booking Links Not Working? A Website Checklist
When a phone or booking link is not working, check the visible label, the actual destination and the handoff to the next app or page. Stop before placing a real call, reserving an appointment or triggering payment unless that action is authorized. Opening a destination does not establish completion.
List the actions customers can use
Check the main service page, header, footer and any mobile-specific contact controls. A number can be correct in one place and outdated in another. Record the exact page and action label rather than treating all contact links as one component. The contact-test worksheet helps keep destinations and outcomes together.
Verify the phone handoff
MDN documents telephone links using the tel: scheme. A basic illustrative link looks like this:
<a href="tel:+15550100100">Call the example business</a>
This is a code example, not a number to call. Use the business owner’s verified number in a real implementation. Check that the visible wording and the destination agree. On a phone, inspect the number offered by the dialer and cancel before calling. On desktop, behavior depends on the configured calling application.
A dialer opening is evidence of a handoff, not evidence that the line is staffed or that a call would be answered. Availability claims such as emergency or round-the-clock support need separate business confirmation.
Check the booking destination
- Confirm that the link points to the correct provider, business and service, rather than an obsolete account or generic sign-in page.
- Inspect whether the destination is readable and usable on the test device.
- Check whether time zone, location, service and price information are clear where relevant.
- Stop before confirming a slot or payment. Use the provider’s documented test method if end-to-end verification is required and authorized.
A visible calendar does not prove that confirmations, staff routing or payments work. If those private stages are part of the agreed scope, the authorized account owner needs to verify them. Do not create a real booking merely to gather an audit screenshot.
Make the action understandable and reachable
Read the link as someone who has not seen the rest of the page. “Book a plumbing visit” gives a clearer expectation than several identical “Click here” labels. Check keyboard focus, visible contrast and whether another element covers the target. The W3C’s link-purpose guidance explains the importance of understanding a link’s destination from its context.
Use the mobile contact audit to investigate clipping and overlays. A technically correct destination can still be difficult to activate if the control is hidden or obstructed.
Treat email drafts as a distinct next step
An email link can open a draft instead of transmitting a message. Its outcome depends partly on the visitor’s configured app. Explain that the visitor must send the draft. Offer a readable business email address and a suitable alternative when possible; do not silently label draft preparation as successful delivery.
For forms that send to a server, use the form-to-inbox troubleshooting guide. The correct acceptance check depends on the intended design.
Keep a result that can be rechecked
Illustrative example. A footer displays the new office number, but its link still contains the old number. Record both values privately, obtain the correct destination from the owner, update the link and repeat the dialer handoff check. Do not infer how many enquiries were missed. This is a teaching scenario, not a customer case.
After any agreed change, recheck relevant copies of the action across pages and device layouts. Record “not checked” for private stages outside scope. A bounded repair should define those stages and the evidence required for explicit acceptance.
Want evidence from your own website?
Request a free one-page diagnostic with up to three verified issues, supporting screenshots and recommended fixes. Implementation is optional and separately quoted.
Request a free diagnostic