peopleanalyst

Platform · Live · new here

Support channel — portfolio-wide /support form → ticket store → operator email

The one support door for every portfolio property (LS-SUPPORT-1 / HO-691): a clean /support form (source_site auto-detected from the proxy's host sets, or passed by sister sites via ?site=) writes a row to the shared platform.support_tickets store and fires a fail-soft operator email to mike@peopleanalyst.com over the commerce Resend transport. Spam is rejected cheaply (honeypot + max lengths + link-flood) with uniform success so bots learn nothing. Operator reads via service-key GET /api/support/tickets and MCP support.tickets.list (newest first, status filter). MVP piping only — AI triage (classify/route/auto-draft, withhold-to-human) is LS-SUPPORT-2. Flywheel: tickets are product signal + content input, not just cost (STRAT-SUPPORT-FLYWHEEL).

Cluster
Platform
Type
service
Status
Live
Used by
people-analytics-toolbox

Maturity evidence

Functioning
13/13 node:test tests green (npx tsx --test src/lib/support/tests/support.test.ts): honeypot + oversize + link-flood rejection, fail-soft email (throw / non-2xx / missing key all return false without throwing), status-filter parsing, proxy host -> source_site mapping. Migration drizzle/0179 creates platform.support_tickets; REST + MCP + /support page wired.
Valuable
Closes the LAUNCH-SURFACES-READINESS 'Support: MISSING everywhere' gap — required before commerce scale (buyers of live SKUs currently have no ticket channel; only raw mailto).
Understood
Design + boundaries (public POST vs gated GET, fail-soft email contract, platform-schema placement rationale) documented in module headers and the Layer-1 manifest entry.
Integrated
Only this app's own surfaces reach /support today. Integration = a second portfolio site (pa-site, get2great, ...) linking in with its own ?site= slug per the HO-691 linkback pattern.

How to use it

REST
/api/support/tickets
MCP
support.tickets.list
Data
src/lib/support/

Other Platform capabilities

← Every platform capability

Capability detail sourced from the People Analytics Toolbox capability feed (source of truth), snapshot retrieved 2026-07-23.