CFF Ops
Twenty sync — clients
Push pushes ClientAccount + ClientReplyConfig + topics up to Twenty. Pull overrides local YAML with Twenty's current state (operator edits in Twenty win).
Twenty sync — drafts
Push pending drafts to Twenty's draftReply view + pull
operator approve/edit/reject decisions back. Default runs both.
Twenty sync — client-tier
Push OperatorProfile + ClientTierAccount YAML records to Twenty,
plus any pending CTA-origin drafts via the shared draftReply
object. One-click upsert for the whole client-tier surface.
Twenty sync — engagement
Push every persona's engagement_targets.yaml rows and
every queued / dispatched / completed engagement action up to Twenty.
Local YAML + SQLite remain the source of truth — Twenty is the
operator read surface.
Training — promote few-shots
Lift operator-approved drafts older than dwell-days
(default 30) into the per-client cached few-shots. The next inbound
that hits each account's prompt builder will see the new examples.
Twenty schema — migrate
Provision every custom object + field CFF needs in the workspace. Idempotent — safe to re-run after a CFF version bump.
Bridge / Matrix status
Ping each bridge for its current login state.