starter.wiki中文

Decision map

Messaging

Which communication surface, delivery channel, or system-to-system event path does the product need?

Recommendation

Start with Transactional Email

Product and platform teams choosing customer communication infrastructure, embedded interaction capabilities, support operations, or outbound event delivery.

Open the starting decision

Scope

Use this boundary to avoid solving adjacent problems in the wrong layer.

Included

  • Application-triggered and broadcast email delivery
  • SMS and browser or device push delivery
  • In-product notification inboxes and embedded text or realtime media interactions
  • Customer-support ticket and service workflows
  • Producer-side outbound webhook delivery

Excluded

  • Cross-channel lifecycle journey orchestration, which belongs to Product
  • Internal queue transport and background execution, which belong to Infrastructure
  • Complete meeting products that are not embeddable communication infrastructure
  • Incident status communication
16

Important tools

These tools represent distinct routes inside this decision area; open the relevant Task before treating any as a default.

Decision sequence

Make the foundational ownership decisions before adding specialized capabilities.

  1. What initiates the communication and who receives it?

    Separate application-triggered delivery from campaign sends, then identify recipient, consent, sender, and unsubscribe or opt-out requirements.

    Transactional Email Email Marketing Programmable SMS

  2. Does the message leave the product or live in the product interface?

    Push reaches a user agent through a push service, while an in-app notification owns rendered product UI and user state.

    Push Notifications In-App Notifications

  3. Is the interaction an alert, a product conversation, a support case, or realtime media?

    Choose the record and protocol that match the participants, response model, agent workflow, and media requirements.

    In-App Notifications Embedded Product Chat Customer Support Platforms Embedded Realtime Audio & Video

  4. Is the recipient another software system?

    Use the Webhooks decision for producer-side event subscriptions and external HTTP delivery, not for internal work execution.

    Outbound Webhook Delivery

23

Decision groups

Each Task owns a distinct user decision rather than a product feature label.

45

Common confusions

These boundaries prevent adjacent Tasks from collapsing into one generic shortlist.

Transactional Email and Marketing Email are treated as one generic email-delivery decision.
Product-triggered one-to-one email and audience broadcasts have different intent, infrastructure, and unsubscribe operations.
Push Notifications and In-App Notifications are treated as the same surface.
Push is delivered through a user-agent push service; an in-app notification is rendered and stateful inside the product.
Embedded Product Chat is treated as a synonym for customer support.
Embedded Product Chat is a product feature built around conversation channels; Customer Support is built around agent-managed cases and service workflow.
Webhooks, queues, and background jobs are treated as interchangeable asynchronous infrastructure.
Webhooks deliver subscribed events to external endpoints; queues transport internal messages and background jobs execute work.
1456

What to defer

Do not add specialized identity systems before the product has the requirement they serve.

The product sends only application-triggered email and has no audience or campaign program.

Campaign segmentation, consent, deliverability, and automation operations are not yet active.

The product does not require a persistent inbox, embedded conversation, or realtime media.

These Tasks add product UI, state, moderation, participant, or media operations that channel delivery alone does not require.

37

Related starter stacks

See how these decisions appear inside complete application starting points.

Authoritative resources

Standards and primary documentation supporting the Category boundaries.

StandardW3C Push API
StandardW3C WebRTC
Official documentationGitHub: About webhooks

Sources

Claim-level references used for this decision map.

  1. 1
    Message Streams API

    Postmark · Accessed Official

  2. 2
    Push API

    W3C · Accessed Official

  3. 3
    Introduction to Inbox

    Novu · Accessed Official

  4. 4
    Chat channels

    Stream · Accessed Official

  5. 5
    Tickets API

    Zendesk · Accessed Official

  6. 6
    About webhooks

    GitHub · Accessed Official

  7. 7
    WebRTC: Real-Time Communication in Browsers

    W3C · Accessed Official