Skip to content

Autopilot Campaign Engine

Set-and-forget marketing automation with full auditability and attribution.

UC-MKT-006: Autopilot Triggers

Purpose: Manage lifecycle-based automated campaigns.

Property Value
Actor Business Owner
Trigger System Event (Lifecycle)
Priority P1

Capabilities Breakdown:

1. Trigger Management (UC 10.1, 10.2)

  • Trigger Listing: View all active automation rules (e.g., "Birthday Offer", "Follow-up after 30d").

  • Activation/Deactivation: One-click toggle to Pause/Resume a trigger.

  • Conflict Prevention: System warns if two triggers overlap (e.g., sending 2 offers same day).

2. Multi-Trigger Chaining (UC 10.7)

  • Logic: IF Booking Completed AND Service = Haircut THEN Wait 30 Days THEN Send Reminder.

  • Branching: IF Customer Clicks Link -> Notify Front Desk. ELSE -> Send SMS.

3. Revenue Attribution (UC 10.3)

  • Tracking: Links revenue back to the specific automated message.

  • Metric: "Autopilot generated $4,500 this month".

4. Audit Logs (UC 10.6)

  • Record: "User X paused 'Birthday Trigger' on [Date]".

  • History: View last 500 automated actions sent.

Main Success Scenario:

  1. Marketing Manager enables "Post-Visit Review" trigger.
  2. System waits for event:booking.completed.
  3. 24 hours later, System checks if review already received.
  4. If No, System sends WhatsApp: "How was your visit?".
  5. Dashboard records action in Audit Log.

Acceptance Criteria:

  1. [ ] Chained triggers execute in the correct sequence.
  2. [ ] Attribution logic correctly links revenue only if booking occurs < X days after message.
  3. [ ] Conflict detection prevents sending > 1 message per client per day.