Skip to main content

Communication Hub

Unified messaging, notes & notifications · loading...

What's real now: Internal notes, @mentions, logs and automation tools are live in Firestore. Automated messaging now uses the backend queue and Firebase Functions. WhatsApp API and Brevo still need provider credentials to deliver automatically, but the product-launch, lifecycle queueing and template seeding controls are available here.

Messages by Channel

Communication Activity (14 days)

Fresh Launch Subscribers

loading...
Select a conversation

Pick a customer to view the conversation

Internal Team Notes

Direct Message

WhatsApp
Email
SMS
Select a saved customer to personalize {name} automatically.

AI Revenue Opportunities

Recommendation-only, admin approved

Retention Watchlist

High-value follow-up focus

Communication Policy Summary

Trust and cost controls

Journey Performance Summary

Inferred revenue from recent sends

Automation Tools

Backend controls kept below the primary action area
Lifecycle engineOrder, refund, Seeds, referral, membership, reorder and review flows are backend-driven.
Template storeSeed the `notification_templates` collection from here.
Product launchSeparate intentional trigger only. Product create/edit does not auto-broadcast.
Ready. Use Product Launch Notification above for announcements, and keep these controls as admin tools below.

Customer Journey Matrix

Full launch communication map
Stage 1

Acquisition and Referral

Entry-point communication from referral discovery to signup welcome and reward confirmation.

  • Referral link click or referred signup welcome
  • New customer account welcome
  • Referral reward earned after first valid delivered order
  • Separate referral reward notice for referrer and referee
Stage 2

Browse to Checkout

Conversion nudges while keeping frequency controlled.

  • Cart abandonment after 4 hours inactivity
  • Single reminder only in initial launch mode
  • Coupon success stays on-site and does not trigger outbound messaging
  • No multi-nudge sequence until conversion data proves the need
Stage 3

Order Placed to Delivered

Core transactional journey for every real order.

  • Order placed
  • Confirmed
  • Processing
  • Shipped with tracking
  • Delivered
  • Review request as a separate delayed message
Stage 4

Payment and Refund

Payment confidence, COD acknowledgment and refund clarity.

  • Successful online payment acknowledgment
  • COD delivered and paid acknowledgment
  • Refund processed confirmation
  • Payment receipt path available if finance wants explicit receipt messaging
Stage 5

Loyalty, Membership and Retention

Ongoing retention flows after first purchase.

  • Membership purchase welcome
  • Membership expiring in 7 days
  • Membership expired
  • Reorder reminder
  • Seeds earned and redeemed milestone communication
Product Launch

Intentional Product Announcement

Handled separately so normal product edits never broadcast to customers by mistake.

  • Product launch is triggered only from the dedicated panel above
  • Announcement summary is curated per product
  • No auto-send on add, edit, price change or stock change
  • Designed for campaign-style release moments

Recommended Launch Channels

Expanded from the audit screenshot

Use this standard unless business overrides it. Before WhatsApp API goes live, email carries the transactional load. Once WhatsApp is approved, enable dual-path for critical events.

EventPrimaryFallbackPriority
Order placedEmailWhatsAppCritical
Order confirmedEmailWhatsAppCritical
Order processingEmailWhatsAppHigh
Order shippedEmailWhatsAppCritical
Order deliveredEmailWhatsAppHigh
Order cancelledEmailWhatsAppCritical
Refund processedEmailWhatsAppCritical
Membership expiring soonWhatsAppEmailHigh
Membership expiredWhatsAppEmailHigh
Abandoned cartWhatsAppEmailMedium
Reorder reminderWhatsAppEmailMedium
Referral reward earnedWhatsAppEmailMedium
Review requestWhatsAppEmailLow

Launch Notes

Operational guidance for the team
Referral: now treated as a real customer-facing flow and no longer deferred in the hub presentation.
Review request: shown as a separate journey event instead of hiding inside delivered messaging.
Membership: includes welcome, 7-day reminder and expired-state communication.
Seeds: shown as a launch-visible milestone flow, not buried as a later phase note.
Product launch: remains intentionally separate because sending on every product edit is not logical.

Communication Logs

Queued & sent messages
ChannelToMessageStatusWhen

Campaign History

Broadcast-level audit trail
HeadlineAudienceQueuedDedupedChannelsStatusWhen