Core Automations

Learn from proven automation examples that handle the most common conversation scenarios effectively.

Learning Resources

Quick Reference - Looking for automation examples? Check out the core automations we use below.

What are the main automations we use?

These are the core automations that handle the most common scenarios in automotive lead management:

Active Automations:

Strict DNC Opt Out: Handles strict opt-out requests (Active)

Pipeline Management (Not Configured):

Engaged | Intent To Buy: Moves interested customers forward (Disabled)
Wrong Phone Number | Old Data: Handles wrong number situations for old data
Wrong Phone Number | Paid Leads: Handles wrong number situations for paid leads
Call Request: Handles customer requests for phone calls
Permission to Pull Credit | Ready To Submit: Manages credit permission process

Protection & Compliance (Not Configured):

Hate Speech or Abuse Detection: Detects abusive language
Do Not Qualify - Age (Under 18): Handles underage contacts
Not Interested | 3 Attempts: Manages disinterested leads after referral bonus
Human Assistance Needed: Routes complex inquiries to human agents

Wrong Phone Number Automation

When to use: When your agent reaches someone who isn’t the intended client.

Name: Wrong Phone Number

Description: Detects when the agent sends a wrong-number rebuttal message → Turns Auto Pilot OFF → Moves to “Wrong Number” status in the pipeline.

Event Logic:

ONLY monitor the LAST message in the conversation. Do not trigger on any
other messages that is not the LAST agent message.

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

THIS IS THE EXACT TARGET MESSAGE (must be the LAST agent message):
"My apologies. What's your name? I was reaching out to a past client about
our new exclusive low interest rate program, which is transferable to new
clients. Would you be interested if I showed you some low rate options?"

IMPORTANT:
- If there is any message after this target message in the context or the
  client has mentioned intent to proceed, do not trigger
- NO other message can trigger this event

Actions:

Disable Auto Pilot
Move status to Wrong Number

Engaged | Intent to Buy Automation

When to use: When a customer shows clear buying signals and engagement.

Name: Engaged Intent to Buy

Description: Client has shown engagement → Turns Auto Pilot ON → Moves client to Engaged stage of the pipeline (Currently Disabled)

Event Logic:

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

Trigger the event only if the client's message contains clear buying signals.
Examples of genuine engagement include:
- "Cars" "Trucks" "SUVs" Or "Cars or SUVs" "Trucks or SUVs"
- "I'm interested"
- "Tell me more"
- "What do you have?"
- "Show me what you got"
- "I need a [vehicle type]"
- "Looking for a [specific vehicle]"
- "Do you have [specific make/model]?"
- "I want to see [vehicle type]"
- "When can I come in?"
- "I want to trade my [vehicle]"
- "Yes" / "Sure" / "Okay" / "Yeah" (ONLY as first response to initial Opening Message)

DO NOT trigger the event if the client's response is negative, just providing
information, or not showing buying intent. Examples of non-engagement responses include:
- "No" / "No thanks" / "No thank you"
- "I just bought a [vehicle] I'm good"
- "I don't want to trade my vehicle"
- "I'm ok" / "I'm good"
- "I pay [amount] for my [vehicle]" (just stating current situation)
- "I don't have any payments now"
- "10-4" / "Sure" / "Yes it does" (acknowledgments without buying context)
- "Not even a little bit actually"
- "Not right now" / "Maybe later"
- Identity questions like "Who is this?"
- Wrong number claims

IMPORTANT:
- Only trigger when customer shows clear intent to purchase or get specific vehicle information
- Do not trigger on acknowledgments, current vehicle info, or polite declines
- "Yes/Sure/Okay" only triggers if it's the first response to initial vehicle offer

Conditions:

Source status in: New Contact, Wrong Number, Needs a Call, Not Interested

Actions:

Enable Auto Pilot
Move status to Engaged

Permission to Pull Credit | Ready To Submit

When to use: When a customer gives permission to proceed with credit check.

Purpose: Captures when client gives permission to proceed and pull credit.

Actions:

Turns Auto Pilot OFF
Moves to “Permission To Pull Credit” stage

Call Request

When to use: When a customer asks to speak with someone on the phone.

Purpose: Handles customers who want direct phone contact.

Actions:

Turns Auto Pilot OFF
Sends confirmation message
Moves to “Needs A Call” stage

Hate Speech or Abuse Detection

When to use: When customers use abusive or inappropriate language.

Purpose: Automatically handles abusive language situations.

Actions:

Turns Auto Pilot OFF
Moves to “DNC” (Do Not Contact) status

Not Interested | 3 Attempts

When to use: After multiple attempts when customer shows clear disinterest.

Purpose: Handles customers who remain uninterested after referral bonus message.

Actions:

Turns Auto Pilot OFF
Moves to “Not Interested” stage

Do Not Qualify — Age (<18)

When to use: When a contact reveals they are under 18 years old.

Purpose: Handles underage contacts who cannot legally enter into contracts.

Actions:

Turns Auto Pilot OFF
Moves to “DNC” status

Strict DNC Opt Out

When to use: When customers use strict opt-out language like “STOP”.

Purpose: Handles strict opt-out phrasing and compliance requirements.

Actions:

Turns Auto Pilot OFF
Moves to “Not Interested” stage

These core automations handle the most common scenarios you’ll encounter. Use them as templates for creating your own automations, and always test thoroughly before going live. Next, learn how to properly test your automations in Testing.