Website AI · Custom solution
AI customer support for logged-in users
Logged in. Looked after.
A customer who is signed in to your website or portal wants to know about their order, their plan, their booking. The Authenticated Customer Assistant answers those questions using your login, your permission rules and the systems you connect, as well as the general questions a public chatbot handles.
It is designed and built for your platform after discovery, not bought off the shelf.
- Channel
- Your website or customer portal, after login
- Uses
- The customer’s authenticated session
- Data from
- Your systems, through approved integrations
- Delivered
- After discovery, integration and testing
Public chatbot or authenticated assistant?
The difference is whose information it may use
-
AI Website Chatbot
Answers anyone from public content
Your pages and uploaded documents. It never sees a customer’s private account.
-
Authenticated Customer Assistant
Answers a signed-in customer about their own account
Orders, plans, invoices, bookings or tickets, read from your systems for that customer only.
Access control
Login is the start of access, not the whole of it
Being signed in does not give the assistant free access to your data. Every lookup is checked on your server against what that customer is allowed to see.
-
The customer signs in
Through your existing login. The assistant receives the authenticated session, not the password.
-
The question is understood
General questions are answered from approved content; account questions go to the next step.
-
Permission is checked server-side
Your backend confirms the customer may see that order, invoice or booking before anything is read.
-
Only approved data is read
Through integrations agreed for the project, with credentials kept on the server.
-
Actions need their own approval
Changing an address, cancelling or raising a ticket only happens where that workflow was separately approved and built.
-
Escalate with context
If permission is refused, data is missing or the customer asks for a person, the conversation goes to your team as a ticket or callback request with the details attached.
Where it fits
Account questions it can answer, by industry
-
Ecommerce
Orders and returns
A signed-in customer’s orders, delivery status, return requests and support tickets.
-
Hosting providers
Plans and invoices
Hosting plans, invoices, renewal dates, existing service details and support-ticket status.
-
Real estate
Bookings and handover
Booking details, approved construction updates, documents and handover information for the buyer.
-
Subscription and software
Plans and billing
Plan details, billing information and account-related support.
Requirements
What a project needs from you
-
An existing customer login
On your website or portal, so the assistant can rely on your authenticated session.
-
Documented APIs or data access
For the information customers ask about, callable from the server.
-
Permission rules
Who may see which records, enforced by your backend.
-
A list of approved answers and actions
What the assistant may read out, and which actions, if any, it may take.
-
A test environment
Test accounts and data, so the integration is proven before real customers use it.
-
A handoff route
A support queue or team that receives anything outside scope, with the conversation.
Boundaries
What it will not do
-
Guess at account data
If a system does not return the information, the customer is told so and offered a person.
-
Act without an approved workflow
Refunds, cancellations and changes stay with your team unless you approve and integrate them.
-
Share another customer’s information
Every lookup is limited to records the signed-in customer is allowed to see.
An example conversation
A signed-in customer asks about a return
An illustration for an online store with an order API. The same pattern applies to invoices, bookings or tickets in other businesses.
-
Customer
Asks after login
“I returned the blue jacket last week. Has my refund gone through?”
-
Business system
Checks permission
Your backend confirms this signed-in customer owns the order before anything is read.
-
Business system
Looks up the return
The agreed integration reads the return and refund status for that order only.
-
Assistant
Answers in plain words
It explains what your system shows, such as “received at the warehouse, refund not yet issued”, without promising a date it was not given.
-
Person
Escalates when needed
If the customer disputes the status, the conversation reaches your support team with the order reference and the chat attached.
Questions
About the Authenticated Customer Assistant
Can I buy this online?
No. It depends on your login, data and permissions, so it is scoped and built with you. The AI Website Chatbot is the product sold online.
Does it also answer general questions?
Yes. It answers from your approved public content as well as from the customer’s own account data.
Is this the same as phone support?
No. This works on your website after login. Verified phone support is part of AI Customer Support & Call Routing.
Which platforms does it work with?
Any platform with a login and documented APIs we can call from the server. We confirm this during discovery; no platform is assumed.
Tell us what your customers ask after they sign in
Share your platform, your login and the questions that reach your support team.