- Visitor question
- Where can I find this equipment's specification?
- Source
- An approved document for the exact model
- Answer
- Point to the verified specification and its source
- Clarification or handover
- Missing facts, compatibility or warranty go to a specialist
- Result
- A supported answer or a clear next step; no booking is confirmed
What people and teams gain
Visitors can find their way more easily.
Answers are based on a specific service description or rule.
Staff receive more context.
An unclear question reaches a person with a useful record of the enquiry.
Permissions and boundaries are maintained.
The assistant does not disclose personal data or promise a service that is not available.
Usefulness can be tested.
We test common questions, errors and the route to a real booking or enquiry.
A useful answer includes a handover path
Customer question
Start with a real service or equipment question.
Approved source available and sufficient?
Yes: explain the published facts
For example, find the equipment specification and its source.
No or exceptional: hand over context
Compatibility, warranty, missing facts or protected status go to a specialist or separately checked integration.
Example: find an equipment specification, then pass compatibility and warranty questions to the specialist. Missing facts, protected order status or resource approval require a human or a separately checked integration.
Start with real questions
What do visitors ask before booking, registering or ordering? Which answers are already on the website, and which require a member of staff? We choose a limited, useful scenario and prepare the knowledge it needs. The assistant should not become another barrier between the customer and the team.
What pNet does
Prepares a verified basis for answers
We collect agreed descriptions, terms, instructions and FAQs. Each important source has an owner and an update process. If current information contradicts an older page, we resolve the source first rather than asking AI to guess.
Designs the conversation and its limits
We define what can be explained, which clarification is useful and when the conversation should pass to a person. Prices, availability, medical suitability, compatibility and individual terms are not invented from a general description.
Organises enquiry handoff
We agree the minimum information, receiving location and person responsible. The customer understands what was sent and what has actually been confirmed. A chat message alone is not a booking, an order or a promise to respond within a certain time.
Checks quality and behaviour when things go wrong
We use real questions, ambiguous requests and examples without an answer. We test prohibited topics, outdated materials, service outages and attempts to make the assistant ignore its boundaries. Usefulness and a proper handoff matter more than fluent wording alone.
One question, an authorised source and a handover
Examples of use
| Visitor's question | What service options are available? |
|---|---|
| What the assistant can do | Show an approved description and a link to the page |
| When a person is needed | When professional assessment is needed, including assessment of contraindications |
| Visitor's question | How do I book? |
|---|---|
| What the assistant can do | Explain the available route and conditions |
| When a person is needed | When a booking requires resources to be coordinated |
| Visitor's question | What is happening with my order? |
|---|---|
| What the assistant can do | Point to the official channel for checking |
| When a person is needed | When the status requires secure access |
For a salon: explain the service format and preparation using approved materials, then direct the visitor to booking or a specialist. Diagnosis and decisions about treatment are outside the assistant's role.
For an academy: help find a programme and participation requirements, clarify the format and pass individual questions to the administration. Promising a qualification or automatically enrolling someone requires a different process.
What remains with the team
Knowledge has an owner, enquiries have someone responsible, and difficult questions have a clear handoff. The team can correct sources and see recurring gaps. After launch, pNet helps maintain content and check changes within the agreed scope.
You can start with public information and enquiry preparation. Connecting private records, making bookings, changing orders and taking payment require separate agreement on permissions and checks.
What the customer receives and what stays with staff
A visitor to a salon can learn the booking rules and prepare to speak with an administrator. A prospective academy student can find information about a programme and its format, but does not receive a fabricated confirmation of a place. An equipment buyer can find a published specification and pass a question to the seller without an automatic compatibility judgment.
pNet first agrees the sources and tests answers against ordinary and difficult questions. Handoff is part of the design: who receives an enquiry, what information they see, and who confirms a real booking or order. If that route is not needed, an ordinary FAQ or form may be more reliable than an AI chat.
The knowledge base holds verified answers, while CRM receives the permitted enquiry. Actual message sending requires separate permissions and a delivery check.
Important: An AI answer is not automatically an accepted booking or a confirmed order. A member of staff remains responsible for complex cases.
Frequently asked questions
It can reduce selected repetitive questions. Professional decisions, exceptions and responsibility stay with people; we do not promise that the team can be removed entirely.
Only with a separately verified integration, permissions and confirmation rules. Having a conversation does not mean the assistant already has calendar access.
The assistant states its limit, asks an appropriate clarification or hands the question to a person. A missing fact must not become an invented service condition.
Each channel, account and interface is checked separately. A working website chat does not prove that every messenger is ready.
Connected services
Start with customers' most common questions
Tell us what visitors need to understand before getting in touch and where difficult questions should go. We will choose a safe and useful first scenario.