Customer-facing assistants
Answer a defined set of questions from approved product or service material and guide visitors towards useful pages.
Conversational tools for approved website information and internal knowledge, with a defined scope and a practical route to a person.
Plan your projectAn assistant is only useful when people understand where its answers come from and what to do when it cannot help.
We scope the source material, audience, permissions, and answer behaviour before choosing the interface. A public website assistant and an internal knowledge tool need different access and handoff arrangements.
Answer a defined set of questions from approved product or service material and guide visitors towards useful pages.
Help staff find relevant policies, procedures, or product information in an agreed document collection.
Connect answers to retrieved material where appropriate, with links that let the user check the underlying source.
Define which users can reach which material. Source permissions need to be enforced before information enters an answer.
Decide when the assistant should ask a clarifying question, decline to answer, or direct the user to the appropriate person or channel.
Review representative questions, outdated documents, ambiguous requests, and source updates so the tool has a maintainable content process.
A team has approved procedures across several documents, but everyday questions still turn into repeated messages to the same person.
A useful first scope: A limited-access assistant with a curated document set, clear source references, and escalation when the source does not support an answer.
| Workstream | What you receive | What we need from you |
|---|---|---|
| Knowledge plan | Document scope, user groups, and answer boundaries. | Approved material, content owners, and access rules. |
| Assistant experience | An agreed interface, retrieval setup, and handoff paths. | Brand guidance and the real destination for escalations. |
| Quality review | Evaluation examples, failure findings, and maintenance notes. | Subject experts to review the answers and source freshness. |
Choose useful, current, and authorised sources.
Define answer style, limits, and user journeys.
Test normal questions, missing answers, and access boundaries.
Review feedback and keep the source material current.
Retrieval supplies relevant material to an AI model; it does not eliminate mistakes. References support checking, but an answer still needs evaluation against the actual source and task.
We do not describe an assistant as knowing everything about a business. The brief should identify excluded topics, unsupported actions, and when a person must take over.
Depending on the selected approach, approved material can be prepared from documents and web content. Formatting, scanned pages, freshness, and source permissions affect the work.
Yes, if identity and retrieval access are designed around those permission boundaries. A shared prompt alone is not an adequate access-control mechanism.
It may help with defined, recurring questions. Complex requests, complaints, account issues, or unsupported answers still need a useful human handoff.
The content process must define who approves source changes, how updates reach the assistant, and how important questions are rechecked.
Potentially. We assess the platform, identity needs, content access, hosting, and integration options before quoting the work.
A new website. A useful app. A smarter workflow.
Or an idea that deserves to be played.