Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

CRM: Conversion and Provisioning

Closed-won fan-out into operational products via explicit domain events and reference linking.

Problem

Closed-won transitions often require manual recreation of operational context before execution can begin.

Capability

Closed-won fan-out into operational products via explicit domain events and reference linking.

How it works

  1. 1 Conversion event publisher added for crm.opportunity.converted on stream crm:opportunity-events.
  2. 2 TMS conversion consumer provisions customers/carriers by crm_account_id reference.
  3. 3 CMMS conversion consumer provisions vendor contact profiles by crm_account_id reference.
  4. 4 Account rename endpoint added (PATCH /internal/accounts/{accountID}/name) with crm.account.renamed emission and TMS/CMMS display-name propagation by crm_account_id.

Operational outcomes

  • Reduced lag from deal close to operations-ready records.
  • Fewer conversion handoff errors between teams.

Integration boundaries

  • Intake & Qualification
  • Accounts & Contacts

Proof model

Feature-level proof

  • Conversion and Provisioning scope is defined in product module catalog.

    verified

    docs/products/crm/product.md · Module Catalog > Conversion & Provisioning

  • CRM modules support intake processing, route projection, and qualification lifecycle evidence.

    verified

    docs/products/crm/product.md · Module Catalog > Intake & Qualification

    Code: backend/services/crm/internal/modules/intake

    Contract: proto/crm/intake/v1

  • CRM intake and qualification flows are implemented in dedicated modules and contracts.

    verified

    docs/products/crm/product.md · Module Catalog > Intake & Qualification

    Code: backend/services/crm/internal/modules/intake

    Contract: proto/crm/intake/v1

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.