Skip to main content
IronKernel Platform

CRM: Intake and Qualification

Initial CRM intake proto contracts scaffolded (crm.intake.v1).

Problem

Inquiry channels often create inconsistent records and manual triage queues that slow qualification response.

Capability

Public inquiry capture, validation, qualification scoring, and owner/queue routing.

How it works

  1. 1 Initial CRM intake proto contracts scaffolded (crm.intake.v1).
  2. 2 Initial backend inquiry validation domain scaffolded for required commercial fields and low-friction qualification inputs.
  3. 3 Public intake endpoint scaffolded at POST /api/public/intake/inquiries with explicit origin allowlist checks, IP-based rate limiting, request...
  4. 4 Intake pipeline abstraction introduced with sink interface and PostgreSQL persistence (with log-mode fallback for local/testing) plus...

Operational outcomes

  • Faster response from intake to qualified opportunity.
  • Cleaner commercial handoff into pipeline workflows.

Integration boundaries

  • Intake & Qualification
  • Accounts & Contacts

Proof model

Feature-level proof

  • Intake and Qualification scope is defined in product module catalog.

    verified

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

  • 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.