Send4 – AI SMS Lead Follow-up for Contact Forms

Send4 texts every new lead from your WordPress contact forms within seconds. When someone submits a Contact Form 7,
WPForms, Gravity Forms or Elementor Pro form on your site, this plugin hands the submission to your Send4 account, and
the AI flow you set up there starts an SMS conversation with that person: it answers their questions, asks what you
need to know, and can book a call.

Most leads that come through a contact form go cold before anybody answers them. Send4 is the follow-up that
answers first.

You do not have to build a payload, sign a webhook, or write a line of code. Install the plugin, connect it to
your Send4 account with one button, pick which form field holds the phone number, and turn the form on.

What it does

• Works with Contact Form 7, WPForms, Gravity Forms and Elementor Pro.
• Maps the phone number, name and email once per form, in wp-admin.
• Passes every other field through as context, so the AI knows what the person asked for.
• Retries for about a day and a half if Send4 is briefly unreachable, so a lead is never lost.
• Tells you, per form, whether the last submission arrived and whether a Send4 flow is listening for it.
• Optionally adds a country picker to your phone field, and refuses a number with no country code while the
  visitor is still on the form — so the number Send4 gets is one it can text.

You need a Send4 account and a number to text from. Send4 is a paid service; this plugin is the WordPress half
of it. Send4 texts your leads through your own Twilio or Vonage account, which you connect in Send4. If your leads are
in Lithuania, Send4 can provide the sending number instead. Until everything is in place, the plugin’s dashboard lists
what is still missing, with a link to fix each step in Send4.

External services

This plugin sends data to Send4 (https://send4.ai), the service it integrates with. Nothing is transmitted
until you start connecting the site to Send4, and no visitor’s submission is sent until you also enable a form.

• Connecting. Pressing Connect with Send4 sends your site’s address and the address of this plugin’s
  Connection screen in wp-admin, so that Send4 can create an API key bound to this site and send you back here
  to finish; the one-time code it returns is then exchanged for that key. If you paste an API key instead, the
  key is sent to Send4 to obtain an access token and to confirm which account it belongs to.
• What is sent: for each submission on an enabled form — the phone number, name and email address you
  mapped, the remaining form fields, the form’s name and key, your site URL, and a random submission
  identifier used to avoid sending the same lead twice.
• When: at the moment the form is submitted, and again on retry if the first attempt failed.
• Where: to https://app.send4.ai by default, over HTTPS.
• A list of your forms. So that Send4 can offer your forms by name when you build a flow, the plugin
  also sends a description of every form it detects: the form’s name and key, whether you have enabled it
  here, and each field’s label and type. No submitted values are included — this describes the shape of
  your forms, not anything a visitor typed. It is sent when you connect the site (before any form is
  enabled), when you change a form’s settings, once a day, and when you press Sync forms to Send4.
• Which versions this site runs. With the list of forms, the plugin sends the version of this plugin, of
  WordPress, of PHP and, when it is installed, of WooCommerce, the site’s language, and whether the site is part of
  a multisite network. Send4 uses this to know which versions are still in use before it changes anything they
  depend on.
• Checking the account. When you open the plugin’s screens, and once a day, the plugin asks Send4 which flows
  listen for this site’s forms, whether your account is ready to text leads, and which version of this plugin Send4
  needs. That request sends nothing but the connection’s credentials and the User-Agent described below.
• With every request the plugin identifies itself and its version, and includes your site’s address, in the
  HTTP User-Agent header.
• Send4’s terms of service: https://send4.ai/terms — privacy policy: https://send4.ai/privacy

Because the data you forward includes personal information about your visitors, tell them so. Your form
needs a clear consent line explaining that submitting it means Send4 may text them, and your privacy policy
should name Send4 as a processor. In the United States, SMS follow-up is also regulated by the TCPA and
carrier 10DLC rules; get consent language right before you switch a form on.

Third-party libraries

The country picker bundles intl-tel-input 29.2.3 by Jack O’Connor, under the MIT licence
(https://github.com/jackocnr/intl-tel-input). It is shipped unmodified in public/lib/intl-tel-input/, with its
licence, and the unminified source sits next to the minified build. One image is renamed, flags@2x.webp to
flags-2x.webp, because the plugin directory does not accept an “@” in a file name. Everything is served from your
own site; nothing is loaded from a third-party host.

utils.js, which formats and checks the number, is a compiled build. It is Google's libphonenumber (Apache License

2.0, https://github.com/google/libphonenumber) with intl-tel-input’s wrapper, compiled by Google Closure Compiler.
The sources and the build script, at the version shipped:

• Wrapper source: https://github.com/jackocnr/intl-tel-input/blob/v29.2.3/packages/core/src/js/utils.js
• Build script: https://github.com/jackocnr/intl-tel-input/blob/v29.2.3/scripts/build-utils.js (npm run build:utils
  in that repository, which pulls libphonenumber in as a git submodule)