Case study
Tim: useful website answers within a clear boundary
A small site guide with prepared answers, source links and local history—and the decision to defer a live AI service.
Written with assistance from Dottie, Mike’s AI dot assistant, under Mike’s direction and review.
Tim helps visitors find information on this website by matching reviewed questions to prepared answers and source links in the browser. The result is a small guide with inspectable content, retained conversation and a clear route to the relevant page.
I wanted visitors to get useful help while keeping the character unobtrusive around artwork and the playable game. I also wanted a firm distinction between public website content and private development material, and an operating model that fit a limited budget.
One question, a useful next step
Ask Tim how to save the Browser RPG. A supported question is matched to a reviewed answer about the game’s Saves menu and browser-local storage, with a link to the source page. Closing and reopening the guide keeps the conversation available at the same site address.
Suggested questions offer a direct route to a topic. Ambiguous input can offer choices; unsupported input returns useful site links. This release uses bounded topic matching.
Choose a smaller delivery deliberately
An earlier server-side prototype explored model access, visitor quotas and cost reservations. Its local checks used deterministic and simulated provider responses. The next acceptance work for a live version would cover answer quality, grounding, privacy and production budget enforcement.
I chose prepared browser-side answers for the delivery: reviewed content, source links, conversation history and the character interaction. The live AI service remains deferred and disabled. The technical record describes the prototype and the checks a later live-service decision would require.
Make the guide fit the page
I set the behavior, wording, visual direction and acceptance requirements, then directed AI-assisted implementation and revisions. Tim appears after the Home header collapses, supports keyboard activation and Escape, respects reduced-motion preferences and hides while the game player is loaded.
Tim keeps up to 60 messages from the latest 30 days in this browser. Expired records are removed when the guide next runs; storage does not delete them automatically while the site is unused. Clear conversation removes the guide’s history separately from game saves and appearance choices. Browser storage and coordination have limits, which the privacy page explains.
What this offers a team
The practical skill is choosing a useful operating boundary, then making the interface and evidence match it. A business considering a helper needs to decide which questions it can reliably answer, where those answers come from and what happens when it cannot help. The first delivery should fit those needs and its operating budget.
I used this studio feature to make that product and operating decision concrete. A client project would need its own user research, support measures and acceptance checks before deciding whether to add a live model.
Scope and next steps
Prepared answers trade broad conversational flexibility for predictable content and a simpler deployment. Content changes still require reviewing their source evidence, and stored history can become unavailable when browser data or the site address changes. The technical record keeps matching, storage, UI checks and deferred API work separate.