Skip to content

Finalize operational launch runbook and tutor roster readiness #146

Description

@Taleef7

Context

The product code is only half the MVP: docs/OPS.md, docs/MVP.md, and docs/ROADMAP.md make operational readiness part of launch. The tracker should explicitly cover non-code launch work like tutor roster coverage, WhatsApp Business setup, labels, quick replies, SLAs, and policy communication.

Acceptance criteria

  • Confirm WhatsApp Business number, labels, quick replies, and operating-hour/SLA expectations are ready.
  • Confirm at least one approved tutor exists per offered subject, with two for high-demand subjects if available.
  • Confirm payment, matching, no-show, reschedule, and renewal workflows have named admin ownership.
  • Run through OPS workflows A-H and mark any missing app support as separate issues.
  • Update README/docs with the final launch runbook status.

References

  • docs/MVP.md launch checklist: operational readiness
  • docs/OPS.md workflows A-H and response SLAs
  • docs/ROADMAP.md Phase 0/MVP exit criteria

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

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions