Chat link without context
- —The WhatsApp entry point is buried in page content
- —Visitors start a chat without knowing what to write
- —The mobile contact path competes with unrelated actions
← ButtonFlow overview
Add a WordPress WhatsApp contact button with ButtonFlow
Use the WhatsApp Chat action when the site's intended mobile next step is a conversation rather than a generic contact page. ButtonFlow keeps one site-wide invitation on included pages and opens the configured wa.me destination with an optional message ready to edit.
WordPress WhatsApp CTAmobile WhatsApp chat buttonpre-filled WhatsApp message WordPress
Give a WhatsApp enquiry a clear starting point.
A WhatsApp CTA is most useful when the visitor knows what will happen after the tap. ButtonFlow provides the mobile entry point, the international number supplies the destination, and an optional message gives the conversation context.
A prepared chat handoff
- —The WhatsApp CTA stays available at the mobile-only boundary (<=767px)
- —The tap opens the configured wa.me destination
- —An optional pre-filled message gives the enquiry a starting point
Use the message to name the visitor's reason for writing.
The pre-filled message is optional and site-wide. Keep it short, editable, and relevant across every included page so the visitor gets a useful first line without being forced into a script.
General enquiry
Action: WhatsApp Chat. Number: +12025550147. Message: Hi, I have a question about your services.
- —Use a neutral prompt when the CTA appears across multiple service pages
Appointment request
Action: WhatsApp Chat. Number: +12025550147. Message: Hi, I would like to ask about appointment availability.
- —Name the next step without promising a time slot
Property enquiry
Action: WhatsApp Chat. Number: +12025550147. Message: Hi, I would like more information about this property.
- —Use a reusable prompt when several listings share one site-wide contact number
No pre-filled message
Leave the optional message empty when visitors should start the conversation in their own words. The WhatsApp number still needs to be entered in international format.
- —Choose a label such as Chat with us so the action remains explicit
Configure the destination before the invitation.
Open Settings → ButtonFlow and choose WhatsApp Chat. Enter the business number in international format, then add a pre-filled message only if it helps the visitor explain why they are contacting the business. The number is the destination; the message is supporting context.
When the visitor taps the mobile CTA, ButtonFlow opens the corresponding wa.me destination. Keep the phone value consistent with the business's approved WhatsApp number and test the handoff on a device with the expected WhatsApp behavior.
ButtonFlow v1.2.0 shows the control at the <=767px boundary. Use the label, icon, colors, Small, Medium, or Large size choice, and show delay to make the invitation visible without turning it into a second navigation system.
Publish the WhatsApp contact path in five steps.
Choose one message pattern for the site-wide configuration, then verify the destination and display rules across the included pages.
Install and activate
Install ButtonFlow from the WordPress plugin directory and activate it on the site.
Select WhatsApp Chat
Go to Settings → ButtonFlow and choose WhatsApp Chat as the action type.
Enter the chat details
Add the business WhatsApp number in international format and decide whether the site-wide CTA needs an optional pre-filled message.
Style the invitation
Set the label, icon, colors, Small, Medium, or Large size, and show delay. Make the label describe a chat rather than a phone call.
Test the boundary
Save and test at the <=767px boundary. Add page IDs or slugs to the exclusion controls when a page should not invite a WhatsApp conversation.
Check the number, message, and page rule.
A WhatsApp CTA should be easy to inspect before it is easy to tap.
Destination check
Compare the international number in Settings → ButtonFlow with the business number that owns the WhatsApp conversation.
- —Confirm that the selected number is the intended wa.me destination
Message check
Open the CTA on a mobile viewport and confirm the optional pre-filled message is short, accurate, and still editable before sending.
- —Use page exclusions if the site-wide message is not relevant to a section of the site
Exclusion check
Resize above and below 767px, then visit one included and one excluded page to confirm ButtonFlow's page IDs and slugs are doing what the site needs.
- —Review exclusions after changing a page's slug
Common questions.
Is a pre-filled WhatsApp message required?
No. The message is optional. You can leave it empty so visitors begin in their own words, or add a short prompt that gives the enquiry context.
How should I enter the WhatsApp number?
Enter the number in international format in Settings → ButtonFlow. WhatsApp Chat uses that value for the wa.me destination.
Where does the WhatsApp button open?
The WhatsApp Chat action opens the configured wa.me destination, with the optional pre-filled message available as the conversation starts.
Does the WhatsApp CTA appear on desktop?
No. ButtonFlow v1.2.0 is mobile-only and shows the CTA at the <=767px boundary.
Can I exclude pages from the WhatsApp CTA?
Yes. Add the WordPress page IDs or slugs that should be excluded in ButtonFlow's page exclusion controls, then verify an included and excluded page.
Put this guide into practice with ButtonFlow.
Review the plugin features, requirements, and other implementation guides, or install it directly from WordPress.org.