Skip to content
ConversionIQ Docs

Account – Settings – SMS Requests

Route

Section titled “Route”
  • Path: /account/settings/sms-requests (TBD)
  • Parent: settings.md

Purpose (business goal)

Section titled “Purpose (business goal)”

Manage requests for provisioning SMS numbers and approvals required by enterprise policies.

User roles & permissions

Section titled “User roles & permissions”
  • Org Admin / Workspace Admin (TBD)
  • Permissions: sms.request, sms.approve (TBD)

Reference: Roles & Permissions Model

Layout structure

Section titled “Layout structure”
  • Requests list (pending/approved/rejected)
  • Request details drawer/modal
  • Approval actions

Components used

Section titled “Components used”

TBD

States

Section titled “States”
  • Empty: no requests
  • Loading: fetch requests
  • Error: permission denied
  • Complete: requests list rendered

Business logic (high-level)

Section titled “Business logic (high-level)”
  • Requests affect SMS channel availability and routing.

Domain refs:

API dependencies

Section titled “API dependencies”
  • GET /sms/requests
  • POST /sms/requests
  • POST /sms/requests/{id}/approve

Enterprise constraints

Section titled “Enterprise constraints”
  • SMS provisioning is sensitive; approvals must be auditable and role-gated.
  • Requests/approvals may involve external compliance requirements; workflows are TBD.

Edge cases

Section titled “Edge cases”
  • Duplicate request for the same workspace/number; handling is TBD.
  • Approval succeeds but downstream provisioning fails; reconciliation behavior is TBD.

Security & compliance considerations

Section titled “Security & compliance considerations”
  • Audit approvals/rejections

Reference: Security & Compliance

Analytics events (if applicable)

Section titled “Analytics events (if applicable)”

TBD

Reference: Analytics Events (MVP)