From a3d59d8ea378eb69905e5771c07a2ba490fdc3dc Mon Sep 17 00:00:00 2001
From: Arnas Donauskas <arnas.donauskas@hostinger.com>
Date: Fri, 17 Apr 2026 21:42:20 +0300
Subject: [PATCH] fix(automations): Welcome Message template uses
 first_inbound_message
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The template seeded trigger_type as new_contact_created, which only
fires when the webhook auto-creates a contact row. A user who added
or imported the contact manually before the contact first messaged
would not hit the welcome flow — that's almost certainly not what the
user setting up "Welcome Message" wants.

first_inbound_message (added in PR #33) is the superset: fires the
first time any contact — auto-created or pre-existing — sends us a
customer message. Correct semantic for a welcome/greeting template.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 src/lib/automations/templates.ts | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/lib/automations/templates.ts b/src/lib/automations/templates.ts
index 8bb5bdd..5a4d260 100644
--- a/src/lib/automations/templates.ts
+++ b/src/lib/automations/templates.ts
@@ -33,7 +33,12 @@ export const AUTOMATION_TEMPLATES: Record<TemplateSlug, AutomationTemplateDefini
     slug: 'welcome_message',
     name: 'Welcome Message',
     description: 'Auto-reply to first-time contacts with a greeting.',
-    trigger_type: 'new_contact_created',
+    // first_inbound_message (added in PR #33) catches both brand-new
+    // contacts AND manually-added/imported contacts on their first-ever
+    // reply, which is what a user setting up a "welcome" automation
+    // almost always wants. new_contact_created would miss the
+    // manually-imported case.
+    trigger_type: 'first_inbound_message',
     trigger_config: {},
     steps: [
       {