Configuration
General
The button text is fixed: Share contact info.
Advanced

Advanced tab of the Request contact node
What the user must share
WhatsApp lets the user choose which details from their card they share, and the button can’t restrict that. That’s why the node enforces the requirement, with two mutually exclusive options:
With either option, if the user replies with free text instead of tapping the button, they get the Retry message. A contact card sent from the attachments menu doesn’t unblock the node either: the user has to use the button.
Nodes that already had Mandatory selection turned on behave as Phone number without you having to reconfigure or republish them.
Using the captured number
When the user shares their number through the button and didn’t have one on record yet, the number is linked to the user and is available in the following nodes of the same execution:Use cases
Banking onboarding with BSUID users
Banking onboarding with BSUID users
A banking workflow that receives users identified only by BSUID needs the phone number to verify their identity: Request contact with Mandatory selection and Phone number keeps the flow from moving on until it has it, and the Retry message tells the user what’s missing.
Frictionless lead capture
Frictionless lead capture
A lead capture workflow wants to save the user’s contact without stopping the conversation: Request contact with Username accepts any shared card and leaves the number optional.
Next steps
Location Request
Ask for the user’s location with an interactive button
Contact
Send a contact card to the user