Website Chat.
A better first hello.
Explore a website assistant that answers everyday questions, gathers context and knows when a person should take over.
Product concept · Illustrative demos · Availability not confirmed
YOUR WEBSITE · SAMPLE STORE
Help, without
the waiting room.
A question. A helpful answer. A clear path to your team.
Anonymous visitor
No verified CRM contact linked
Hello! I’m a sample AI assistant. What can I help you with?
How can I check delivery details?
In this demo, I’d answer from the store’s approved delivery information. For a specific order, a teammate can help without guessing your identity.
Helpful answers.
Human when it matters.
A proposed experience built around your approved information — and the people behind your business.
FAQ assistance
Use approved FAQs and policies for everyday questions. When the answer is missing or uncertain, ask for clarification or pass it to the team.
A clear human handoff
Let a visitor ask for a person. A proposed handoff carries the transcript and question forward, subject to team availability.
Context, not assumptions
Capture the question and details the visitor chooses to share. Never infer a verified identity just from a conversation.
A website conversation.
Not another silo.
Keep the thread together.
In the unified inbox concept, website enquiries sit alongside supported messaging channels. Your team can see the conversation, understand what was asked and decide what comes next.
- Conversation history and a concise handoff summary
- A named teammate or queue for the next action
- Anonymous visitor status stays visible until verified
Illustrative workspace only · no live channel connections
SAMPLE CONVERSATIONS
Website visitor #104
Anonymous · delivery question
WhatsApp enquiry
Sample · product information
Instagram enquiry
Sample · needs a teammate
Concept only. A conversation is not proof of identity; CRM linking requires verification.
Know the difference between
a visitor and a verified contact.
A conversation is not an identity.
A new visitor starts anonymous. Sharing a name or email alone must not mark them as a verified CRM contact. The proposed workflow requires a verified identity and a confirmed matching record before linking.
- 01Keep the visitor unlinked by default.
- 02Verify identity through an approved process.
- 03Confirm the matching CRM record; ask permission separately for follow-up.
Design safeguard, not a connected CRM or verification service.
CRM link: Anonymous / unlinked
Follow-up: Blocked
Nothing is saved or sent. Even an eligible follow-up needs approved content, timing and team controls.
Useful context.
Clear boundaries.
Proposed controls for a responsible chat experience. Actual security, retention and compliance details need confirmation before launch.
Collect only what is needed
Ask for relevant information, explain its purpose and avoid requesting sensitive details in routine website chat.
Control access & retention
The design calls for authorised team access and configurable retention. These are requirements, not verified security certifications.
Respect customer choices
Consent to chat is not consent to marketing. Keep channel-specific follow-up permission separate and honour withdrawal.
A next step.
Never an automatic assumption.
A proposed workflow for relevant follow-up. No P4/P5 automation or live outreach is connected to this preview.
- 01
Confirm the contact
Verify identity and the matching CRM record. An anonymous visitor cannot enter outreach.
- 02
Check permission
Confirm permission for the purpose and selected channel, including current opt-out status.
- 03
Review the next step
A team-approved message, appropriate timing and channel rules determine eligibility.
- 04
Respect the outcome
Record the action and stop on opt-out. Permission alone does not mean a message must be sent.
A little more clarity.
What to expect from these channel concepts, and what still needs to be confirmed.
One conversation.
More ways to connect.
See how Website Chat fits into the REBNAL Channels vision.
Back to Channels