For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to add a share contact info button to a template

Learn how to add a Share Contact Info button to a template so customers can share their phone number with your business in one tap.

Some WhatsApp users message businesses using a username instead of their phone number, so you may only have their BSUID and not an actual number to reach them on. The Share Contact Info button lets you ask for it directly — the customer taps it, and their phone number lands with your business in one go.

What's covered

How to create a Share Contact Info template

  • Go to Templates and click New Template.

  • In Basic info, enter a name for your template. Use only lowercase letters, numbers, and underscores, for example share_contact_info.

  • Select the Category, Language, and Channel for your template, then click Next.

  • In Content, add a Header if required. The header is optional.

  • In the Body section, enter the message you want to send to your customers. For example: "Hi, we'd like to have your phone number so we can continue assisting you and keep in touch with you. Please tap on the button below to share your contact information."

  • Add a Footer if required. The footer is optional. Once you have added your content, click Next.

  • In Buttons, click Add a button and scroll through the available options to select Share Contact Info. The button text is fixed and cannot be customized.

  • Review the template using the Message preview, then click Submit.

  • Once submitted, Meta will review the template. This process can take 24–48 hours. After the template is approved, you can start sharing it with your customers on WhatsApp.

Keep in mind

  • Share Contact Info must be the only button in the template — you can't add any other buttons alongside it.

  • Once a customer taps it, their phone number is shared with your business and can be used anywhere a phone number is needed, including sending them an OTP or verification code.

Why use it

  • Reach customers who message via username — get their actual phone number when you only have their BSUID.

  • One-tap sharing — no manual back-and-forth asking a customer for their number.

  • Unlocks authentication — a phone number collected this way can be used for OTP and verification templates, which can't be sent to a BSUID alone.

Who can see a customer’s shared phone number

Once a customer shares their phone number, who gets to see it in full depends on your business's privacy setting. Team members who don't have permission to view customer phone numbers will see the shared number hidden — for example, +91XXXXXXXX40 — instead of the full number. This follows your business's existing privacy setting, which can be set to show just the last 2 digits or hide the whole number.

Key takeaways

  • Add a Share Contact Info button from Add buttons in the template builder.

  • It must be the only button on its template.

  • Use it to collect a real phone number from customers who message you via a WhatsApp username.

  • Team members without phone number visibility will see shared numbers masked, per your business's privacy setting.

Frequently asked questions

Can I combine Share Contact Info with other buttons?

No. Share Contact Info must be the only button in the template.

Can I rename the Share Contact Info button?

No. Its label is fixed as "Share Contact Info."

Why would I need this button?

If a customer messages you using a WhatsApp username, you may only have their BSUID and not their phone number. This button lets them share it with you directly.

Can I use the collected number to send an OTP?

Yes. Once a customer shares their phone number, you can use it for authentication messages, which require a real phone number and can't be sent via BSUID alone.

Will every team member see the shared phone number in full?

No. Team members without permission to view customer phone numbers will see it masked, showing only the last 2 digits or none at all, based on your business's privacy setting.

Last updated