Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Contact Created Trigger Block

The Contact Created trigger starts an automation when a new contact is added to your Patch database. This is best for first-touch workflows like SMS/email opt-ins, welcome campaigns, and new lead routing.

Contact Created Trigger Block

The Contact Created trigger starts an automation when a new contact is added to your Patch database. This is best for first-touch workflows like SMS/email opt-ins, welcome campaigns, and new lead routing.

What’s in This Article

 

 

What This Trigger Does

The Contact Created trigger fires when:

  1. A brand new contact record is created in Patch (from a form, purchase, integration, import or manual entry), and

  2. Patch sends the contact information into the automation

In simple terms:
“Run this automation the first time a new contact shows up in Patch.”

 

 

When to Use This Trigger

Use Contact Created when you want to:

  • Start a welcome campaign for brand-new contacts

  • Run an SMS/email opt-in flow when someone enters the database

  • Tag or route contacts based on how they were created (source, form, integration, etc.)

  • Set default values (example: lifecycle stage = Lead, tag = New Contact)

  • Send “Here’s what to do next” messages for new signups

 

 

When Not to Use This Trigger

Don’t use Contact Created if your message needs to be based on a specific action the contact took later.

Use these instead:

  • Check-In Finished → when someone visits / checks in

  • Order Finished → when someone buys (revenue + product data)

  • Calendar Event → when you need reminders before/after an appointment/booking

  • Contact Updated → when a field changes (like lifecycle stage, tags, opt-in status)

  • Membership Start/End → when membership status changes or a membership begins/ends

A simple rule:

  • Contact Created = “Who is new?”

  • Behavior triggers = “What did they do?”

 

 

Contact Created vs Behavior-Based Triggers

Contact Created is best for:

  • First-touch welcome messages

  • Confirming signup expectations (what they’ll receive and how often)

  • Opt-in flows (especially SMS compliance)

  • Default tagging and segmentation

Behavior-based blocks are best for:

  • Visits → Check-In Finished

  • Purchases → Order Finished

  • Bookings → Calendar Event

  • Profile changes → Contact Updated

  • Member lifecycle → Membership Start/End

Example:
If you want to send “Thanks for your purchase,” don’t use Contact Created—use Order Finished so you can reference what they bought and how much they spent.

 

 

Block Settings Explained

Details (Info Panel)

This section explains:

  • How the block is triggered

  • When to use this block

It’s informational only—no settings here change behavior.

Add Conditions

Use Add Conditions to control which new contacts can enter the automation.

Common examples:

  • Only run if Contact Source = “Website Form”

  • Only run if Email is known

  • Only run if SMS Phone is known

  • Only run if Tag includes “Lead”

  • Only run if Created By Integration = [name] (if available in your account)

Tip: Conditions help prevent internal/test contacts from getting messages.

 

 

Primary Automations Using Contact Created

1) SMS and Email Opt-Ins (Compliance-Friendly)

Use Contact Created to start an opt-in flow when someone is added to your database—especially when contacts are created from integrations.

Best practice approach:

  • Email: confirm what they signed up for and give a clear way to unsubscribe

  • SMS: don’t message until you have the right consent/opt-in captured

SMS compliance tips (Patch-specific)

  • Use the SMS Double Opt-In block and SMS opt-in wizard to collect and confirm consent the right way.

  • If you are not sure whether a contact has opted in, do not send promotional SMS yet. Route them through the opt-in flow first.

  • Include clear expectations in your opt-in message (what they’ll get + how often).

  • Always include opt-out language when required by your setup (example: “Reply STOP to opt out.”)

Common pattern:

  1. Contact Created

  2. If phone exists AND SMS consent is missing → start SMS double opt-in flow

  3. If email exists → send email “Welcome / confirm signup”

  4. Tag contact with “Opt-in Started” / “Opt-in Complete”

2) Welcome Campaigns

Welcome campaigns are usually your highest ROI automation because they hit at the moment of highest attention (right after signup).

Use Contact Created to:

  • Introduce your brand

  • Set expectations

  • Drive a first conversion (book, buy, visit, join)

Common welcome campaign goals:

  • Get a guest to book a visit

  • Get a lead to claim an intro offer

  • Get a new subscriber to set preferences (kids ages, interests, membership type, etc.)

  • Move people into the right segment (pickleball vs parties vs memberships)

 

 

What Data This Trigger Has Access To

Contact Created includes contact data (standard + custom fields), such as:

  • Name, email, phone

  • Some orders data - item names, total spent, and more (type "orders" into the filter to see all options)

  • Last Checkin Date
  • Is A Lead (yes/no)
  • RFM
  • Integration specific fields

  • Custom fields (source, interests, location, etc. if configured)

Unlike behavior triggers: 

  • It does not include booking start/end times (Calendar Event does)

  • Order or checkin frequency

 

 

Important Things to Know

  • Contact Created triggers when a record is added to Patch, not when they take future actions.

  • If you import contacts in bulk, this can trigger many automations at once—use conditions to control who qualifies.

  • For SMS: if consent is not confirmed, use the double opt-in block/wizard first before sending marketing texts.

  • Consider excluding staff/test contacts with conditions (email domain, tags, etc.).

 

 

Example Automations

Example 1: SMS Double Opt-In + Email Confirmation

  1. Trigger: Contact Created

  2. If phone exists AND SMS opt-in is not confirmed → run SMS Double Opt-In

  3. If email exists → send email: “You’re in! Here’s what you’ll get.”

Example 2: Simple Welcome Campaign (Email + SMS)

  1. Trigger: Contact Created

  2. Send email: “Welcome! Here’s how it works + top links”

  3. Delay: 1 day

  4. If SMS opted-in → send SMS: “Want 10% off your first booking? Reply YES.”

  5. Message Reply block -> Send discount code and redemption instructions

Example 3: Route New Contacts by Source

  1. Trigger: Contact Created

  2. If Source = Party Form → tag “Party Lead” and send party info

  3. If Source = Reservation Form → tag “Ree Lead” and send membership trial offer

  4. If Source = Import → do nothing (or tag only)

 

 

Best Practices

  • Use conditions to avoid messaging contacts who shouldn’t enter (imports, staff, tests).

  • Keep welcome messages short, clear, and focused on 1 next step.

  • For SMS, use Patch’s double opt-in tools when consent is missing or unclear.

  • If you need action-based messaging, choose a behavior trigger (check-ins, orders, calendar events).

  • Tag contacts early so future automations can segment correctly.