CRM job catalogue
Communications
no milestone assigned
5 jobs in this area. 1 partially supported, 4 not supported.
validated end to end An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.
partially supported Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.
not supported No implementation and no test. It would have to be built. This is the default status in the catalogue — a row moves out of it only when a test proves it.
JTBD-CM-01 · Sync email with CRM records
not supported
no email provider; needs the Integration Runtime
JTBD-CM-02 · Sync calendar events
not supported
no calendar provider
JTBD-CM-03 · Log meetings and calls
not supported
no Activity model
JTBD-CM-04 · Schedule and track a follow-up
partially supported
qualification creates exactly one follow-up Task with a deterministic source key (M6); there is no scheduler, reminder or task engine — the same limit JTBD-07 states
JTBD-CM-05 · Honor unsubscribe and communication preferences
not supported
no preference or suppression model (DATA_GOVERNANCE.md)
docs/strategy/DATA_GOVERNANCE.mdWhat a status here does not mean
These statuses describe this repository at this commit. None of them implies the framework is deployable: there is no authentication, tenancy or RBAC, so it is local-development-only whatever any row says. Every claim and every limitation is on one page.