Skip to main content

Auto Comms

Event-Driven Notifications for Payments, Subscriptions, and Team Management

Example:

Payment Received

Multi-Invoice Payment

  • Channel: Email

  • Subject Line (if email): Payment Confirmed for {amount}

  • Recipient: Payer/customer

Payment-Plan Due/Charged

  • Channel: Email + SMS + Push

  • Subject Line (if email): Admin-configurable

  • Recipient: Payer/customer

  • Note: Only recipient of this message is the user who has a payment due.

Checkout/Order Complete

  • Channel: Email + SMS

  • Subject Line (if email): {Affiliation} Order #{id} / New {Affiliation} Order #{id}

  • Recipient: Customer (confirmation); merchant/registration inbox (receipt); affiliate partner (sale notice)

Lodging Order Placed

Stripe webhook mismatch

  • Channel: Email (internal)

  • Subject Line (if email): Stripe Payment Missing

  • Recipient: Internal admin

Chargeback/decline

  • Channel: Email

  • Subject Line (if email): Action Required: Updated Payment Information Needed

  • Recipient: Customer (cardholder)

Prepayment received

  • Channel: Email (internal)

  • Subject Line (if email): Prepayment Received for {Affiliation} Order #{id}

  • Recipient: Merchant/admin

Subscription cancelled

  • Channel: Email

  • Subject Line (if email): Subscription Cancelled: {Plan} / {Product} Cancellation: {athlete}

  • Recipient: Subscriber; admin/product-registration contact

  • Note: Subscription Cancelled: Rookie/All-Star/All-American

Subscription upgrade/downgrade

  • Channel: Email

  • Subject Line (if email): Subscription Upgraded: {Plan} / Subscription Change Scheduled: {Plan}

  • Recipient: Subscriber

Subscription renewal failure

  • Channel: Email (Internal)

  • Subject Line (if email): Payment Declined for Subscription #{id}

  • Recipient: Internal brand/admin

  • Notes:

    • Payment Declined for Subscription # 18058”

    • Internal email (PF), no traditional email sent

Password reset submitted

  • Channel: Email + SMS

  • Subject Line (if email): Password Reset!

  • Recipient: The account holder

OTP Requested (Login/Signup)

Roster Spot Created

  • Channel: Email

  • Subject Line (if email): Invite to Join {TeamCode}

  • Recipient: Invited player/parent

Coach/Manager Contact Added

  • Channel: Email

  • Subject Line (if email): Invite to {coach/manage} {TeamCode}

  • Recipient: Invited coach/manager

Registration Requiring Waiver

  • Channel: Email

  • Subject Line (if email): A Waiver is Required to Play

  • Recipient: Parent/athlete responsible for waiver

Waiver/Payment Change

  • Channel: Email

  • Subject Line (if email): {Team} Waiver and Verification [Reminder]

  • Recipient: Team contact/parent responsible for waiver or payment

Waiver Signed

  • Channel: Email

  • Subject Line (if email): {Athlete}'s Waiver

  • Recipient: Parent/athlete (confirmation)

Age Verification Submitted

  • Channel: Email

  • Subject Line (if email): Proof of Age Required / Confirmed / Denied

  • Recipient: Parent profile

Direct Message/Reply Sent

  • Channel: Email + Push

  • Subject Line (if email): None

  • Recipient: Message thread recipient (team member/contact)

Game Schedule Change/Add/Cancel

Game Finalized

  • Channel: Push

  • Subject Line (if email): None

  • Recipient: Team/division followers

Bracket/Round Advance

  • Channel: Push

  • Subject Line (if email): None

  • Recipient: Team/division followers

Bracket Seeded

  • Channel: Push

  • Subject Line (if email): None

  • Recipient: Team/division followers

Live Score/Goal Update

  • Channel: Push

  • Subject Line (if email): None

  • Recipient: Team/division followers

Tournament Broadcast Authored

  • Channel: Push

  • Subject Line (if email): None

  • Recipient: Division/team subscribers (admin-selected audience)

Scoring Conflict/Timeout

  • Channel: Email (internal)

  • Subject Line (if email): Scoring Conflict

  • Recipient: League admin

Flagged Survey Response Submitted

  • Channel: Email

  • Subject Line (if email): A {QuestionSet} Alert

  • Recipient: Configured alert-recipient staff

Vensure Sync Failure

  • Channel: Email (Internal)

  • Subject Line (if email): Vensure Failure

  • Recipient: Internal admin/HR-payroll staff

Did this answer your question?