> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/ai-assistants/how-to-set-up-ai-assistants-in-mercuri.md). # How to Set Up AI Assistants in Mercuri ### **1. Go to the AI Assistants Section** 1. Log in to your **Mercuri Dashboard**. 2. In the left-side panel, navigate to **AI Assistants**. 3. Click on **“+ Create Agent”** to start setting up a new assistant.
*** ### **2.** Configure the AI Assistant
Under the **Set Up Your Agent** section, you will find 6 tabs. Configure each tab carefully to set up your AI Assistant accurately. Let’s go through each tab one by one. #### 1. General In the **General** tab, enter the basic details of your AI Assistant, such as: * **Agent Name** * **AI Model** (pre-selected) * **System Prompt** {% hint style="info" %} The **System Prompt** defines how the AI Assistant should behave and respond to users. Provide clear instructions about: * **The assistant’s responsibilities**\ \&#xNAN;*(e.g., answering customer queries, sharing product information, handling basic support requests)* * **The communication style**\ \&#xNAN;*(e.g., professional, concise, friendly, and helpful)* * **Any limitations or escalation rules**\ \&#xNAN;*(e.g., directing users to a human agent for complex, sensitive, or account-related issues)* These instructions help ensure the AI Assistant responds consistently and accurately. **Example Prompt** {% code overflow="wrap" %} ``` You are a friendly and knowledgeable assistant for our website. You help customers with product information, FAQs, booking questions, and basic support. Keep responses clear, polite, and concise. For anything urgent or account-related, direct the user to our support team. ``` {% endcode %} {% endhint %} *** #### **2. Knowledge**
Once your AI assistant identity is configured, the next step is to train it with your business information so it can respond accurately to customer queries. Inside the **Knowledge** section in Mercuri, you can connect different knowledge sources that the AI will use while replying to conversations. **You can add:** * Your website URL * Sitemap URL (`sitemap.xml`) * Individual pages like: * Pricing pages * FAQ pages * Service pages * Product pages * Booking or policy pages
Why Add a Sitemap? Adding your sitemap allows Mercuri to automatically crawl and index your website pages. This helps the AI assistant: * Understand your business better * Learn your services and workflows * Access FAQs and important information * Provide more accurate customer responses Mercuri recommends starting with the sitemap because it gives the AI a complete overview of your website content.
When to Add Specific Pages Instead? If you want the AI assistant to focus only on important business pages, you can manually add individual URLs. This is useful when you want tighter control over AI responses for: * Pricing information * Appointment booking details * Refund or cancellation policies * Service-specific information * Support documentation
Benefits of Connecting Knowledge Sources Once your knowledge sources are connected, the AI assistant can: * Answer customer questions instantly * Give context-aware responses * Reduce repetitive support queries * Improve response accuracy * Deliver a more human-like conversation experience * Help customers get information faster without manual team involvement
*** #### 3. Tools
**Tools** section defines what your assistant can do. These are the tools and capabilities that the AI will have access to. {% tabs %} {% tab title="Wix Bookings Support" %} *Helps customers manage their bookings and appointments.* Use this if your business relies on: * Appointment scheduling * Class or session bookings * Event reservations * Service-based consultations Your AI Assistant will help customers with: * Booking new appointments * Checking availability * Rescheduling or cancelling bookings * Confirming upcoming sessions This is ideal for salons, coaching centres, clinics, fitness trainers, consultancies, etc. {% endtab %} {% tab title="Order Tracking" %} *Assist customers in tracking their order status and delivery.* Enable this if you want your AI Assistant to automatically answer: * “Where is my order?” * “Has my package been shipped?” * “When will I receive my delivery?” The system fetches live shipping and delivery data, reducing workload for support teams. Best for D2C brands, e-commerce stores, food delivery services, and logistics-based businesses. {% endtab %} {% tab title="Product Enquiry" %} *Answer customer questions about products, features, and availability.* Useful for businesses that offer multiple products or variants: * Clothing & accessories * Electronics * Food & FMCG * Health & beauty * Home decor Your AI Assistant will help users with: * Product features * Stock availability * Variants and options * Price and offers * Recommendations This automates a major part of pre-purchase conversations. {% endtab %} {% tab title="Customer Support" %} *Provide general customer service and support.* Enable this for: * Handling FAQs * Answering policy-related questions * Assisting with basic troubleshooting * Guiding users through workflows Your AI will act as the first line of support, escalating to human agents when needed. Best for any business that receives recurring customer service queries. {% endtab %} {% endtabs %} *** *** #### 4. Channels
After setting up your AI assistant and knowledge base, the next step is to connect the communication channels where customers will interact with your business. Inside the **Channels** section in Mercuri, you can connect platforms like: * WhatsApp * SMS Mercuri allows you to manage these conversations directly through the AI assistant. #### Connect a WhatsApp / SMS Channel To connect : * Select **WhatsApp /** **SMS** from the available channel options * Choose the phone number you want to connect * Click + **Connect Channel**
#### Connect Test Number After clicking on **+ Connect Channel**, Mercuri will prompt you to add a test number where you can test your AI assistant before going live. **To add a test number:** * Enter your phone number in the provided field * Click on **+ Add** Only the phone numbers added here will be able to chat with your AI assistant while it is in testing mode. {% hint style="info" %} #### Why This Is Important Adding test numbers allows you to: * Test AI responses safely * Verify workflows and automations * Check conversation quality * Ensure the assistant behaves correctly before customers use it This helps avoid errors and gives you full confidence before launching the assistant publicly. {% endhint %} #### Manage Connected Channels Mercuri also gives you control over connected channels directly from the dashboard. You can: * Enable or disable the channel using the **toggle icon** * Delete the connected channel using the **bin/delete icon** This makes it easy to manage testing, pause communication temporarily, or remove channels when needed. *** #### 5. Launch
**AI Billing & Keys** Before launching your AI Assistant, you need to choose how the AI model will be billed and accessed. Inside the **AI Billing & Keys** section, Mercuri provides two options: #### 1. Use Mercuri Credits Select **Use Mercuri Credits** if you want Mercuri to manage the AI infrastructure for you. With this option: * No API key setup is required * AI usage is billed using your Mercuri credits * Quickest and easiest way to get started #### 2. Bring Your Own Key Select **Bring Your Own Key** if you prefer to use your own AI provider account. You can connect API keys from supported providers such as: * OpenAI * Claude * Azure OpenAI Using your own key allows you to manage AI usage and billing directly through your chosen provider. *** After selecting your preferred billing option: 1. Click **Save AI Key Settings** Once saved, you can continue with training and launching your AI Assistant. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mercuri.cx/features/ai-assistants/how-to-set-up-ai-assistants-in-mercuri.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.