IronKernel Platform

CRM: Activity & Tasking

Opportunity/account timeline tracking with owner task workflows and SLA visibility.

Problem

Opportunity/account timeline tracking with owner task workflows and SLA visibility.

Opportunity/account timeline tracking with owner task workflows and SLA visibility.

1 CRM activity and task persistence added (crm_activities, crm_tasks) with SQLC-backed query coverage for timeline listing, task...
2 Pipeline lifecycle mutations now auto-record activity timeline entries (qualification, stage changes, lane updates, conversion attempts, account...
3 Activity/task API endpoints added (GET/POST /internal/activities, GET/POST /internal/tasks, PATCH /internal/tasks/{taskID}/complete) plus /api/internal/* aliases.
4 SLA status computation added for tasks (no_sla, on_track, at_risk, breached, completed) based on due date and...

CRM activity and task persistence added (crm_activities, crm_tasks) with SQLC-backed query coverage for timeline listing, task...
Pipeline lifecycle mutations now auto-record activity timeline entries (qualification, stage changes, lane updates, conversion attempts, account...
Activity/task API endpoints added (GET/POST /internal/activities, GET/POST /internal/tasks, PATCH /internal/tasks/{taskID}/complete) plus /api/internal/* aliases.

Feature-level proof

Activity & Tasking scope is defined in product module catalog.
verified
docs/products/crm/product.md · Module Catalog > Activity & Tasking
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

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).

Commercial to execution

Outcome: Converted commercial records move into execution with less re-entry and clearer ownership.

Commercial handoff friction drops when conversion and execution planning are connected by shared identifiers.

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

Revenue-to-Execution

Formula: Execution-Aware Sales -> Load Lifecycle

Zero-to-Onboarded

Formula: CRM -> TMS

Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.