Skip to content

cross-cutting: prefill / programmatic compose API (capability-flag style) #51

@productdevbook

Description

@productdevbook

Some providers support message prefill (Beacon, Tidio, Jivo, Drift interactions), most don't (Chatwoot, LiveChat native no). Design as capability flag.

Evidence

Tasks

  • `prefill({ subject?: string; text?: string; fields?: Record<string, unknown> })`
  • Adapter capability type: `supports: { prefill: boolean, track: boolean, identityHmac: boolean, jwt: boolean, unreadCount: "native" | "poll" | "none", locale: boolean, theme: "config" | "runtime" | "none" }`
  • Unsupported calls throw `UnsupportedOperationError` with capability matrix link

Metadata

Metadata

Assignees

No one assigned

    Labels

    competitor-analysisDerived from OSS competitor issue patternsdxErgonomics, docs gapstrackingEvent tracking race / queue

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions