Switchboard
Support ticketing SaaS
Customer support for small teams. Customers write in through a hosted help center; agents work a shared inbox with live presence, internal notes, response targets and reports.
What it does
- Shared inbox with live counts, full-text search and views for mine, unassigned and at risk
- WebSockets show who has a ticket open and who is typing, so two agents never answer the same customer
- Response targets pause while waiting on the customer and flag misses once
How it holds up
- Tenant isolation in PostgreSQL row-level security, so a forgotten WHERE org_id can't leak data
- Side effects run after commit: retrying email queue, live events fanned out through Redis
- Attachments checked by magic bytes and served with a sandboxing CSP


























