Understand automation dependencies
Keep lead forms, meeting types, categories, assignees, and suggested questions ready for active automations.
On this page
Forms, meeting types, categories, team members, and Suggested Questions can be reused across several visitor journeys. That reuse keeps configuration consistent, but it also means a change to one asset can affect an automation somewhere else in the project.
This reference helps you understand those relationships, read builder warnings, and make changes in a safe order. Use it whenever a working flow or Contact Option becomes unavailable after one of its supporting assets changes.
In this article, you'll learn:
- Which assets each automation feature requires
- How to use builder diagnostics
- How Zeltino protects Contact Option forms
- How to review dependencies after a change
Dependency map#
Use this table to find the asset or earlier step behind each visitor action:
| Automation feature | Required asset or earlier step | Ready state |
|---|---|---|
| Capture lead | Lead form | Form exists and is Active |
| Create ticket | Earlier lead form on every route | Active form captures Email before the ticket action |
| Book meeting in a flow | Meeting type | Public active one-to-one or group type, exactly one host, supported availability, and public booking enabled |
| Callback Contact Option | Lead form | Active form with required Phone |
| Schedule call Contact Option | Meeting type | Public active one-to-one type with exactly one host and supported availability |
| Inquiry Contact Option | Lead form | Active form with required Email |
| Assign category | Conversation category | Category exists and is enabled |
| Specific ticket assignment | Team member | Selected assignee remains active and available |
| Suggested question trigger | Suggested Question | Question remains saved and available |
Read builder diagnostics#
The Chat Flow builder checks dependencies while you work. It identifies missing, inactive, or incompatible forms, meeting types, categories, and assignees. It also checks required fields and verifies that every route into Create ticket has already captured email.
Select the affected block to see the warning in context. Repair the asset or choose another one, save again, and confirm the diagnostic clears. Do not activate a flow with unresolved warnings.
Protect Contact Option assets#
Enabled Callback and Inquiry options protect the required fields in their selected forms. Zeltino also prevents pausing or deleting a form that an enabled Contact Option uses. These safeguards keep an active visitor path from losing its required Phone or Email field unexpectedly.
When you need to change the form, select a ready replacement in Contact Options first. You can then return to the old form and pause, edit, or remove it without breaking the enabled option.
If a Contact Option shows Needs setup, Missing, Paused, Needs phone, Needs email, or Needs attention, follow the readiness detail and save after correcting it.
Maintenance checklist#
Treat a dependency change like a small release. Review the affected journeys before and after editing the shared asset:
- Review active Chat Flows and Contact Options after any asset change.
- Resolve warnings and readiness badges.
- Test every affected trigger and branch in the installed widget.
- Verify the team-side lead, booking, category, or ticket.
- Pause the automation if a required asset cannot be restored immediately.
For activation testing, see Test and activate a chat flow.