Prepared answers
Agree common questions, response text and cases that need a person.
AI assistants
AI answers. Your team takes over.
An assistant explains your services, collects the request and passes complex questions to your team.
Discuss this task
- Answers stay on topic
- A clear next step
- Complex cases reach a person
Choose your task
A common question gets a short answer and next step.
- Receive question
- Find response
- Pass to team
When a person takes over: Pass individual requests to the team
The helper shows a short instruction and its source.
- Ask a question
- Find guidance
- Check the path
When a person takes over: If the path changed, ask its owner to confirm
The answer shows its limits and a human next step.
- Receive question
- Check status
- Involve a person
When a person takes over: Do not claim readiness without a confirmed status
Start with what you need
Team assistant
Define internal requests, permitted sources and answer boundaries.
Custom scenario
Design the interaction and assess integrations before stating capabilities.
Before we start
Is the site helper connected to AI?
Yes, but only after you allow AI in the privacy settings: questions are then sent to OpenRouter and the model provider. Without that permission the helper shows prepared answers.
How can invented answers be avoided?
Limit answers to approved material and route unsupported questions to a person.
Can an assistant take actions?
Only after the action, integration, permissions and review have been agreed and implemented.
Who will be able to see our information?
That needs to be defined for the project: who can read or change each type of information, where it is processed, and what is kept and for how long. Signing in does not give someone access to every record, and permission to read a document does not automatically allow it to be sent to another service. A new tool’s access rules need checking, not assuming.
How will we check the work?
We agree what the solution needs to do, then check the actual version against that. You should be able to see what was tested, what worked and what still needs attention. Accepting the work and putting it live are separate decisions.
Who looks after it once the work is handed over?
That should be settled before work starts: someone needs to own content updates, access and the response to problems. Handover, regular maintenance, incident support and new features are different responsibilities. Any support period, response time and cost need to be written down; ongoing support is not automatically part of the initial build.