FormAssembly review

FormAssembly is a forms and workflow platform for collecting information and routing it into business systems. It is aimed at organizations that need more than a basic contact form: the product combines multi-step forms, workflow automation, data validation, audit trails, security controls and integrations, including Salesforce connections.

The homepage lists Fai, an AI assistant that can help create forms, logic and Salesforce integrations from plain-language prompts. It also lists SOC 2 Type II certification on all plans, with FedRAMP and DoD IL4 available. Those claims are not a substitute for checking which controls and deployment options your own compliance requirements need.

The practical case for FormAssembly is complex data collection and process automation, particularly when Salesforce is part of the workflow. It is not an obviously low-cost choice: according to the pricing information available to us, rates are quotation-based, and monthly and annual prices are not published.

FormAssembly’s clearest strength is handling forms that need to collect structured information and move it through a business process. Its forms and multi-step workflows are designed for data collection and process automation, while validation can help ensure submissions enter connected systems in the expected structure. Audit trails and listed security controls matter when teams need to track compliance-relevant activity.

The Salesforce connection is a particular draw in user discussions. In one r/salesforce thread comparing FormAssembly with Formstack, a commenter said FormAssembly offered more options for complex forms, including writing to and retrieving Salesforce objects, though setup could be trickier. Another user described using it to collect extra information related to a Salesforce Case. These are individual reports, not a guarantee that every connector or configuration will behave the same way.

Fai is another listed capability: it can assist with creating forms, logic and Salesforce integrations from prompts. The pricing page also lists document generation and enterprise compliance on Atlas Enterprise. For government and regulated organizations, Gov Cloud lists dedicated environments and certified environment options. Check the exact deployment and compliance requirements with FormAssembly before treating those labels as a fit.

The biggest buying obstacle is price opacity. The pricing information available to us lists Atlas Explorer, Atlas Team, Atlas Enterprise and Gov Cloud, but publishes no monthly or annual rates. Seat and usage limits are also not published for Explorer or Team; Enterprise seat and usage limits are not published either. Enterprise has tiered response buckets, while Gov Cloud lists tiered response buckets and additional document allowances, but the bucket sizes and allowances are not stated.

Add-on packs for users, responses and documents are available without changing plans, but their prices and overage costs are not published. Gov Cloud’s listed core Enterprise features exclude AI. Budgeting therefore means getting a quote and asking for the included seats, response and document allowances, and overage terms in writing.

There are also concerning user reports. In one r/salesforce thread, users described Salesforce connectors failing or not running, duplicate records after reprocessing, and slow or unhelpful support. Other commenters reported intermittent syncing. These are anecdotes, not proof of a widespread current defect, but they are relevant risks to raise in a demo and contract discussion. A separate comparison thread describes FormAssembly as more capable for complex forms but trickier to set up.

FormAssembly does not publish plan prices; pricing is quotation-based, and monthly and annual rates are not listed. That means there’s no reliable way to calculate the jump between tiers from the available information. Ask for a quote that spells out your expected seat count, response volume, document needs, and any compliance requirements.

The listed plans are Atlas Explorer for individuals, Atlas Team for workgroups and small businesses, Atlas Enterprise for organizations needing enterprise capabilities, and Gov Cloud for government and regulated organizations. The plan details describe tiered response buckets for Enterprise and Gov Cloud, plus document generation on Enterprise and additional document allowances on Gov Cloud. Seat and usage limits are not published.

Budget for possible add-ons: user, response, and document packs are available, and the pricing information says they can be purchased without changing plans. Their prices and overage costs are not published. Get both in writing before committing; the plan names alone do not reveal your likely bill.

The available materials do not specify migration tools, supported export formats, transfer fees, or how much setup is needed to recreate forms and workflows. Before moving data, ask FormAssembly what you can export, in what format, and whether submissions, audit trails, workflow logic, and Salesforce connections transfer. Don’t assume a form export will include the surrounding process.

The review notes flag reports of connector problems and support concerns. That is worth checking directly if your workflows depend on reliable connections: ask about troubleshooting, escalation, and what happens to queued or failed submissions. Treat those reports as a reason to verify your own requirements, not proof that every connector fails.

If you’re leaving, confirm data access and export timing before ending the contract. If you’re switching in, price migration and connector rebuilding alongside the quote. With no published pricing, limits, or migration terms in the published information, those details need to be settled with the vendor before you plan a cutover.