Skip to content
Automotive AI Automotive AI AAI Documentation

Event Logic

Learn how to create precise event logic that triggers your automations at exactly the right moments.

Learning Resources

Section titled “Learning Resources”

Quick Reference Need help with event logic? Follow the guidelines below.

What is event logic?

Section titled “What is event logic?”

Event logic is the detailed description that tells your automation exactly when to trigger. It’s like giving very specific instructions about what to look for in conversations.

How do inbound vs outbound triggers work?

Section titled “How do inbound vs outbound triggers work?”

Inbound Triggers (Customer Messages):

  • Monitor what customers say
  • Trigger immediately when customer sends matching message
  • Use when you need instant reaction to customer phrases
  • Example: Customer says “I want to buy” → Move to engaged stage

Outbound Triggers (Agent Messages):

  • Monitor what your agent says
  • Trigger when agent sends specific types of messages
  • More reliable and precise
  • Example: Agent sends wrong number recovery message → Turn off Auto Pilot

How do I write good event descriptions?

Section titled “How do I write good event descriptions?”

Be Very Specific: Write exactly what should happen, including specific phrases and words to look for.

Use This Format:

  1. What to monitor: Describe what type of message to watch for
  2. Specific phrases: List exact words or phrases that should trigger
  3. Examples that SHOULD trigger: Give clear positive examples
  4. Examples that should NOT trigger: Give clear negative examples

Example Event Logic:

Monitor the conversation for when the client shows clear buying intent.


ONLY trigger on CLIENT messages containing:
- "I'm interested"
- "Tell me more"
- "What do you have?"
- "Show me what you got"
- "I need a [vehicle type]"


DO NOT trigger on:
- "No thanks"
- "I'm good"
- "Not right now"
- "Who is this?"

What are the key rules for event logic?

Section titled “What are the key rules for event logic?”

Message Direction:

  • Always specify if you’re monitoring CLIENT or AGENT messages
  • Don’t mix them in the same automation

Phrase Matching:

  • Use exact phrases when possible
  • Allow for extra words around key phrases

Context Matters:

  • Consider the conversation stage
  • Think about what happened before this message
  • Account for different ways customers might say the same thing

How do I handle complex conditions?

Section titled “How do I handle complex conditions?”

Multiple Requirements (AND logic):

ONLY trigger when the agent's message contains ALL of these phrases:
- "My apologies. What's your name?"
- "I was reaching out to a past client"
- "transferable to new clients"

Alternative Options (OR logic):

Trigger when client mentions any of these vehicle types:
- "Cars" OR "Trucks" OR "SUVs"
- "Cars or SUVs" OR "Trucks or SUVs"

What are field conditions?

Section titled “What are field conditions?”

Field conditions add extra requirements beyond the message content.

Common Field Conditions:

  • Source Status: Only trigger if contact is in specific pipeline stages
  • Lead Source: Only apply to certain types of leads
  • Contact Age: Only trigger for new or old contacts
  • Previous Actions: Check if other automations have already fired

Example:

Conditions:
- Source status in: New Contact, Wrong Number, Needs a Call
- Lead source is not "Referral"
- Contact created within last 30 days

How do I avoid conflicts between automations?

Section titled “How do I avoid conflicts between automations?”

Stage Conflicts:

  • Don’t have multiple automations that move contacts from the same stage
  • Make sure automations work in sequence, not against each other

Message Direction:

  • Avoid having inbound and outbound automations that could fire at the same time
  • Space out timing if both are needed

Action Conflicts:

  • Don’t have automations that turn Auto Pilot on and off simultaneously
  • Make sure status changes make logical sense

What makes event logic precise?

Section titled “What makes event logic precise?”

Good Event Logic:

  • Uses specific phrases
  • Gives clear examples
  • Handles edge cases
  • Considers context
  • Avoids false positives

Poor Event Logic:

  • Too vague or general
  • Missing examples
  • Doesn’t handle exceptions
  • Ignores context
  • Creates conflicts

Example of Precise Logic:

ONLY monitor the LAST message in the conversation. Only trigger on a CLIENT message. Never trigger from an AGENT message.


Trigger only if the client's message contains clear buying signals:
- "I'm interested" / "Tell me more" / "What do you have?"
- "I need a [vehicle type]" / "Looking for a [specific vehicle]"
- "Yes" / "Sure" / "Okay" (ONLY as first response to initial offer)


DO NOT trigger if response is:
- "No" / "No thanks" / "I'm good"
- "Not right now" / "Maybe later"
- Just providing information without buying intent

Good event logic is the key to reliable automations. Take time to be specific and test thoroughly. Next, check out Core Automations to see examples of well-written event logic in action.