Skip to content
← All work
AI website assistant

Website Assistant

An on-site assistant that answers from answers the business wrote and approved — and says plainly when it has nothing approved to give.

The website assistant open on a demo business, answering a visitor question about treatments and pointing them to booking.
The same assistant declining a product question: it explains it cannot look up product inventory because this site has no online shop connected, and offers services, hours and booking instead.

2Tyme product

The problem

A website assistant grounded in the business's own approved content rather than improvising. The interesting half is the refusal: a visitor is better served by an honest 'I can't look that up' than by a confident guess.

The thinking

Retrieval grounded in CMS-approved answers, per-tenant isolation so one business can never surface another's data, an explicit decline when a capability is not connected, and a clean hand-off to a person.

The system

Answers live in the CMS with a draft/approved status, so the business controls what the assistant may say without touching code. Product lookup is resolved from the tenant's own configuration — a site with no shop connected declines instead of falling through to somebody else's catalogue.

Built with

 Grounded retrieval
 Approved-answer workflow
 Tenant isolation
 Explicit refusal
 Human hand-off
StackTypeScript · Next.js · Sanity · LLM-optional engine

What it proves

Retrieval grounded in CMS-approved answers, per-tenant isolation so one business can never surface another's data, an explicit decline when a capability is not connected, and a clean hand-off to a person..

What this is

Our own implementation, running against a fictional demo tenant. Northwind Aesthetics is an invented business, not a client.