ROASForm is a form and booking tool. You build a multi-step form, embed it on a page you already have or share it on its own link, and the leads flow into GoHighLevel or out to another app by webhook. Visitors can book a call on a GoHighLevel or Calendly calendar as part of the same flow.
This article is the honest list of what sits outside that, so you can plan around it instead of finding out mid-build.
Build the landing page. You embed the form into a page you already have. There's no page builder. See How to Embed Your Form on a Website.
Claim HIPAA compliance. Nothing in the product is certified HIPAA compliant, and you shouldn't collect protected health information on the assumption that it is.
Offer a public API. There's no API key and no MCP server for pulling submissions into another product. To get form data out, use a webhook — see Send form events to Zapier, Make, n8n, or your own backend. GoHighLevel is the exception: it has a real integration, and tags drive your workflows there.
Restore a deleted form. There's no trash can that brings a form and its submissions back. Duplicate a form before you delete it if there's any chance you'll want it.
Raise Calendly's limits. Bookings need a paid Calendly plan, and Calendly's rate limits are Calendly's. A higher ROASForm plan doesn't change either.
Give the Free plan paid features. Free is 50 completed submissions a month, one subaccount, the full-size badge, and no team invites. See ROASForm pricing.
The Integrations page lists several connections as Coming Soon: HubSpot, Close CRM, ActiveCampaign, Mailchimp, Zapier, Slack, and Google Sheets. They're on the roadmap and not available today.
Five form skins. TypeSkin, Chat Bot Skin, Calendar Skin, SmartSkin, and Spektra Skin. Your questions, logic, and design survive switching between them, so trying another skin costs nothing. One thing to know: on SmartSkin and on Calendar Skin in vertical flow, answered questions stay on screen, so logic that jumps from one question to another doesn't run — only rules that route to an ending do (which is how these skins still send a lead to the right calendar). If you switch those skins to show all fields at once, no routing logic runs and scoring decides the ending. The other skins run every rule.
Address autocomplete. The Address question has Google Places autocomplete built in, with an option to split street, city, state, postal code, and country into separate CRM fields. It's a question type, not a separate integration to set up.
Importing an existing form. You can import from GoHighLevel or Typeform by URL instead of rebuilding by hand. See Import a form from another tool.
Native Meta conversion tracking. The Pixel and the Conversions API are built into each form's settings. You don't need a thank-you page or a GoHighLevel workflow. See Track Meta conversions with the Pixel and the Conversions API.
Split testing. You can run an A/B test between form variants. See How to Run a Split Test.
ROASForm pricing
What to include when you contact support
