Rhythm 2.0 Specifications

Appearance

ADR-PFM-NOT-012Console, E-mail and Text Are Native; Customer Chat Goes Through Integrations

Markdown

ADR-PFM-NOT-012

Console, E-mail and Text Are Native; Customer Chat Goes Through Integrations

Markdown
  • DocumentProposed

KindDecision recordProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Console, E-mail and Text Are Native; Customer Chat Goes Through Integrations ​

Context ​

Delivery ownership must distinguish Rhythm-provided channels from the customer’s connected systems.

Decision ​

Notifications supplies native console, communication e-mail and AWS text capabilities; customer Slack and Teams use Integrations, with Teams deferred.

Alternatives Considered ​

Native customer chat would duplicate integration authorization and credential management. Routing native text through an integration gateway adds unnecessary credential and transport dependencies.

Consequences ​

The channel adapter contract is shared, but only console and operational HQ Slack are currently available. Other personal channels retain explanations of their deferred availability. HQ Slack is a separate system adapter using Rhythm’s own workspace.

Decision
Notifications supplies native console, communication e-mail and AWS text capabilities; customer Slack and Teams use Integrations, with Teams deferred.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software