Request contact

The Request contact node sends a message with the Share contact info button so the user can share their WhatsApp contact card. Use it to get the phone number of users who arrive identified only by their username or BSUID, and to hold the flow until you have it.

Configuration

General

Field	Description	Limit
Message	Text that goes with the button and explains why you need the user’s details	1,024 characters

The button text is fixed: Share contact info.

Advanced

Field	Description
Mandatory selection	Either way, the flow waits for the user to share their contact. When it’s on, the user has to reply with the button, and any other message gets the Retry message. When it’s off, the user can write something else and the project router handles it. See Without mandatory selection.
What must the user share?	Sets which reply unblocks the flow. Only shows up when Mandatory selection is on.
Retry message	Text the user gets when their reply doesn’t meet the requirement. If you leave it empty, this is sent: Por favor, comparte tu información de contacto usando el botón para continuar. Only shows up when Mandatory selection is on.

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:

Option	The flow moves on when	If the user shares only their username
Phone number (default)	The reply includes a phone number	They get the Retry message and the node keeps waiting
Username	The user shares their contact, with or without a number	The flow moves on

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.

Without mandatory selection

With Mandatory selection off, the node works like Buttons or List without mandatory selection: it sends the message and waits for the contact card, but it doesn’t hold the user. The flow only moves on through the node’s output once the contact arrives, so the following nodes can already use what the user shared.

If the user…	What happens
Shares their contact with the button, with or without a number	The flow moves on through the node’s output. If the card includes a number, it’s available as `{{$user.phone}}`
Writes any other message	The project router handles the message and may start another workflow. This flow keeps waiting for the contact
Shares the contact after entering another workflow	The flow that asked for the contact resumes, just like tapping a button on an earlier message
Doesn’t reply	The flow keeps waiting. There’s no expiration output, and after 24 hours the contact no longer resumes the flow

If nothing is connected to the node’s output, the flow ends there, same as before. A card sent from the attachments menu doesn’t resume the flow: the user has to use the button.

Using the captured number

With or without Mandatory selection, 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:

Thanks, we saved your number {{$user.phone}}

Use cases

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

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.

Ask for the phone number without blocking the conversation

A sales workflow asks for the contact to register the customer, but the customer may first ask for an agent or a branch: Request contact without Mandatory selection lets the router handle those questions and, once the customer shares their card, the registration continues. Since the card may arrive without a number, a Conditional node checks whether {{$user.phone}} is empty before saving it and, if it’s missing, asks for it another way.

This node only works on WhatsApp channels.

Next steps

Location Request

Ask for the user’s location with an interactive button

Contact

Send a contact card to the user

Getting Started

Developer

Jelou CLI

Outbound Messaging

Inbox

Marketplace

Channels

Configuration

Billing

Configuration

General

Advanced

Without mandatory selection

Using the captured number

Use cases

Next steps

Location Request

Contact

​Configuration

​General

​Advanced

​What the user must share

​Without mandatory selection

​Using the captured number

​Use cases

​Next steps

Location Request

Contact

Configuration

General

Advanced

What the user must share

Without mandatory selection

Using the captured number

Use cases

Next steps