Skip to main content

Customer Segmentation

Dynamic, rule-based customer segmentation inside CDP — classify contacts into auto-updating groups from customer attributes and cross-module activity, reusable for targeting and campaigns. Today users export contacts to spreadsheets or apply static tags manually (hours/week, stale snapshots), so Broadcast recipients stay static and CRM data in CDP goes unused for audience selection. This initiative makes CDP a customer-intelligence layer and is the foundation for the 2026 personalization roadmap (signal scoring, loyalty, campaign intelligence).

Scope Changes​

Engineering surfaces this initiative touches (controlled vocab: Backend · Frontend · Mobile · Infra · Data · Design · Docs · None). Aggregate of this initiative's PRDs; mirrors the scope_changes frontmatter above.

  • Backend — contact-service: segment definition CRUD; rule/condition tree evaluation over customer fields + associations (Conversations, Campaigns, Company, Deals, Tickets); nightly batch evaluation + manual refresh (rate-limited); nested/exception filter logic; segment permission keys (customers_segment_view/add/manage/archived).
  • Frontend — qontak-customer-fe: Segment List, Segment Builder (condition/nested/exception/preview), Segment Detail (Overview + Performance), "Send campaign" entry, permission gating.
  • Data — segment evaluation query patterns over association tables; performance metrics (size growth, source/domicile/age/gender distribution); reachability-by-channel calculations.
  • Design — Figma for Segment List, Builder, Detail/Performance, campaign hand-off.

QA Lane​

Lane C — transition lane (between B and A). CRUD segmentation is automatable, but checking the segmentation data still needs manual testing due to a gap in the data-ingestion workflow. QA initiates the full end-to-end suite and Engineering contributes; it graduates to Lane A once that coverage closes the gap. Classified 2026-06-29.

Contents​

  • prds/ — Product Requirements Documents (1 anchor + 2 child PRDs)
  • rfcs/ — Request for Comments
  • tests/ — Test plans
  • delivery/ — Timeline, status updates, decisions

Knowledge Graph​