Overview #
Agent Editor is the control center where you design how an Agent behaves from start to finish.
It combines journey structure, visual setup, matching logic, completion behavior, and operational settings in one place.
What you can do in Agent Editor #
- Define the Agent identity and purpose
- Build the journey flow using Paths, Gates, and Steps
- Configure appearance and messaging
- Set timeout and completion behavior
- Configure candidate-facing chat behavior
- Import or export full Agent configuration
Main areas inside the editor #
Journey Structure #
This is where you map candidate progression:
- Path entry logic
- Step sequence
- Branching decisions (through Gates)
- Outcomes and completion states
Candidate Experience #
You control how the Agent looks and feels:
- Header branding
- Primary/secondary texts
- Chat label and conversational affordances
- Completion page messaging
Operational Controls #
These settings affect reliability and behavior:
- Timeout rules
- Completion triggers
- Export/import portability
- Reusability across brands or environments
Best practices #
Start from business intent #
Before adding steps, define:
- What decision this Agent should produce
- What candidate data is required
- What "complete" means for your process
Keep journeys compact #
Avoid over-long paths.
Break complex logic into clear gates and outcomes so troubleshooting is easier.
Separate content from logic #
Use widgets for candidate-facing content, and keep routing decisions in gates/outcomes logic for better maintenance.
Common mistakes to avoid #
- Building too many steps before defining outcomes
- Mixing branding edits with logic changes in one release
- Setting timeout without deciding resumption behavior
- Exporting without documenting dependencies (e.g., integrations, merge fields)
Related pages #
- Compatibility Match
- Path Steps
- Path Outcomes
- Journey Completion
- Import & Export Agent