Skip to content

SMS connector: document provider abstraction boundary #434

Description

@sridharkalaibala

Parent: #34

Problem

Shops may want SMS alerts through different providers. Posnic should define the abstraction before adding provider-specific code.

Acceptance criteria

  • Document common SMS provider inputs: destination, template/message, sender id, status callback, and cost/error metadata.
  • Define privacy and opt-in boundaries for customer phone numbers.
  • Propose a fake SMS provider fixture for tests.
  • State that no real SMS is sent by default.

Out of scope

  • Integrating a specific SMS provider.
  • Marketing automation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: integrationsExternal services, optional connectors, import/export contractscommunity editionMust work in the free local/community edition without requiring Posnic ClouddocumentationImprovements or additions to documentationgood first issueGood for newcomershelp wantedExtra attention is neededneeds evidenceNeeds reproducible evidence before stronger product claimssecuritySecurity, auth, permissions, secrets, signatures, or data protectionsize: smallSmall, focused task suitable for a short PR

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions