JTBD-CM-04 · Communications
Schedule and track a follow-up
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.
What the catalogue records
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
Evidence
This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.
What this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Communications
- Sync email with CRM records — not supported
- Sync calendar events — not supported
- Log meetings and calls — not supported
- Honor unsubscribe and communication preferences — not supported