Form Management & Data Collection
A Form is often the first place a Client tells you what they need. That answer should do more than arrive in an inbox. In SuiteDash, you can collect the details, connect them to the right record, and configure what happens next.
Use the Form type that fits the moment: a public Kickoff Form for a new relationship, an authenticated Update Form for an existing Contact, a Checkout Form for a purchase, or a Work Request Form when a Client is ready to ask for a specific service. Support, General, and Subscriber Forms cover other kinds of requests. Each type has a different job; choosing the right one matters.
This guide explains those differences and shows how Form submissions connect with the wider SuiteDash Platform. For a quick visual tour, see the Forms feature page.
One Form toolkit, several moments in the Client journey
The word “form” can describe very different jobs. A first-contact form may need to create a Contact; an account update should change an existing record; a general questionnaire may need no Contact record at all. SuiteDash gives those jobs distinct Form types instead of forcing every submission through the same workflow.
Kickoff Forms
Publish a link or embed the Form on your website to begin a sales or onboarding journey. Configure the Contact role and Coordinator, then optionally assign a Circle, start an On-Boarding FLOW, or run Automations when the Form is submitted. A Kickoff Form can also be used by an existing Contact to update information or start another configured action.
Update Forms
Ask a known Contact to review or add information. The Contact accesses this Form through an authenticated route, and submitted values can update the Contact’s CRM profile. Use it when you need an existing record to stay current, rather than opening a public intake route.
Checkout Forms
Let a buyer select configured Items, Add-ons, or Packages and see the total change with those choices. An on-page payment option can complete the purchase. Checkout Forms can be shared by link or embedded on your website or in the Portal.
Work Request Forms
Give Clients a guided way to request work. An Itemized request uses predefined offerings; a Free-Form request captures an open-ended brief. The steps save progress as the Client moves through them, and submission can be configured to create an Invoice, Estimate, Project, or Task.
Support Forms
Collect the information needed to open a Support Ticket. A direct link or embed can bring the request in from outside the Portal, while the Support Tickets toolkit gives your team a place to manage the resulting conversation.
General and Subscriber Forms
Use a General Form for responses that should be stored as submissions without being matched to a Contact or Company. Use a Subscriber Form when the goal is to add someone to an Email Marketing Audience.
The Forms overview in SuiteDash Help explains the access rules and setup options for each type.
Collect the right detail, not every possible detail
Build a Form from the fields the next step actually needs. Default Fields and Custom Fields let you gather standard Contact information and business-specific answers. Depending on the Form type, Advanced Blocks can add choices, explanatory HTML, or appointment booking options.
Conditional Logic can show or hide fields based on earlier answers. A service request might ask for a project deadline only when the Client selects a time-sensitive service. Another answer might reveal the appointment block that fits that path. Multiple conditions can use ANY or ALL rules, so one Form can stay short while still handling different situations.
Plan the questions in the order a person would naturally answer them. Put the essential choice first, then ask for the details that choice calls for. Use clear field labels and a short explanation when a question could be misunderstood. The result is easier for Clients to finish and easier for Staff to act on. See the Conditional Logic guide for the exact field behavior and setup.
Make the submission the start of the next step
A completed Form has value because someone can use the answer. A Kickoff Form can create a CRM Contact with the Role and Coordinator you chose, place that person in a Circle, and begin an On-Boarding FLOW. A Work Request can move into the work or billing tools your team already uses. A Support Form can start a Ticket. These are configured outcomes, so decide what should happen for each Form before publishing its link.
Consider a design agency receiving two requests. A new prospect completes a public Kickoff Form and enters an onboarding path. A current Client uses a Work Request Form to brief the next design job; that request can become a Project or Estimate. The same team can see the relevant information in SuiteDash without retyping the answers into a separate form service and then into a separate delivery tool.
Submitted Forms can be reviewed from the Form’s submission list and, where associated with a Contact, from that Contact’s dashboard. This gives Staff a place to check what the person actually supplied before responding. The Automation Suite can connect Form events with other configured steps across the Platform.
Choose the Form type before you build the questions
Starting a new Client relationship? Begin with a Kickoff Form. Decide who should own the Contact, which role they should receive, and whether an On-Boarding FLOW should begin.
Updating an existing Client’s details? Use an authenticated Update Form so the submission goes to the known Contact record. A public Kickoff Form serves a different purpose.
Selling a configured offer? Use a Checkout Form to present the available Items, Add-ons, or Packages. Decide whether the buyer should pay on the page.
Taking a request for work? Use an Itemized Work Request for a known menu of services, or a Free-Form Work Request for an open brief. Decide which work or billing record the request should create.
Receiving a question or collecting a standalone response? A Support Form is designed for Tickets. A General Form collects submissions without associating them with a Contact or Company. A Subscriber Form is designed for Email Marketing Audiences.
Before sharing any Form, submit it yourself as the intended user would. Check the public or authenticated access, the field conditions, the submission record, and any configured follow-up action.
Frequently asked questions
Can I put a SuiteDash Form on my website?
Yes. Kickoff Forms can be shared by a public link or embedded on a website. Checkout and Support Forms also offer external sharing or embed options. An Update Form is different: it is for an authenticated, known Contact and cannot be published as an anonymous public Form.
Will every submission create a Contact?
No. A Kickoff Form can add a Contact to CRM as configured. A General Form stores a submission without matching it to a Contact or Company. An Update Form changes an existing Contact’s data. Choose the Form type according to the record you want the answer to affect.
Can a Form change based on an answer?
Yes. Conditional Logic can show or hide fields, and it can control an appointment block. The available conditions depend on the field type. Test each path before sending the Form to Clients.
Can Clients request work through a Form?
Yes. Work Request Forms offer Itemized and Free-Form paths. They collect a guided request and can be configured to move the submission into an Invoice, Estimate, Project, or Task.
Where does the team find submitted answers?
Open the Form’s submissions in the Forms area. Submissions associated with a Contact can also be viewed from that Contact’s dashboard.
Explore Forms in the connected Platform
See the Forms feature page for the visual overview. Then explore how a submission can feed Client Onboarding, Work Requests, Support Tickets, and Automations.
