Add a conversational entry point
Use the existing agent integration and allowed-site configuration for your deployment. Clearly identify the assistant as AI. On this marketing site, the live connection loads only when a visitor opens it.
Website AI Agent
A website AI chatbot.
A more helpful welcome.
Give visitors a conversational way to understand your product and ask for help. Connect answers to a clear, configured next step.
YOUR WEBSITE
A little help.
Right here.
Echo AI assistant
Can someone help with my setup?
Let’s find the next step. What are you trying to connect?
Conversation → Ticket
1Visitor asks2AI helps3Context follows4Your team continues
How a website AI agent works
Make your website
a conversation channel.
Fit the agent’s knowledge, instructions and next steps to your visitors.
Answer from the right knowledge
Provide approved product information and relevant support guidance. Keep the sources current as your offer changes. Help visitors find a useful service page or clarify their question before taking another action.
Define the route to staff
Configure the appropriate Ticket tools, permissions and routing for requests that need follow-up. Pass the relevant conversation context so the receiving team can understand the request and what remains unresolved.
Keep the visitor informed
Distinguish an AI answer, a confirmed queued request and a person actually joining. If the service is unavailable or an action fails, show the real error and available retry or alternative route.
A conversation with somewhere to go
Keep the context
when your team takes over.
A useful answer may finish the conversation. When a request needs staff, the next step depends on the connected Ticket workflow and actual availability.
Embedding the assistant, creating a Ticket and joining a live conversation are separate capabilities. Verify each before presenting it as available.
Explore website-agent ticket handoffINBOX
Workspace accessNeeds a team action
Getting startedKnowledge answer
Plan questionSales inquiry
AI → YOUR TEAM
Context comes
with the request.
- Issue
- Missing workspace
- Tried
- Invitation email checked
- Next
- Review access
Explore connected services
Give each conversation
the right kind of help.
Choose a route that matches the visitor’s question.
Explore the details
Website AI Chatbot:
your questions answered.
What to know when choosing your workflow.
Can I add the agent to an existing website?
The agent is intended as an additional conversation channel for an existing site. Use the deployed package’s real embed mechanism, agent identity and allowed-origin settings.
Does every chat automatically become a Ticket?
No. Intake and handoff rules determine when a Ticket is created. A conversation session and a support Ticket are separate records.
Can a visitor continue with a human?
Where the live takeover connection is configured and staff are available. Otherwise use the configured asynchronous workflow and show its actual state. See the handoff details.
Can I try the agent on this website?
Use Ask Echo AI to check availability. The preview explains when the live connection is not ready and offers labelled guided examples. Those examples submit no real messages or Tickets.
PUT IT INTO PRACTICE
Explore the documentation.
Follow the setup, understand the controls and find the next step.
Website AI agent: conversations and ticket handoff
Plan an EleonEcho website AI agent with appropriate knowledge, visitor access, verified ticket handoff and clear live-staff availability.
AI knowledge sources, context and retrieval
Learn how configured AI knowledge sources, retrieval modes, source permissions and conversation context shape an EleonEcho agent’s answers.
Use the customer support portal
Sign in with email OTP, create and reply to authorized support tickets, manage safe attachments and understand customer and Account Administrator access.
Your next chapter, with AI
More ideas out.
More conversations moving.
Bring your publishing, marketing and support work into Echo.