Skip to main content

8. CRM, Customer Accounts & Loyalty

Purpose — A 360° view of each customer and their assets, the "My Products" self-service surface, and loyalty/rewards/affiliate programs whose value scales with purchase (notes #11).

Personas served​

Customer, Marketing admin, Service head, Manager (scoped), Dealer (own customers).

Key capabilities​

  • Customer 360 — every product owned, serials, warranties, AMCs, service history, invoices, documents (projection over commerce + warranty + FSM).
  • "My Products" portal/app — register product, raise complaint, track technician, download invoice/warranty, renew AMC, buy spares/accessories.
  • Loyalty / rewards — points that increase as purchase increases (tiered earn rates); redemption against purchases/service.
  • Affiliate — referral links + attribution + payouts.
  • Partner loyalty — shared engine with DMS for dealers/installers/electricians.
  • Segmentation & lifecycle marketing — renewals, cross-sell (battery → inverter owner), win-back; feeds Marketing + Newsletter.

Data owned​

Mongo (CRM): customer 360 projection, segments. Mongo (Loyalty): points ledger (non-financial), tiers, affiliate links/attribution. Financial payouts → Finance (PG). See dms-partners-loyalty.

Events​

  • Emits: points.accrued, points.redeemed, segment.changed, affiliate.conversion.
  • Consumes: order.placed/payment.captured (accrue), warranty.registered (bonus), installation.completed (engagement), customer.created.

APIs​

  • GET /me (360), GET /me/products, GET /me/loyalty, POST /loyalty/redeem
  • POST /affiliate/links, GET /affiliate/:code/stats
  • GET /crm/segments (admin, scoped)

Tenant-config knobs​

featureFlags.loyalty/affiliate; earn-rate tiers; redemption rules; affiliate commission; segment definitions.

Dependencies​

Warranty, FSM, Orders, Marketing, Finance.

Open questions​

  • Loyalty points financial liability treatment (with finance).
  • Affiliate fraud controls in v1?