Skip to content
Vishwa Raj logoVishwa Raj
Back to projects
Kalkine: Unified Multi-Channel Communication Platform

Case study

Kalkine: Unified Multi-Channel Communication Platform

Designing and shipping a unified orchestration layer for Email, WhatsApp, In-app, Push and SMS—so users get timely, personalized market updates with measurable activation and retention impact.

FintechLifecycleMessagingProduct strategy

Outcome focus: user trust and decision speed

Risk reduced: costly roadmap drift

Reusable assets: sequence, scoring, and instrumentation

TL;DR

Kalkine had fragmented messaging across Email, WhatsApp and in-app. I led the product strategy and delivery of a unified communication platform that standardized segmentation, triggers, measurement and governance—so messages were timely, relevant and compliant.

This case study is written from a Product Manager perspective and uses assumptions where exact numbers were not available for publication.

Multi-channel communication highlights

1) Context

Why this mattered

In investing products, communication is the product: users act on alerts, insights and nudges. Fragmented tooling caused inconsistency (and noise), which reduced trust and engagement.

Users

  • Trial – Active: exploring features, setting watchlists, sampling insights
  • Trial – Passive: browsing content, low-frequency engagement
  • Paid – Low use: at-risk renewal segment
  • Returning users: previously churned or dormant

Core user job-to-be-done

“Keep me updated on market events and my portfolio without spamming me—and make it easy to act.”

2) The problem

Symptoms

  • Users got duplicate or irrelevant notifications across channels.
  • Teams ran manual campaigns with limited trigger logic.
  • Measurement focused on opens/clicks, not user actions.
  • WhatsApp consent flows were leaky and under-instrumented.
  • Governance was unclear (ownership, frequency, escalation, suppression rules).

Root causes

  • No shared segmentation schema.
  • No unified trigger engine / orchestration layer.
  • No consistent event taxonomy and KPI dashboarding.
  • No guardrails for over-messaging.

3) Objectives & success criteria

Objective

Build a unified, measurable, and compliant communication system that:

  • Moves from fragmented tools → one integrated platform
  • Improves Day-7 Activation and Last Meaningful Action (LMA)
  • Enables multi-channel orchestration with governance + audit trails

Success criteria (targets)

  • Day-7 activation improves by +10pp within 6 months [assumption]
  • WhatsApp consent drop-offs reduced by 30% within 6 months [assumption]
  • Unified dashboards live for 100% of campaigns by Jan 2026 [assumption]
  • NRR maintained >100% across 2026 [assumption]

4) Scope

In-scope (Phase 1)

  • Channels: Email, WhatsApp, In-app, Push, SMS
  • Journeys: Onboarding, Activation, Retention, Renewal, Win-back
  • Measurement: end-to-end (from send → click → action) with cohort views
  • Governance: ownership mapping, escalation triggers, suppression/fatigue rules
  • Compliance: consent-first journeys + audit logs (GDPR/CCPA/AU) [assumption]

Out-of-scope (Phase 1)

  • Full AI automation (planned Phase 4) [assumption]
  • Browser push at scale (considered Phase 5) [assumption]
  • Advanced personalization beyond rule-based (Phase 4+) [assumption]

5) Research & insights

What we did

  • Behavior analysis: identify what users actually engage with (alerts vs long-form)
  • Feedback collection: support tickets + targeted interviews
  • Journey mapping: Trial → Paid and renewal cohorts
  • Pain-point identification: where messages created confusion or missed critical updates

Key insights

  1. Users preferred fewer, higher-signal alerts with clear “why it matters”.
  2. Personalization mattered more than frequency—users tolerated more when relevance was high.
  3. Consent friction (WhatsApp) was a major loss point and needed UX + tracking upgrades.
  4. Teams needed an operating system (ownership + escalation), not just templates.

6) Solution framework (product + system design)

6.1 Unified communication system

  • One orchestration layer connecting Email/WhatsApp/Push/In-app
  • Shared triggers + shared segments
  • Unified dashboard for actions and outcomes

6.2 Segmentation

  • Trial active / trial passive / paid low use / returning
  • Behavior rules: report download, alert set, screener usage, portfolio events

6.3 Triggers (examples)

  • Day-3: “No LMA yet” reminder (nudge to set watchlist/alerts)
  • Day-7: activation checkpoint (prompt to configure preferences)
  • Renewal stage: usage-based win-back drip with suppression rules

6.4 Governance

  • Ownership table: each KPI has an owner, review frequency and escalation trigger
  • Escalation logic examples:
    • Activation drop >3% → audit journey
    • Engagement <75% → refresh messaging / targeting

6.5 Compliance (assumptions)

  • Consent-first flows, especially for WhatsApp
  • Opt-in audit logs
  • Region-based policies (GDPR/CCPA/AU)

7) Functional requirements (what we shipped)

Preference-based notification settings

  • Users select channels (Email/In-app/Push/WhatsApp/SMS)
  • Users select alert types (price, volume, earnings, news)
  • Users set frequency caps (daily/real-time) and quiet hours [assumption]

Automated alert generation

Supported triggers like:

  1. New reports / recommendations published
  2. Stock achievements and watchlist changes
  3. Price targets hit
  4. Volume spike alerts
  5. Earnings report alerts
  6. Portfolio performance alerts [assumption]
  7. Market news / theme alerts [assumption]
  8. Dividend alerts [assumption]

Dispatch + reliability

  • Multi-channel dispatch with fallback rules (e.g., push → email) [assumption]
  • Scalable architecture to handle spikes (earnings, high-volatility days)

8) Measurement (KPIs)

| Metric | Definition | Owner | Frequency | Escalation | |---|---|---|---|---| | Day-7 Activation | % users with ≥1 LMA in 7 days | Growth Lead | Weekly | Drop >3% → audit | | Engagement | % users active on ≥1 channel weekly | Product Ops | Monthly | <75% → refresh | | Consent drop-offs | % users lost in opt-in flows (WhatsApp) | Ops Lead | Weekly | >5% → redesign | | NRR | Net revenue retention | Finance | Quarterly | <100% → win-back | | Cost-to-serve | Cost per user contact | Ops Strategy | Quarterly | Drift >10% → review |

Owner titles and thresholds are representative assumptions based on a typical lifecycle operating model.

9) Delivery plan (phased rollout)

Phase 1 — Foundation (Aug–Sep 2025) [assumption]

  • Map journeys + define KPI owners
  • Establish event taxonomy and consent tracking
  • Create initial segments + message templates

Phase 2 — Build & launch (Oct–Nov 2025) [assumption]

  • Deploy orchestration layer + triggers
  • Launch dashboards and alert preferences
  • Pilot with 10–20% traffic and strict suppression rules

Phase 3 — Adopt & improve (Dec 2025–Jan 2026) [assumption]

  • Expand lifecycle campaigns
  • Governance reviews + fatigue suppression tuning

Phase 4 — Scale & optimize (Feb–Apr 2026) [assumption]

  • A/B testing at scale
  • Predictive nudges (ML-assisted) and next-best-action [assumption]

10) Outcomes & impact

Observed / directional impact

  • Increased engagement: +30% increase in DAU among the alert-engaged cohort [assumption]
  • Improved satisfaction: fewer complaints about irrelevant notifications [assumption]
  • Operational improvement: automation reduced manual support workload by ~40% [assumption]

Why I’m confident in these outcomes

The system reduced noise through segmentation + preference controls, and it improved measurement by tracking actions (not just opens). Even if the exact percentages vary, the directionality matches what we typically see when messaging becomes relevance-first.

11) What I’d do next

  • Add a feedback loop: user actions → refine rules and suppression
  • Expand alert types based on portfolio context (risk, holdings, time horizon)
  • Introduce “digest vs real-time” smart bundling
  • Build a creator workflow for analysts with approval and compliance checks