Forms and touchpoints
A structured entry point for customers, prospects and participants.
How it fits together.
A touchpoint connects an external entry point with structured registrations and CRM context. The current creation form offers List, Form and Event. Its kind is fixed after creation, so begin with the intended workflow: collect information, maintain a list or manage event participants.
Fields selects required information and additional fields. Rules controls the destination contact type, lead status where applicable, responsibility assignment and participant limit. Email, Design and Permissions are configured separately. Depending on kind, the display contains registrations or participants and associated emails.
Step by step in AIOS
Create or open a Touchpoint object in its collection.
The current picker offers List, Form and Event. Decide before saving: an existing touchpoint’s kind is then fixed.
Choose its kind when creating it. Configure General, Fields, Rules, Email, Design and Permissions for your use case.
For an introductory-call form, select Email, First name and Last name as required fields and add a request field. Rules configures contact type, responsibility and, where applicable, lead status or participant limit.
Save the touchpoint. Its display lets you inspect registrations or participants and emails.
Check the entry point using fictional data and inspect the registration. Existing registration and email views show what the workflow produced.
Distribute access through the available sharing or publishing actions.
Review access, required information and configured email communication before distributing the link. General distinguishes invitation-only and open access.
AIOSAn example for your work.
Name: Request an introductory call
Kind: Form
Required information: Email, first name, last name
Additional field: What problem would you like to solve?
Example: mira@example.com / Mira / Example
Request: We want to standardize project handovers.
Responsibility: Select the intended support teamApply this plan in the form configuration. Use the sample data to review it and adapt required fields to your workflow.
Form configuration
| Area | Meaning in daily work |
|---|---|
| General | Name, kind at creation and offered access mode. |
| Fields | Required information and additional input fields. |
| Rules | Contact type, responsibility, optional lead status and participant limit. |
| Communication for the configured workflow. | |
| Registrations/participants | Resulting entries available for inspection in the display. |
If something does not work.
- The kind cannot be changed: It is fixed after creation. Select the required kind for a new touchpoint.
- Survey or Portal cannot be selected: These choices are disabled in the current creation picker; the documented workflow uses Form.
- The Form, Data or Seating tab has no content: Those display tabs are placeholders. Use configuration and registration/email views.