AI Agent for website support

With Eloquent you can easily create a support agent for websites that answers customer questions 24/7 in over 95 languages, based on the company’s own data. This type of agent can resolve a large portion of incoming questions automatically — saving time, reducing ticket load, and improving customer satisfaction. Because every organization has repetitive support requests, this is one of the easiest agents to sell.

How it works

The agent is trained on company data such as website content, FAQs, knowledge bases, or other documents. It can:

• Rely on this knowledge base to answer common questions.
• Hand a conversation over to a human via email when it cannot solve the issue.
• (With an integration) fetch information from connected systems to provide accurate, up-to-date answers.

Our recommendations

• Keep it fresh → Use a sitemap.xml and enable automatic fetch so your agent always has the latest information.
• Make it visible → Add an Ask AI, Ask a question or AI Support button prominently in your website header.
• Leverage contact pages → Place an input field on the contact page to capture user questions directly.
• Set expectations → Don’t pretend the AI is human. Users dislike being misled. Instead, be clear it’s AI — they often appreciate the speed and consistency.
• Use the right interface → Our website embed looks and feels like ChatGPT, making the user experience instantly familiar and intuitive.

What can it do?

A website support agent can handle far more than FAQs. It can:

• Answer questions based on your client’s own dataset (website content, knowledge base, or documents).
• Escalate conversations to a human when it can’t resolve the issue.
• Fetch live information from connected systems (CRM, CMS, e-commerce, etc.) to give accurate, current answers.

This makes the agent feel both smart and reliable — it resolves the bulk of conversations automatically, while still knowing when to hand over or pull in extra context.

What pain points does it solve?

• High ticket volumes overwhelming support teams.
• Long response times frustrating customers.
• Repetitive, low-value questions eating up staff time.
• Limited service availability outside office hours.
• Rising support costs without scaling headcount.
• Inconsistent answers across different team members.

Who it’s for

This use case is especially relevant for:

• E-commerce → shops managing product, shipping, or return questions.
• Professional services → agencies, law firms, accountants with recurring FAQs.
• Education & training → schools or online platforms fielding student questions.
• Healthcare & wellness → clinics needing structured intake or patient info.
• Public sector & non-profits → organizations that must provide accessible answers to citizens or members 24/7.

How to set it up

We’ll soon be releasing templates so you can just select this agent from the creation menu. Until then we recommend the following settings:

• Agent temperature: 0.1
• Reranking: On – when dataset is above 300 pages.
• Embeddings: 20
• Similarity: Default
• The following prompt works very well as a starting template, just remember to fill in the blanks:

# INSTRUCTIONS (SUPPORT)

## ROLE 
You’re a support expert for {company-name} that specialises in {5-to-10-word-summary}. You’re empathic, friendly, and always happy to help.

## GOAL
You’re on the website {website-url} to help visitors finding the right answers to their questions. You provide clear, concise answers with full context, avoiding jargon unless necessary. You respond in a tone that’s professional but warm, and you adapt to the user’s level of understanding. You aim to resolve issues efficiently, leaving users feeling heard, understood, and supported.

## TASK
Answer questions as briefly as possible, but with full context, and be unambiguous in your response. IMPORTANT: If you can’t be unambiguous ask a question to clarify what the user is looking for before answering.
IMPORTANT: Never ask more than 1 question at the time.
IMPORTANT: Only ask a follow-up question if it makes sense.
IMPORTANT: Never refer to the website you’re placed on unless you refer to a specific topic.
IMPORTANT: Don’t answer questions outside of your given context and goal. Instead refer to {contact-details} and state that the information is outside your intended knowledge.
IMPORTANT: If you can’t help the user you can escalate by calling the `share_conversation_via_email` tool to send this conversation to {primary-contact-email}, bcc: {optional-secondary-contact-email}. ONLY USE this when you have collected name and email.
IMPORTANT: Never promise refunds, always point to an expert or - if available- the policy.

## LANGUAGE
Your default language is {default-language-settings}. Always respond in the same language the user uses, regardless of the context language.

## FORMATTING
Use Markdown where necessary for clear structure, such as when explaining steps or multiple scenarios, but keep it chat-like, so avoid excessive headings and blank lines. Always use Markdown for e-mailadresses, url’s and other clickable content.

Examples in action

• Kwaliteitsregister Paramedici uses a support agent to handle around 1,200 questions per month. Visitors get consistent answers directly on the website, while the support team only handles edge cases.
• Opwegnaarzes uses a support agent to answer over 10,000 questions each month. Citizens receive information instantly, instead of waiting for staff or having to look through the website.

In both examples, clients see the same outcome: faster service, less manual work, and a support experience that scales without extra headcount.