Every phone number on your HubSpot forms, verified.
Before a protected form submits, the visitor enters a one-time verification code (OTP) sent to their WhatsApp, or by SMS. Real people get through in seconds. Fake and mistyped numbers never reach your sales team.
Built to live inside
FormVerify connects through HubSpot’s own app install. On HubSpot pages it’s one switch; on WordPress, Webflow, Shopify and the rest, one snippet.
Why a WhatsApp OTP beats a CAPTCHA
CAPTCHA tells humans from bots. It can't tell a real phone number from a fake one.
It proves the number is real
Only someone holding that phone can enter the code. A typo, a made-up number or someone else's number never becomes a contact.
It lands where people look
The code arrives in WhatsApp from your business, with a Copy code button. Visitors not on WhatsApp can get it by SMS.
It costs cents, only when delivered
Meta bills authentication messages only when they’re delivered, at its own rate for the visitor’s country. hubglo adds nothing on top.
One OTP. A number your reps can call.
Works on the HubSpot forms you already have. Set up in about ten minutes, free for 14 days.
- ✓ No form rebuild: you pick which forms ask for an OTP
- ✓ HubSpot pages with one switch, any other website with one snippet
- ✓ Verified contacts marked in HubSpot so sales calls them first
- ✓ Limits per number, per visitor and per day keep sending costs in check
"Won't verification hurt my conversion rate?"
Some of it, yes, and that's the point. When teams switch on OTP verification, raw submission counts dip, because fake numbers stop getting through. What's left is a smaller list of people your reps can actually reach.
And it's your call, form by form: gate the demo-request form where one fake lead wastes an hour of sales time, and leave the newsletter signup exactly as it is.
Questions, answered
What teams want to know before switching it on.
What is FormVerify?
FormVerify adds phone verification to HubSpot forms. When someone submits a protected form, it sends a one-time passcode (OTP) to their phone over WhatsApp or SMS and only lets the submission through once the code is confirmed. Fake, mistyped and borrowed numbers never become HubSpot contacts, so sales only calls numbers that work.
Do I have to rebuild my HubSpot forms?
No. FormVerify protects the forms you already use. On HubSpot pages, one switch adds it to your theme and covers every page, including ones you publish later; on any other website you paste one snippet. You then switch protection on per form.
How are passcodes delivered?
Over WhatsApp (through Meta’s Cloud API) or SMS (through Twilio). You connect your own WhatsApp Business or Twilio account during setup, so OTPs send from your accounts at Meta’s or Twilio’s rates; hubglo adds no markup. Every plan includes both, and with both connected, visitors whose number isn’t on WhatsApp get the OTP by SMS.
What’s the difference between OTP verification and CAPTCHA?
CAPTCHA tries to tell humans from bots, and modern bots increasingly pass it. It does nothing about a human typing a made-up phone number. OTP verification proves the submitter owns a real, reachable phone, which is what your sales team actually needs.
Won’t verification hurt my conversion rates?
Raw submission counts usually dip when verification goes on, and that dip is mostly fake numbers your sales team could never have reached. Protection is per-form, so you can gate high-intent forms like demo requests and leave low-friction forms like newsletter signups alone.
How does FormVerify prevent SMS pumping and abuse?
Layered rate limits: a phone number can request three OTPs per form every five minutes and ten per hour in total, an IP address fifteen per ten minutes, and every portal has a daily send cap (300 on Starter, 2,000 on Professional). Throttled attempts are logged in your audit trail, not silently dropped.
Is FormVerify a server-enforced firewall?
No. FormVerify gates submissions in the browser at submit time, which sharply raises the cost of spam and confirms real submitters. It is not a server-side block against someone deliberately posting straight to HubSpot’s form endpoint, but those submissions are easy to separate: turn on marking verified contacts and every verified lead gets FormVerify verified = Yes in HubSpot, while they never do. If an OTP can’t be sent because of an outage or a problem with your messaging account, the form submits rather than lose the lead, and the contact is marked No. It’s a phone verification tool, not a web application firewall.
How does billing work?
Billing runs through your hubglo account with a secure third-party payment provider. Every plan starts with a 14-day free trial (no credit card required), and you can manage or cancel anytime from account.hubglo.com.
What is hubglo?
hubglo builds the apps HubSpot lacks; FormVerify is the first. One hubglo account signs you into every hubglo app, and each app is billed separately, so you only ever pay for what you use.
Try FormVerify free for 14 days.
No credit card required. Protect real forms during the trial.
Start free trial