Forms & intake
Forms are a structured way to take requests in. A submitted form creates a ticket or a work item automatically, so intake flows straight into the queue your team already works.
What a form is
A form has a name, a public slug, and a target:
- Ticket — submissions open a support ticket (optionally on the customer portal).
- Task — submissions create a work item in a chosen project.
A form can be published (live) or a draft, and portal-enabled so it appears on your customer portal.
Fields and branching
Each form is built from fields. A field has a key, a label, a kind (text, textarea, select, checkbox, date, number, or email), and a required flag; select fields carry their options.
Forms support branching — show-if rules that reveal a field only when an earlier answer matches. This keeps forms short while still collecting the right detail for each kind of request.
On submit
When a form is submitted, ActionConnect:
- Records the submission (the full payload).
- Creates the configured ticket or task.
- Remembers which entity the submission created, so you can trace any item back to the intake that produced it.
A starter Contact Support form is seeded into every new organization so the portal has a working intake form on day one.
Tips
- Use branching to keep forms short and relevant.
- Send intake to a task form when requests should become project work, and a ticket form when they need a support response.
- Combine forms with Automations to route or triage new submissions the moment they arrive.