JTBD-CM-03 · Communications
Log meetings and calls
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.
What the catalogue records
Work v1 adds a free-text note on a subject timeline, and that is all: there is no meeting, call, participant, duration, direction or outcome model, no calendar and no telephony. A note is not a logged call
Evidence
This row names no test and no document of its own, and its status does not claim one. Treat it as unbuilt: nothing here proves it, and nothing here says otherwise.
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
- Schedule and track a follow-up — partially supported
- Honor unsubscribe and communication preferences — not supported