Build a form and connect it to your CRM
Last updated 3 August 2026

A form is the most common way a stranger becomes a record. Solstral forms write straight into your CRM, so a submission arrives as a real contact on a real timeline rather than an email you have to re-key.
1. Create the form
Open Forms and create one. Give it a name you will recognise later — "Contact us" and "Book a demo" behave very differently and you will want to tell them apart in reporting.
2. Add the fields
Add only what you genuinely need. Every extra field costs you completions, and you can enrich the record later. Name and email are usually enough to start a conversation.
Each field maps to an attribute on the object the form creates, so a value typed by a visitor lands in the same place as one typed by your team — and every view, filter and report understands it immediately.
3. Publish it
A form stays in draft until you publish. Publishing gives it a public address you can share directly, embed on your own site with a snippet, or drop into a page built with the website builder as a block.
4. Design what visitors see afterwards
The Thank you tab is a canvas exactly like the form itself: add a heading, a paragraph, rich text, an image or a divider, and that is what appears in place of the form once someone submits. It is worth more than a single line of thanks — tell people what happens next, point them at something useful, or confirm what they signed up for. If you would rather send visitors somewhere else entirely, switch the action to Redirect to a page and give it a URL.
5. Decide what happens on submission
This is the step people skip, and it is the one that matters. A form that only creates a record still leaves someone to notice it. Use the form submitted automation trigger to send an acknowledgement, assign an owner, create a follow-up task, or add the person to a marketing list — see Build your first flow.
6. Check it end to end
Submit the form yourself before you publicise it. Confirm the thank-you screen looks right, the record appears with the values in the right fields, the automation fired, and the acknowledgement actually arrived. A form quietly writing to the wrong field is the kind of fault that goes unnoticed for weeks.