Set up FormVerify in four steps

In FormVerify, open Channels, choose WhatsApp and click Connect with Facebook. Follow Meta's steps to pick your WhatsApp Business account and number. Then choose an approved message template or create one right there; OTPs start sending once Meta approves it, which is often instant.

In Channels, choose Twilio SMS and click Connect with Twilio, or enter your Account SID, Auth Token and the number OTPs should come from. FormVerify sends a test message to confirm it works.

Connect both WhatsApp and Twilio SMS, then in Channels turn on “If WhatsApp can't deliver, use SMS”. When a number isn't on WhatsApp, the visitor gets a fresh OTP by SMS a few seconds later. Without it, the popup tells them the number isn't on WhatsApp and asks for another.

OTPs go out from your own WhatsApp Business or Twilio account, so Meta or Twilio bill you directly at their usual rates. hubglo adds no markup. Meta only charges for WhatsApp messages that are delivered. Every plan includes both WhatsApp and SMS.

HubSpot forms, on HubSpot pages or embedded on another website with HubSpot's embed code. Forms your website builder makes itself, like WPForms or Webflow forms, aren't covered. On a website HubSpot doesn't host, use forms made in HubSpot's legacy form editor: forms from the new editor load inside a frame there that FormVerify can't reach, and Forms shows “Skipped on 1 page” next to them.

Go to Site. Under Pages where FormVerify loaded you'll see each page it ran on in the last 30 days and the HubSpot forms it found there. A new install shows up within a minute of someone opening the page.

Go to Site → Popup and pick your brand color; the preview shows exactly what visitors see. You can also set the country used for numbers typed without a country code.

Forms has a ready-made consent line, such as “By submitting, you agree to receive a one-time verification code from Acme on WhatsApp.” Copy it and add it under the phone field in your HubSpot form.

Reports shows how many visitors asked for an OTP, how many OTPs were sent and how many verified, plus each form's pass rate and delivery by channel. Overview shows the latest activity as it happens.

Turn on Forms → Mark verified contacts in HubSpot. A minute after a visitor verifies, their contact gets FormVerify verified: Yes, with the number and time, in the FormVerify property group. Use it to send verified leads to sales first. A contact that was let through because no code could be sent gets No. Empty doesn't mean spam: forms you haven't protected never verify. FormVerify only updates contacts your form created; it never creates contacts.

If FormVerify can't send an OTP for a reason the visitor didn't cause (WhatsApp or Twilio is down, your template was paused, your account was blocked), the form submits without an OTP and the contact is marked FormVerify verified: No. A number that isn't on WhatsApp, or isn't a real number, is never let through. When your channel can't send, a banner appears in FormVerify and your portal's admins get one email saying why.

Check that FormVerify is on for your site (Site), the form is switched on in Forms, and the phone field has a value. If FormVerify shows a banner that WhatsApp or SMS can't send, forms submit without an OTP until that's fixed. On a website HubSpot doesn't host, forms from HubSpot's new form editor can't be checked; use a legacy-editor form.

Open Channels and make sure the channel shows Connected and its template shows Approved. If a channel can't send, the banner at the top of FormVerify says what Meta or Twilio reported. The visitor's number must use WhatsApp for a WhatsApp OTP; turn on SMS fallback to cover those who don't. One number can ask for three OTPs every five minutes, so someone retrying a lot may need to wait.

Open a page that has your form in a normal browser window (some ad blockers stop scripts), then check Site again after a minute. Make sure the snippet is inside <head> and that you published the change. If your site sets a Content-Security-Policy, allow https://formverify.hubglo.com for scripts and connections.