Fix a mobile Call button that opens the wrong phone number

Compare the label with the destination

A customer taps Call and the dialer shows an old or unfamiliar number. Write down the visible label and the number opened by the button before editing. Check the header, footer, mobile sticky bar, service pages and campaign landing pages. Identical text can hide different link destinations, particularly after copied pages or template changes.

Check link type and shared components

Wix supports phone-number links as a distinct destination type. Use the appropriate link setting rather than placing a phone number in an unrelated web-address field. For custom sites, ask the maintainer to verify the telephone link's actual destination. A desktop calling-app prompt can behave differently from a phone, so test on a real mobile device.

Source checks: Wix Editor: Adding a Link to a Button · Wix Editor: Adding a Link to an Element

Test each live call entry point

Create a list of call entry points and their intended receiving line. Let the person answering calls know that marked tests are coming. Inspect the dialer before placing each test, then confirm the business identification and receiving device. Avoid testing an incorrect destination after discovering that it belongs to someone else.

• Open each published call entry point on mobile and record the number displayed in the dialer.
• Compare that destination with the owner's approved business number and the visible page text.
• Correct the phone link in the source component, including shared templates where applicable.
• Publish, reopen the page outside the editor and inspect the corrected dialer destination.
• Place an agreed test call and verify the answering or voicemail path with the responsible staff member.

Avoid repairing only the visible text

Changing visible text alone may leave the old link intact. Editing a desktop header may not update a separate mobile bar. A correct link can still forward to an inactive device or unrelated voicemail greeting. Do not count repeated test calls as marketing leads, and do not infer a connected conversation from a click statistic.

Measure link accuracy separately from connected calls

Track which buttons have verified destinations and which still require repair. For operational tests, record the device, page and receiving path. In reporting, distinguish a phone-link activation from an answered call or a useful conversation. The technical fix establishes destination accuracy; it does not establish future demand or the quality of enquiries.

Maintain one approved business number

Store one approved number with its display format, call-link destination and responsible account owner. Include the date it was tested and the places where it is reused. When the number changes, update the shared source first and then verify every distinct mobile component. Keep the written number visible for customers who cannot or prefer not to activate a call link.

Worked example: an illustrative customer journey

For example, a garage-door service displays its new number in a mobile header, but the sticky Call button still opens the previous contractor's line. The owner records the mismatch, then the maintainer changes the sticky component's phone destination.

A marked mobile test opens the approved number and reaches the service's answering line. The footer is tested separately. These checks verify the relevant destinations and receiving path; they do not show that every click in analytics became an answered customer call.

Questions about this task