Save vs Publish
Saving Your Work
Auto-Save
The Flow Builder automatically saves your changes:- Changes are debounced (2-second delay after last edit)
- Save status indicator shows current state
- Local backup stored in browser for recovery
Manual Save
Click Save in the toolbar or pressCtrl/Cmd + S to save immediately.
Save status indicators:
Activating Your Agent
Before Activation
Complete this checklist:1
Test thoroughly
Run multiple test calls and chats to verify behavior
2
Review flow
Ensure all nodes are connected and configured
3
Check voice
Verify voice settings sound professional
4
Validate KB
Confirm knowledge base is attached and current
5
Assign phone number
Connect a phone number to receive calls
Activating
- Click the Active toggle in the top toolbar
- Confirm activation in the dialog
- The agent is now live
Deactivating
To take an agent offline:- Click the Active toggle (switch off)
- Confirm deactivation
- The agent stops receiving calls
Agent States
Pre-Launch Checklist
Flow Validation
Flow Validation
- Start node is configured
- All paths lead to End Call or Transfer
- No orphaned nodes
- No validation errors (check for red indicators)
Content Quality
Content Quality
- System prompt is complete and accurate
- All conversation prompts reviewed
- Knowledge base content is current
- Pronunciation overrides added for tricky words
Testing Complete
Testing Complete
- Happy path tested multiple times
- Edge cases handled gracefully
- Human transfer works
- Error scenarios don’t break flow
Integration Ready
Integration Ready
- Phone number assigned
- Business hours configured (if applicable)
- Fallback messages set
- Team notified of go-live
Rollback
If issues occur after activation:- Immediate: Toggle agent to inactive
- Fix: Address the issue in the flow
- Restore: Use version history to revert if needed
- Reactivate: Turn agent back on after fix
Monitoring After Launch
After activation:- Watch Call History for incoming calls
- Review Analytics for performance metrics
- Check transcripts for quality issues
- Monitor for unexpected behavior
Best Practices
Soft Launch
Start with limited call volume to catch issues early.
Keep Backups
Create a version snapshot before major changes.
Monitor Closely
Watch the first few calls to ensure everything works.
Have Fallback
Ensure human transfer is always available as backup.
Related
Version History
Manage and restore versions
Phone Number
Assign phone numbers
Test Call
Final testing before launch