What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Yes. Connect your WordPress form plugin to an SMS service such as Twilio, then add an SMS action that runs when the form is submitted. The text can go to a site owner or staff number, or to the visitor’s phone field as a confirmation. The exact steps and required license depend on your form plugin.
First decide who should receive the text
“Get SMS messages from a WordPress form” can describe two different workflows:
- Owner or team alert: a fixed number receives a notification whenever a submission arrives.
- Visitor confirmation: the form’s phone field supplies the recipient, and the submitter receives a confirmation text.
The documented Gravity Forms, WPForms and Formidable Forms integrations primarily support outbound texts triggered by submissions. Formidable Forms also documents workflows in which people text information into a form, so inbound SMS requires a different configuration from a normal submission alert (Formidable Twilio documentation; Formidable SMS feature page).
What you need before configuring SMS
- A working WordPress form and its plugin’s current SMS integration or add-on.
- An account with an SMS provider. The documented integrations use Twilio.
- Provider credentials entered in the plugin, kept private rather than exposed in page content or messages.
- In many setups, an assigned Twilio phone number capable of sending to the destination country. WPForms specifically instructs users to purchase a dedicated Twilio number for its integration (WPForms Twilio Addon documentation).
- Any destination-country permissions or sender registrations required by the provider. Formidable notes that US SMS sending requires A2P 10DLC registration; requirements vary by country and use case (Formidable Twilio documentation).
Which WordPress form integration fits?
| Form plugin | Documented SMS capabilities | License or setup distinction |
|---|---|---|
| Gravity Forms | Texts after form submission or payment completion, customizable text with merge tags, conditional sending and optional Bitly URL shortening. | The Twilio add-on is listed as included with Pro, Elite and Nonprofit licenses. Its tutorial covers Twilio credentials, sender and recipient numbers, message text and conditions (integration page; SMS notification tutorial). |
| WPForms | SMS and WhatsApp notifications when forms are completed. | Install and activate the add-on, connect Twilio in WPForms settings and use a dedicated Twilio number. The reviewed guide does not establish current plan pricing (Twilio Addon documentation). |
| Formidable Forms | SMS on submission or entry update, plus documented text-in poll and survey workflows. | The add-on requires a Business license or above. Add a Twilio action under Actions & Notifications, enter API credentials and configure geographic permissions. US sending requires A2P 10DLC registration (Twilio SMS documentation). |
| Form Notify | The WordPress.org listing describes SMS, email and LINE notifications for supported form plugins. | Check current compatibility, maintenance activity and supported builders before deploying; the listing is a lead to evaluate, not an endorsement (WordPress.org listing). |
Using the form builder you already have is usually simpler than migrating. Confirm its current add-on and license requirements before changing plugins.
How to add an SMS notification
- Open the provider account. Create or connect Twilio, obtain the credentials requested by your plugin and acquire an eligible sending number if required.
- Enable the plugin integration. Install and activate the relevant add-on, then open its settings and save the Twilio account details.
- Add the form action or feed. In Gravity Forms, configure the Twilio feed; in Formidable Forms, use Actions & Notifications; WPForms uses its Twilio add-on settings. Select the form that should trigger the message.
- Choose the recipient. Enter a fixed, properly formatted staff number for alerts, or map the recipient to the form’s phone field for visitor confirmations. Gravity Forms documents both custom-number and form-field recipients (Gravity Forms tutorial).
- Write the message. Keep it short and include only the fields needed, such as the submitter’s name, reference number and a link. Use merge tags where supported. Add conditional rules when only particular answers, payment events or form states should send a text.
- Set geographic and sender rules. Confirm that the sender type, destination country and any registration or permission requirements are satisfied before enabling production traffic.
- Run a controlled test. Submit the form with a test recipient, verify the trigger and check that the intended number—not an accidentally exposed visitor number—received the message. The vendor documentation describes configuration flows, but it does not establish a guaranteed delivery rate or delivery time.
Message, consent and privacy checks
- Collect a phone number only when it is needed for the stated notification.
- Tell visitors what the number will be used for, especially if you will send anything beyond a one-time transactional confirmation.
- Do not place passwords, payment details or other sensitive information in SMS; texts can appear on lock screens and are not a secure document channel.
- Restrict administrator access to Twilio credentials and form entries, and review the provider’s current sending and compliance rules for each destination.
- Use a fixed internal number for staff alerts when visitors should not receive operational details.
Common problems and how to isolate them
The form submits but no text is sent
Check that the add-on is active, the SMS action is enabled for this form, credentials are valid, the sender number is assigned and the destination is allowed. Review the provider and plugin logs for rejected requests.
The visitor does not receive a confirmation
Verify that the phone field is mapped as the recipient, includes the correct international format and is not empty after conditional fields or validation rules run. Test with a number you control.
Rank #2
US messages are blocked
Confirm the required A2P 10DLC registration and geographic permissions described by Formidable, then check Twilio’s current requirements for your sender and traffic type (Formidable Twilio documentation).
Messages go to the wrong person
Inspect the recipient mapping and conditional logic. A fixed staff number and a visitor phone-field recipient are separate configurations; do not assume changing the message text changes the destination.
What SMS integrations do—and do not—promise
These integrations provide a connection between a form event and an SMS provider; SMS is not a default capability of every WordPress form. The cited vendor pages document setup and features, not independently measured delivery performance. Delivery can depend on provider approval, sender registration, carrier filtering, destination coverage and the recipient’s network, so treat a successful test as confirmation of your configuration rather than a guarantee of instant delivery.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.The Bottom Line
Keep your existing form builder when possible: connect its supported Twilio add-on, configure the correct recipient (staff number or visitor phone field), satisfy destination-country requirements, and test with a controlled submission before relying on SMS operationally.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
