# Support

Client support portal where email becomes AI-triaged tickets, and an MCP server lets AI agents work them end to end.

- **Client:** Tomorrow Studio® (internal)
- **Year:** 2026
- **Stack:** Laravel 13, Vue 3, Inertia, Tailwind 4, laravel/ai (Claude), MCP

The studio's client support portal, live at support.tmrw.nz. Clients log
tickets through the portal or just email support@ — an AI triage agent
(Claude) reads every inbound message, writes the subject, priority and a
markdown summary, threads replies onto their tickets, recognises
staff-forwarded client email and credits the original sender, and parks
anything from unknown senders for a moderator to approve. A second
lightweight agent even decides whether a "thanks so much!" reply should
reopen a finished ticket (it shouldn't).

Studio-side it's a full admin: moderation with schedulable approvals that
hold tickets out of Slack until the boss wants them announced, per-ticket
audit trails, internal notes with Slack @mention DMs, time logged straight
to Streamtime, Bitbucket repo context on every ticket, Oh Dear uptime
badges on projects, and a streaming AI companion for questions like
"what's urgent right now?".

Auth is passwordless-first: single-use magic links (with a click-to-log-in
interstitial so Outlook link scanners can't burn the token), optional
passwords, and holographic profile cards with pickable accent colours.
The portal also exposes an MCP server, so AI coding agents can pull a
ticket's full thread and repo context, fix the bug in the site's own
repo, and hand back a drafted reply — which a human approves before any
client sees it.