Discover
We look at the questions visitors and callers ask, the information that answers them, and where a person should take over.
EXAMPLE PROJECT
An AI chat assistant for your website
Visitors often have a quick question before they get in touch. An AI chat assistant can answer from your own business information and pass anything else to a person.
01 · THE PROBLEM
The problem
People visit your site after hours or between other tasks. If a simple answer is hard to find, many leave instead of asking.
Generic chat widgets give canned menus or answer from general knowledge, which can be confidently wrong about your business.
02 · SIGNS
Signs you have it
- Calls and emails often ask things the website already covers.
- Visitors ask questions outside business hours.
- Your services, policies, and common answers are written down, or could be.
- You want a clear path from a question to a real conversation with your team.
03 · A FIRST VERSION
What a first version looks like
An example of a focused scope. Your first version, price, and timing are agreed in writing for your project.
- A chat assistant on your site that answers only from information you approve.
- A plain notice that visitors are talking to an AI assistant.
- A hand-off to a person, such as a contact form, when it cannot help or the visitor asks.
- Topics it will not discuss, such as pricing details or advice, sent straight to a person.
- A log of conversations so you can see what people ask and correct weak answers.
04 · HOW WE’D DO IT
How we’d do it
The same four steps as our approach, applied to this kind of project.
Design
We agree on the approved information, the hand-off, off-limits topics, the AI provider, data handling, and visitor privacy.
Build
We build the assistant and test it before launch with real questions, including tricky and off-topic ones it should decline.
Improve
We review early conversations with you, fix gaps in the information, and confirm the agreed criteria. New features are scoped separately.
05 · QUESTIONS
Common questions
Related: AI integration · Websites & web experiences
What if it tells a visitor something wrong?
It can happen. Approved information only, a hand-off when unsure, and testing before launch reduce the risk. The conversation log lets you catch and fix weak answers.
Will this replace talking to our team?
No. It answers routine questions and hands visitors to a person for anything that needs one. You decide which topics it covers.
Where do visitor messages go?
To the AI provider agreed in design, preferably under your own account. Storage, retention, and your privacy notice are agreed before launch. The assistant does not ask for sensitive details.
Can it go on our current website?
Usually. It depends on how the site is built and hosted. We check that during discovery.
LET’S BUILD SOMETHING USEFUL
Have a version of this problem?
Tell us how the work happens today and what a useful first version would change. A plain-language description is enough to start.