BUILD NOTES
What we’re building, honestly.
Working in the open: what exists, what’s in development, and what we won’t claim until it’s real. Newest first.
Note 002 — Tickets you can actually track
AUGUST 8, 2026 · WEBSITESHIPPED TO CODE
Help requests now work like a proper dispatch queue instead of a hopeful email. When you send a request you get a ticket number (like FM-A1B2C3), and you can check its status any time with the ticket number plus your email — received, being reviewed, replied, or scheduled.
Design choices we care about:
- Nothing is stored unless you actually send a request. Chatting with Brom saves nothing on our servers.
- Ticket lookup requires both the ticket number and the matching email, so tickets stay private.
- If our backend is ever unreachable, the site quietly falls back to a pre-filled email — you're never stuck.
Also new: a session prep checklist appears after you send a request — safe things to note or back up before anyone helps you, so the help goes faster.
Note 001 — A front door you can talk to
AUGUST 8, 2026 · WEBSITEBROMSHIPPED TO CODE
The site is no longer just a brochure. There are now two ways to get unstuck, right on the homepage:
- Ask Brom — a chat assistant that helps you find one safe next step for a frozen, slow, or misbehaving PC. Brom is a fictional, AI-assisted character and the site says so plainly; he gives careful general guidance, not diagnoses, and he will never ask for a password. When the AI backend isn’t reachable, a built-in guided version answers instead — the chat always works.
- Request help — a short intake that works like calling a ride: what device, how urgent, what’s happening, how to reach you. A human reads every request.
Boundaries we’re keeping as we build the “Uber of tech support” idea: FrozenCare stays labeled in development until it’s genuinely customer-ready, and the local technician network stays a waitlist until identity screening, insurance, disputes, payment, and emergency-safety controls exist. No fake availability, ever.