TribeZ Support

TribeZ support queue

Connected apps (e.g. Mindful Missions) store tickets locally. When an app admin pushes a ticket here, it appears in the TribeZ App support admin view for your team — no Notion board required.

Back: AgreementOpen App support (admin)

Where tickets live

  • TribeZ Supabase table app_support_tickets — one row per pushed ticket, keyed by app + external id.
  • Staff UI: /admin-panel/app-support (after admin login).
  • Inbound API: POST /api/app-support/tickets with Authorization: Bearer matching APP_SUPPORT_INBOUND_API_KEY.

Status workflow

Matches connected apps: todo, in_progress, completed, blocked, expedited. When an app admin changes status after linking, the app PATCHes TribeZ to stay in sync.

Client workflow

  1. End user submits a request in the app (e.g. Mindful Missions `/dashboard/help`).
  2. App admin reviews `/admin/support` and clicks push to TribeZ when platform help is needed.
  3. Your team triages in App support, coordinates with the app admin link back to their console.
  4. Close the loop when work is done — status updates flow from the app when configured.