Best Practices

Learn proven best practices for creating automations that work reliably and improve your team’s efficiency.

Learning Resources

Quick Reference - Want to create better automations? Follow the best practices below.

How do I create effective automations?

Start Simple:

Begin with one clear, common scenario
Use specific, well-defined trigger conditions
Test thoroughly before adding complexity
Build on successful automations gradually

Be Specific:

Write detailed event logic with clear examples
Include both positive and negative examples
Use exact phrases when possible
Account for common variations in customer language

Plan the Flow:

Think through the entire customer journey
Ensure automations work in logical sequence
Avoid creating conflicts between different automations
Consider what happens after each automation triggers

What makes event logic reliable?

Good Event Logic:

Uses specific trigger phrases
Includes clear examples of what should and shouldn’t trigger
Handles common variations and edge cases
Considers conversation context
Avoids false positives

Example of Good Logic:

ONLY trigger when client shows clear buying intent:
- "I'm interested" / "Tell me more" / "What do you have?"
- "I need a [vehicle type]" / "Looking for a [specific vehicle]"

DO NOT trigger on:
- "No thanks" / "I'm good" / "Not right now"
- Questions about identity: "Who is this?"
- Just providing information without buying intent

How do I avoid automation conflicts?

Pipeline Stage Management:

Don’t have multiple automations moving contacts from the same stage
Ensure stage transitions follow logical progression
Use appropriate stage restrictions for each automation

Trigger Direction:

Avoid having inbound and outbound automations that could fire simultaneously
Use outbound triggers for higher precision when possible
Space out timing if both trigger types are needed

Auto Pilot Control:

Don’t have automations that turn Auto Pilot on and off at the same time
Consider the customer experience when changing Auto Pilot state
Make sure Auto Pilot changes make sense for each scenario

What are the performance best practices?

Max Transition Limits:

Default to “once per contact” for most automations
Only use “multiple times” when specifically needed
Prevent loops by limiting how often automations can trigger

Trigger Timing:

Use outbound triggers for better precision and timing
Consider when in the conversation the automation should fire
Account for message processing delays

Action Efficiency:

Combine related actions in single automations when possible
Avoid unnecessary status changes or field updates
Keep actions focused and purposeful

How do I maintain automation quality?

Regular Review:

Monitor automation performance regularly
Check for unexpected triggers or failures
Update event logic based on real conversation patterns
Remove or modify automations that aren’t working well

Documentation:

Keep clear descriptions of what each automation does
Document any changes made and why
Share successful automation patterns with your team
Maintain examples of good and bad trigger scenarios

Testing:

Test all changes before going live
Create test scenarios for edge cases
Monitor new automations closely at first
Get feedback from team members using the automations

What should I monitor after going live?

Performance Metrics:

How often automations trigger (too much or too little?)
Accuracy of triggers (false positives or missed triggers?)
Customer experience impact (smooth or disruptive?)
Team workflow improvement (helping or hindering?)

Warning Signs:

Automations triggering unexpectedly
Customers getting confused by status changes
Team members reporting automation issues
Pipeline stages getting cluttered or illogical

Success Indicators:

Consistent, appropriate triggering
Smooth customer experience
Improved team efficiency
Reduced manual pipeline management

How do I scale automation usage?

Start Small:

Begin with 2-3 core automations
Perfect these before adding more
Focus on highest-impact scenarios first
Build team confidence with early wins

Expand Gradually:

Add new automations one at a time
Test each addition thoroughly
Train team on new automation behavior
Monitor for conflicts with existing automations

Team Training:

Ensure team understands what each automation does
Train on when to expect automation triggers
Provide guidelines for when to override automation actions
Create documentation for new team members

What are common pitfalls to avoid?

Over-Automation:

Don’t automate everything at once
Leave room for human judgment and intervention
Avoid automations that remove necessary human touch
Keep customer experience personal and authentic

Under-Testing:

Don’t skip testing phases
Test edge cases, not just happy paths
Get multiple people to test before going live
Monitor closely after launch

Poor Event Logic:

Avoid vague or overly broad trigger conditions
Don’t ignore negative examples and exclusions
Account for real customer language variations
Consider conversation context and timing

What makes an automation successful?

Customer Experience:

Feels natural and helpful, not robotic
Responds appropriately to customer intent
Doesn’t create confusion or frustration
Maintains personal touch when needed

Team Efficiency:

Reduces repetitive manual tasks
Improves response consistency
Helps with pipeline management
Provides clear, actionable results

Technical Reliability:

Triggers consistently when intended
Doesn’t create false positives
Works well with other automations
Handles edge cases gracefully

Business Impact:

Improves lead conversion rates
Reduces response times
Increases team productivity
Enhances overall customer satisfaction

Effective automations balance efficiency with customer experience. Focus on creating reliable, helpful automations that enhance rather than replace human interaction. Start simple, test thoroughly, and improve gradually based on real-world performance.