Skip to main content
This workflow confirms successful purchase events and reassures users with clear transactional details. MailerPath runs the workflow engine and reliability controls for you. You can customize approved timing/priority settings and message templates.

​
Definition and business outcome

Use this workflow to build trust after a transaction and reduce post-purchase uncertainty. Primary outcomes:
  • Users receive immediate purchase confirmation.
  • Support tickets for order uncertainty are reduced.
  • Follow-up lifecycle workflows have cleaner handoff.

​
Entry criteria

Trigger event:
  • Purchase completion (including subscription purchase where applicable).
Required conditions:
  • Valid recipient email.
  • Successful payment state.
Recommended send window:
  • Immediate.

​
Exit criteria

Complete when:
  • Confirmation message delivered.
Cancel when:
  • Transaction state is reversed before send.
  • Recipient is no longer reachable.

​
Suppression and conflict rules

  • Prevent duplicate order confirmations per transaction ID.
  • Prioritize transactional sends in queue.
  • MailerPath conflict controls remain system-managed.

​
Required configuration fields

Client-configurable fields:
  • delay_minutes (typically 0)
  • send_time_mode (typically immediate)
  • priority_score
  • Template customization for receipt/order details
Minimum data:
  • Order ID
  • Payment status
  • Items and totals
  • Recipient email

​
Message blueprint

  1. Purchase confirmation and thank-you.
  2. Order summary (items, amount, payment).
  3. Delivery/subscription next steps.
  4. Support contact path.
CTA examples:
  • View your order
  • Manage your subscription

​
Launch checklist

  1. Validate idempotency by transaction ID.
  2. Test with successful and failed payment states.
  3. Confirm order detail token rendering.

​
Metrics and thresholds

  • Delivery success target: 99%+
  • Duplicate-send rate target: near 0%
  • Order-related support ticket reduction trend

​
Failure scenarios and fixes

  • Duplicate confirmations: enforce transaction-level dedup.
  • Missing order details: validate payload mapping before send.

​
Workflow group and source

Workflow group:
  • Transactional and purchase
Source reference:
  • docs/workflow/MailerPath Workflow Details.md