Field-based builder
Collect different kinds of information with configurable fields.
AMS · Connected business workflows
Forms — Ask clearly. Start with context.
Collect enquiries and structured responses in a form built around what your team needs to know.
Who this helps
Teams collecting enquiries or structured requests from people outside the workspace.
The situation
A request arrives without a contact address or enough detail, so the team has to chase the missing information.
Fictional example: Lina submits her name, email and an autumn collection project brief. This website example makes no live changes.
Follow the example, step by step
Ask for the essentials
- What you do
- Define required fields for a name, email address and project brief.
- What changes
- The field structure makes each requested piece of information explicit.
- Why it helps
- The form sets expectations before anyone submits a request.
Identify the person asking
- What you do
- Enter Lina Hassan in the name field.
- What changes
- The visitor’s name appears in the enquiry.
- Why it helps
- The team knows whose request it is reviewing.
Include a way to reply
- What you do
- Enter the contact email before completing the brief.
- What changes
- The contact address sits beside the visitor’s name.
- Why it helps
- The team does not have to ask a second time for contact details.
Explain the request
- What you do
- Describe the autumn collection launch in the project field.
- What changes
- The completed fields bring the person and the proposed work together.
- Why it helps
- The recipient has a concrete starting point for assessing the enquiry.
Review one complete response
- What you do
- Submit the completed enquiry and review the resulting response record.
- What changes
- The sample changes to Received with Lina’s name and project details.
- Why it helps
- A teammate can assess the request before choosing what happens next.
What your team gains
The team receives one response containing the information needed to assess the request and reply.
Give people a clear way to respond and give your team a consistent starting point.
Inside Forms
Validation
Mark required information and use field validation to make responses more useful.
Shareable forms
Choose a public or controlled sharing route appropriate to the form.
Response records
Keep submissions together so the next person can find the original request.
Landing page context
Place an enquiry alongside the explanation of an offer or campaign.
Lead creation
Map a form into lead creation when configured and the leads module is enabled.
Questions and requirements
Does a response automatically become a project?
No. The response is its own record. Your team decides whether to create planned work; lead creation requires the relevant configuration and field mapping.
Can I use this for requests unrelated to clients?
Yes. Choose fields that suit the information you need. Publishing, form access and response visibility follow the form’s settings and your permissions.
Requirements and limits
Lead creation is configurable; every form does not automatically create a project or lead. Sharing and response access depend on the form settings.
Understand the next tool here
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Landing pages — read how it fits
Provide context for a request on a page, then deliberately connect its call to action to the appropriate form.
Build a focused page for an offer, launch or enquiry inside your workspace.
Fictional example: Forma’s collection page moves from an opening message to product details and a discovery button.
Before you use it
Publishing, domains and page access depend on workspace configuration. The example page and business are fictional.
Optional: explore the full Landing pages story ↗Projects & tasks — read how it fits
Turn an accepted request into planned work when your team decides to proceed.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Before you use it
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗