Messaging Channels

Messaging channels define how a message is delivered to an audience member. ChimeKit supports multiple channels (like in-app and email), and each channel has its own content shape, delivery behavior, and user preference model.

What a channel is

A channel is a delivery surface. Two common channels are:

• In-app: shows up inside your product (for example, an inbox or notifications panel).
• Email: sent via your configured email provider to an email identity.

When you send a message, you can include one channel, or multiple channels at once.

How it fits into the system

• Audience members hold the identities needed for delivery (for example, an email address).
• Messages include channel content (in-app and/or email).
• Templates can define channel content once and reuse it.
• Categories (covered under Messages) are where preferences are applied: a user may opt out of email for “Marketing” but still receive in-app.
• Deliverability differs by channel: email has delivery lifecycle events; in-app is available immediately inside the inbox UI.

Getting started

1. Decide which channels you want to support first (in-app only is a great first step).
2. Make sure audience members have the right identities for those channels (email requires a verified-ish email identity).
3. Start with one message:
   • Create content directly (ad-hoc), or
   • Create a template and send it by template id.
4. Add preferences once you have categories defined.