# Create your first assistant Source: https://documentation.droog.io/essentials/Create-first-assistant Droog Conversational Assistant allows you to create AI agents tailored to your business needs. In just a few steps, you can set up an assistant that understands your domain and starts answering user questions. This guide walks you through creating your first assistant. ## Create an assistant in minutes Your assistant can be ready in just a few minutes. Once created, you can train it with your knowledge and deploy it for users. ## Step 1 — Open Assistant Dashboard From your main dashboard, click **Create Agent** to start creating a new assistant. Dashboard ## Step 2 — Create Assistant Creating an assistant is guided through a simple setup flow. When you click **Create Agent**, Droog opens a wizard that helps configure your assistant’s purpose, personality, and behavior. Trial accounts can create one assistant with limited features. Upgrade your plan to create multiple assistants and unlock full capabilities. Follow the steps below: ### 1. Select Industry Choose the industry or domain that best matches your assistant’s purpose. You can also manually describe your domain if it is not listed. ### 2. Voice and Personality Select how your assistant should communicate, for example, friendly, professional, or technical. This helps shape how responses sound to your users. ### 3. Core Mission Define the primary role of the assistant. Examples include: * Customer support assistant * Lead capture assistant * Product guide * Internal knowledge assistant This helps the assistant understand what it should focus on. ### 4. Constraints and Additional Rules You can define rules or guidelines your assistant should follow, such as: * Follow company best practices * Avoid discussing competitors * Redirect billing questions to support This helps control assistant behaviour. ### 5. Select Avatar (Optional) You may upload or select an avatar image for your assistant. This helps personalise the assistant experience. Once complete, click **Create Agent**. After clicking **Create Agent**, Droog automatically prepares your assistant using the information you provided. ### 6. Upload Knowledge Sources Your assistant needs knowledge to answer questions accurately. You can upload documents such as: * PDF files * Text files * Markdown files * Word documents You can also import knowledge from websites by adding URLs or sitemap links. If needed, you can skip this step and upload knowledge later. When importing content from websites, ensure you have permission to use the content. Always follow ethical and legal guidelines. ### 7. Launch & Activate Assistant This is the final step of the setup wizard. Review your assistant details and activate it. Once activated, your assistant becomes available for testing and deployment. ## Assistant Created Successfully After completion, you will be redirected to the dashboard where your new assistant appears. Click the assistant to: * Modify settings * Add or update knowledge * Customize responses * Deploy the assistant You are now ready to test and deploy your assistant. # Embed on Your Website Source: https://documentation.droog.io/essentials/embed-on-your-website Put your assistant in front of your users — live on your website in under 5 minutes. ## Your assistant, on your website Once your assistant is configured and tested, the final step is making it available to your users. Droog gives you a small snippet of code that you or anyone on your team who manages your website can paste in. The result is a chat widget that appears on your website, ready for visitors to use. Droog Web Chat ## Before you embed Make sure your assistant is ready: All documents you want the assistant to use are uploaded and show a `Active `status. You've run through key questions in the test console and are happy with the responses. Your assistant's status is set to `Published`. A draft assistant will not respond to users. ## How to get your embed snippet 1. Open your assistant from the **Dashboard** 2. Click the \*\*Assistant \*\*you want to publish 3. Navigate to settings and scroll down 4. Copy the embed snippet shown on the page Embed Snippet Your snippet will look like this: ```python theme={null} ``` The `Org_ID `and `Agent_ID` Values are unique to your assistant. Use exactly the values shown in your **Deploy** tab — do not change them. ## How to add it to your website Paste the snippet just before the closing `` tag on any page where you want the assistant to appear. HTML Code Editor — showing a website's HTML file with the Droog embed snippet pasted just before the closing body tag, highlighted to show placement ### If you use a website builder You don't need to edit HTML directly. Most website platforms have a dedicated section for adding custom scripts: | Platform | Where to add it | | --------------- | ----------------------------------------------------------------------------------------- | | **WordPress** | Appearance → Theme Editor → footer.php, or use a plugin like *Insert Headers and Footers* | | **Webflow** | Project Settings → Custom Code → Footer Code | | **Wix** | Settings → Custom Code → Add Code → Body — End | | **Squarespace** | Settings → Advanced → Code Injection → Footer | | **Shopify** | Online Store → Themes → Edit Code → theme.liquid (before ``) | Not sure where to add it? Send the snippet to your web developer or the person who manages your website. It's a one-minute task for anyone familiar with your site. You can always reach out to [contact@droog.io](mailto:contact@droog.io) for clarification or support ## After embedding — what to expect Once the snippet is added, visit your website. The Droog chat widget should appear in the **bottom-right corner** of the page (default) or wherever you desire to place the widget Click it to open the chat and send a test message to confirm it's working correctly. If you see the chat bubble and receive a response, your assistant is live. ## Controlling where the widget appears By default, the widget appears on every page where you've added the snippet. If you only want it on specific pages — for example, just your support page or your pricing page — simply add the snippet only to those pages. ## Removing or pausing the assistant To temporarily stop the assistant from appearing on your website, either: * **Remove the snippet** from your website's HTML * **Unpublish the assistant** from your Droog dashboard — the widget will stop responding without you needing to change any code ## What's next? Once live, track how users are engaging with your assistant. Adjust how your assistant handles edge cases, off-topic questions, and escalations. **Have a question about embedding?** Reach us at contact[i@droog.io](mailto:hi@droog.io) # How Droog Assist Answers Your Questions Source: https://documentation.droog.io/essentials/how-droog-assist-works A plain-English guide to how Droog finds the right answer from your content — every time. ## The short version When a user asks your assistant a question, Droog doesn't guess. It searches through the content **you've uploaded**, finds the most relevant pieces, and uses that to craft a clear, accurate answer — all in seconds. Think of it like giving your assistant a filing cabinet full of your documents, and training it to find exactly the right page every time someone asks a question. ## Why this matters Most AI assistants are trained on general internet knowledge. They sound confident, but they might give answers that are outdated, off-brand, or simply wrong for your specific business. Droog is different. **Your assistant only answers from your content.** If the answer isn't in your knowledge base, it says so, rather than making something up. This makes Droog assistants: * ✅ **Accurate** — grounded in your actual documents * ✅ **Trustworthy** — won't invent facts or go off-topic * ✅ **Up to date** — add new documents anytime to keep answers fresh * ✅ **On-brand** — reflects your tone, terminology, and policies ## How it works — step by step Here's what happens from the moment a user types a question to the moment they get an answer. ### 1. You upload your content You start by uploading your documents — PDFs, Word files, website URL pages, or any other content that contains the knowledge your assistant needs. KB Droog reads through all of it, breaks it into small, meaningful sections, and stores it in a way that makes it easy to search later. This happens automatically; you don't need to tag or organise anything manually. This step only happens once per document. After that, your content is ready to be used immediately. ### 2. A user asks a question When someone types a question into your assistant — for example, *"What documents do I need to apply?"* — Droog gets to work. Chat UI ### 3. Droog searches your content Droog doesn't search using simple keyword matching. It understands the *meaning* behind the question and finds the sections of your documents that are most relevant, even if the user didn't use the same words. For example, if your document says *"required supporting materials"* and the user asks about *"documents needed"*, Droog understands they're asking the same thing. The more content you upload, the better Droog gets at finding the right answer. More documents mean more knowledge to draw from. ### 4. An answer is generated Droog takes the most relevant sections it found and uses them to compose a clear, natural response. The answer is always based on what's in your content — nothing more, nothing less. Message UI The whole process, from question to answer, takes just a few seconds. ## What happens if the answer isn't in your content? If a user asks something that isn't covered in your uploaded documents, Droog will say it doesn't know, and escalate it as an active ticket based on the intent of the escalation being a handoff, knowledge gap, or out-of-scope question, rather than guessing or making something up. This is a feature, not a limitation. It keeps your assistant honest and your users informed. You or your team can clearly be notified of the escalation and take actions respective to the requirement. You can customise what your assistant says when it doesn't have an answer — for example, redirecting users to your support team or a contact form. See \*\*[Customise Behaviour](/guides/customising) to set this up. ## Keeping your assistant accurate over time Your assistant is only as good as the content you give it. Here are a few simple habits that keep responses accurate: Whenever your policies, pricing, or processes change, update your knowledge base. Your assistant will reflect the changes immediately. Delete documents that are no longer accurate. Old content can lead to outdated answers, even if newer documents say something different. If your website has helpful content like FAQs, product pages, and guides, add the URLs directly or the sitemap to select relevant URLs. Droog will read and index them automatically. After uploading new content, use the built-in test console (Test Assist) to check that answers have updated correctly before users see them. ## Ready to build your knowledge base? Learn how to add, update, and organise your documents. Use the test console to check how your assistant responds before going live. **Have a question?** Reach us at [contact@droog.io](mailto:hi@droog.io) # Multi-Tenancy & Workspaces Source: https://documentation.droog.io/essentials/multi-tenanacy Understand how Droog keeps your organisation's data private, isolated, and fully under your control. ## Your workspace, your world When you sign up for Droog Assist, you don't just get an account; you get your own **private workspace**. Everything inside your workspace, your assistants, your documents, your users, and your conversations — belongs exclusively to your organisation. No one else can see it, access it, or share it. This is what we mean by **multi-tenancy**: many organisations using the same platform, each with complete separation and privacy. Tenant Dash ## Think of it like a private office building Imagine a large office building with many companies inside. Each company has its own floor, its own staff, its own filing cabinets, its own locked doors. The building (Droog's platform) is shared, but every floor (your workspace) is completely private. *You cannot walk into another company's floor, nor can they walk into yours.* That's exactly how Droog works. Your data is never mixed with another organisation's data, not in storage, not in search, and not in any AI response. ## What lives inside your workspace When you log into Droog, everything you see and manage belongs to your organisation alone. All the AI assistants you create live here. Each one is configured for a specific purpose, audience, or product. All the documents, files, and websites you upload are stored exclusively in your workspace. You control who in your organisation can log in, manage assistants, or view conversations. All conversation data and usage reports are visible only to you. ## Managing your team *(in progress)* You can invite colleagues to your workspace so they can help manage assistants, upload documents, or monitor conversations. Team Management Screen — showing a list of team members with their roles and an invite button Each person you invite gets their own login. You can: * **Add** new team members at any time * **Remove** access instantly if someone leaves * **Assign roles** to control what each person can see and do Only the **Organisation Admin** can invite or remove team members and change workspace settings. ## Multiple assistants, one workspace Your workspace can hold more than one assistant. This means you can create different assistants for different purposes — all managed from the same place. For example: | Assistant | Purpose | | -------------------- | --------------------------------------------- | | **Support Bot** | Answers customer FAQs and product questions | | **Onboarding Guide** | Helps new users get started with your product | | **Internal Helper** | Answers questions from your own team | | **Sales Assistant** | Engages website visitors and captures leads | Each assistant has its own knowledge base, personality, and deployment settings. Changing one does not affect the others. Start with one assistant, get it working well, then create more as your needs grow. You don't need to set everything up at once. ## Your workspace is yours — always Your data is never used to train shared AI models. Your documents, your conversations, and your users' information stay inside your workspace and are never shared with other organisations on the platform. Multitenancy ## What's next? Set up an assistant inside your workspace in minutes. Upload the content your assistants will use to answer questions. **Have a question?** Reach us at [contact@droog.io](mailto:hi@droog.io) # Frequently Asked Questions Source: https://documentation.droog.io/faqs Quick answers to the most common questions about Droog Assist. ## General Droog Assist is an AI-powered conversational assistant platform. It lets you create chat assistants that answer questions using your own content — your documents, your website, your policies. Unlike general-purpose chatbots, Droog assistants only respond based on the information you provide. This makes them accurate, trustworthy, and specific to your business. No. Droog is designed to be used by anyone — no coding, no AI expertise required. Creating an assistant, uploading documents, and embedding the chat widget on your website are all guided, step-by-step processes that take minutes. Droog works across industries. Organisations in education, healthcare, finance, legal, retail, real estate, and many other sectors use Droog to automate answers to common questions. During setup, you'll choose your industry to help the assistant understand its domain. Yes. All new accounts start on the **Trial plan**, which gives you limited access to explore the platform and create your first assistant. To unlock full capabilities — including multiple assistants, higher usage limits, and advanced features — you'll need to upgrade to a paid plan. See our [Pricing page](https://droog.io/pricing) for details. *** ## Setting Up Your Assistant Most users complete their first assistant in under 10 minutes. The setup wizard guides you through every step — industry, personality, mission, and knowledge base. If you're uploading a large number of documents, the indexing process may take a few additional minutes, but you can leave it running and come back. The number of assistants you can create depends on your plan. Trial accounts are limited to one assistant. Paid plans allow you to create multiple assistants — each with its own knowledge base, personality, and deployment settings. Yes. You can update your assistant's name, personality, mission, constraints, and knowledge base at any time from the dashboard. Changes take effect immediately. Nothing is permanent in Droog. You can edit all your assistant's settings, upload or delete documents, and adjust behaviour at any point — even after the assistant is live. *** ## Knowledge Base Droog supports **PDF, DOCX, TXT, HTML, and Markdown** files. You can also add content by pasting a website URL or submitting a sitemap link for an entire website. Document limits depend on your plan. If you're on the Trial plan, you'll have a limited number of uploads. Paid plans offer higher limits. Check your plan details in your dashboard under **Settings → Plan**. Most documents are ready within a minute or two of uploading. Larger files may take slightly longer. You'll see a `Completed` status next to each document once it's ready to use. Always wait for `Completed` before testing — queries against partially processed content produce unreliable results. Wrong answers are almost always a knowledge base issue. Here's what to check: 1. **Is the correct document uploaded?** Make sure the file containing the right answer is in your knowledge base with a `Completed` status. 2. **Is there an older, conflicting document?** If you have two versions of the same document, delete the outdated one. 3. **Is the content clear in the document?** Vague or ambiguous source content leads to vague answers. Make the content more specific. After making changes, test the assistant again using the **Test** tab. No. Droog can only read publicly accessible web pages. If your content is behind a login, export it as a PDF or Word document and upload it directly. *** ## Conversations & Behaviour If the answer isn't in your knowledge base, your assistant will say it doesn't have that information — rather than guessing. You can customise this response to redirect users to your support team, a contact form, or any other resource. See [Customise Behaviour](/guides/customising) to set this up. Yes. Droog assistants support multi-turn conversations — the assistant remembers context within the same conversation thread. This means users can ask follow-up questions naturally without repeating themselves. Context is not carried over between separate conversation sessions. Yes. During setup — or at any time through your assistant's settings — you can add constraints in the **Extra Intelligence** field. For example: * *"Do not discuss competitor products"* * *"Do not answer medical or legal questions — direct users to a qualified professional"* * *"Only answer questions related to our product and services"* *** ## Embedding & Deployment Copy the embed snippet from the **Deploy** tab in your assistant's dashboard and paste it before the closing `` tag on your website. See the full [Embed on Your Website](/deployment/embed) guide for step-by-step instructions, including how to add it to popular platforms like WordPress, Webflow, and Shopify. Yes. You can paste the same embed snippet on multiple websites or pages. The assistant will behave the same way wherever it is embedded. Yes. Simply paste the snippet only on the pages where you want the assistant to appear. If you don't add it to a page, the assistant will not appear there. Basic customisation — such as changing the widget colour to match your brand — is available from your assistant's settings. More advanced visual customisation is available on higher-tier plans. *** ## Data & Privacy No. Every organisation on Droog has a fully isolated workspace. Your documents, conversations, and users are never shared with or visible to any other organisation on the platform. No. Your content and conversations are not used to train any shared AI models. Your data stays within your workspace. Only members of your organisation's workspace can view conversation history. You can manage who has access by reviewing your team members under **Settings → Team**. *** ## Account & Billing Go to **Settings → Plan** in your dashboard and select the plan that suits your needs. Upgrades take effect immediately. Yes. You can cancel your plan at any time from your account settings. You'll continue to have access until the end of your billing period. Try resetting your password from the [login page](https://app.droog.io). If you're still having trouble, contact us at [hi@droog.io](mailto:hi@droog.io) and we'll help you regain access. *** ## Still have a question? If you didn't find the answer you were looking for, we're happy to help. Reach us at [hi@droog.io](mailto:hi@droog.io) — we typically respond within one business day. Explore the full documentation to find detailed guides on every feature. # Conversation Analytics Source: https://documentation.droog.io/guides/conversation-analytics See how your users interact with your assistant — and use those insights to keep improving it. ## Know what your users are actually asking Once your assistant is live, real users start asking real questions. Analytics gives you a window into those conversations — so you can understand what's working, what's not, and where to improve. Droog has two levels of analytics: * **Workspace Analytics** — a bird's-eye view across all your assistants combined * **Bot-Level Analytics** — a detailed breakdown for each individual assistant *** ## Workspace Analytics The Workspace Analytics page gives you a combined view of activity across **all your assistants** in one place. This is the right place to start when you want to understand the overall health of your Droog deployment. Workspace Analytics Dashboard ### How to open it 1. Go to your main **Dashboard** 2. Click **Analytics** in the left navigation You can filter by date range using the **From** and **To** date pickers, and toggle between **Day** and **Month** views to zoom in or out on trends. Use **Active Bots Only** to filter out inactive assistants from the view. *** ### Summary metrics The five cards at the top give you an instant health check across your entire workspace: | Metric | What it means | | ------------------- | ------------------------------------------------------------------------------------------------------ | | **Total Sessions** | The number of individual conversations started by users across all your assistants | | **Total Messages** | The total number of messages exchanged — both user questions and assistant replies | | **Avg Latency** | The average time your assistant takes to reply to a message | | **P95 Latency** | The response time for the slowest 5% of messages — useful for spotting occasional delays | | **Escalation Rate** | The percentage of conversations where the assistant couldn't fully resolve the user's query on its own | A high **Escalation Rate** means users are frequently hitting dead ends. This is a strong signal to review your knowledge base and add missing content. *** ### Usage & Performance Trends chart Below the summary cards is a chart that plots **messages**, **sessions**, and **average latency** over your selected date range — all in one view. Usage and Performance Trends Chart Use this chart to spot: * **Spikes in sessions or messages** — often linked to campaigns, product launches, or events bringing traffic to your site * **Latency increases** — if the latency line climbs sharply on a particular day, check if large knowledge base changes were made around that time * **Quiet periods** — consistently low engagement may mean users aren't finding the chat widget easily *** ### Bot Usage Breakdown At the bottom of the Workspace Analytics page is a table breaking down activity **per assistant** — so you can see which bots are doing the most work. Bot Usage Breakdown Table | Column | What it tells you | | ---------------- | ------------------------------------------------------- | | **Bot Name** | The name of the assistant | | **Status** | Whether the assistant is currently active or inactive | | **Sessions** | Number of conversations started on this assistant | | **Messages** | Total messages exchanged on this assistant | | **Storage (MB)** | How much knowledge base storage this assistant is using | *** ## Bot-Level Analytics For a deeper look at any individual assistant, open that assistant from your dashboard. The overview panel shows detailed metrics for that bot alone — broken into four sections. Bot Analytics Detail Panels *** ### Performance & Cost *How fast the bot responds and what it costs to run.* This panel tells you about the speed and operational cost of your assistant. | Metric | What it means | | ------------------ | ------------------------------------------------------------------------------- | | **Avg Latency** | The average time taken to respond to a user message | | **P95 Latency** | Response time for the slowest 5% of messages — helps identify occasional delays | | **Cost / Session** | Estimated cost per conversation | | **Cost / Message** | Estimated cost per individual message | Cost metrics help you understand usage at scale. As your assistant handles more conversations, these numbers help you plan your usage and choose the right plan. *** ### User Engagement *How actively users interact with the bot.* This panel shows how users are actually behaving inside conversations. | Metric | What it means | | ---------------------- | ----------------------------------------------------------------------------------------- | | **Total Users (Est.)** | Estimated number of unique users who have interacted with the assistant | | **Active Users** | Users who sent at least one message in the selected period | | **Avg Msg / Session** | Average number of messages per conversation — higher means users are engaging more deeply | | **Dropoff Rate** | Percentage of users who opened the chat but didn't send a message | A high **Dropoff Rate** may mean users are unsure what to ask when they open the chat. Consider adding a welcome message or example questions to give users a clear starting point. *** ### User Feedback *How users rate the quality of your assistant's responses.* Users can rate individual responses with a thumbs up or thumbs down directly inside the chat. This panel aggregates that feedback. | Metric | What it means | | --------------- | ----------------------------------------- | | **Thumbs Up** | Number of responses users found helpful | | **Thumbs Down** | Number of responses users found unhelpful | | **Avg Rating** | Overall satisfaction score out of 5 | Your **Thumbs Down** responses are your most valuable improvement signal. Browse those specific conversations to find exactly which answers frustrated users — then update the relevant documents in your knowledge base. *** ### Automation Health *The bot's ability to handle conversations on its own — without needing to escalate.* | Metric | What it means | | --------------------- | ------------------------------------------------------------------------------------ | | **Total Escalations** | Number of conversations where the assistant couldn't resolve the query independently | | **Escalation Rate** | Percentage of all conversations that ended in an escalation | A low escalation rate means your assistant is self-sufficient. A high rate is a clear signal that your knowledge base has gaps that need filling. *** ## Using analytics to improve your assistant Analytics isn't just a report — it's a feedback loop. Here's how to act on what you see: Review conversations that escalated. Identify topics the assistant couldn't answer and upload content to cover those gaps. Filter for Thumbs Down responses. Find the weak answers and improve the relevant documents in your knowledge base. Check if latency increases coincide with large knowledge base uploads or high-traffic days. Flag to support if spikes persist. Add a friendly opening message or example questions to your assistant to give users a clear starting point. *** ## A simple weekly review routine A 10-minute weekly check is enough to keep your assistant improving consistently. 1. **Open Workspace Analytics** → check total sessions and escalation rate at a glance 2. **Review the trends chart** → spot any unusual spikes or drops in the past week 3. **Open Bot-Level Analytics** for your most active assistant → check feedback scores and dropoff rate 4. **Act on one thing** → upload a missing document, adjust a constraint, or improve the welcome message Small, consistent improvements compound quickly. An assistant reviewed weekly will be significantly sharper after a month than one left untouched. *** ## What's next? Add content to cover the gaps your analytics revealed. After uploading new content, test to confirm the improvements are working. **Have a question?** Reach us at [hi@droog.io](mailto:hi@droog.io) # Managing Your Knowledge Base Source: https://documentation.droog.io/guides/managing-knowledge Learn how to add, update, and organise the content that powers your assistant's answers. ## Your assistant knows what you teach it Your assistant doesn't come with pre-loaded answers. It learns from the content you provide, your documents, your website pages, your guides, and your policies. The **Knowledge Base** is where all of that content lives. The better your knowledge base, the better your assistant's answers. This page explains how to build and maintain it. Kb1 ## What you can upload Droog accepts a wide range of content types. You can mix and match; most organisations use a combination. Product guides, brochures, policy documents Internal handbooks, process documents, FAQs Plain text content, release notes, support articles Paste any public webpage, Droog reads and indexes it automatically Add an entire website at once by submitting its sitemap link When importing content from websites or external sources, ensure you have the right to use that content. Always follow applicable copyright and data usage guidelines. ## How to add content ### Upload a file 1. Go to your assistant's **Knowledge** tab from the dashboard 2. Click **Upload** 3. Select the file from your computer 4. Wait for the status to show `Completed` and `Active` Upload KB ### Add a website URL 1. Click **Scrape via Sitemap** 2. Paste the full web address (e.g. `https://yourwebsite.com/faqs`) 3. Droog will visit the page, read its content, and add it to your knowledge base ### Add an entire website via sitemap 1. Click **Scrape via Sitemap** 2. Paste your sitemap URL (e.g. `https://yourwebsite.com/sitemap.xml`) or (e.g. `https://yourwebsite.com`) 3. Droog will index all the pages listed in the sitemap automatically. You can select individual or multiple pages and add them to your knowledge base Upload scrape Always wait for documents to show a `Active` status before testing your assistant. If you test while content is still processing, answers may be incomplete or inaccurate. ## Understanding document status After uploading, each document goes through a short processing stage. Here's what each status means: | Status | What it means | | ------------------ | ------------------------------------------------------------------------------- | | `Processing` | Droog is reading and preparing your content — this usually takes under a minute | | `Completed/Active` | Content is ready, and your assistant can now use it to answer questions | | `Failed` | Something went wrong — check the file format and try uploading again | If a document repeatedly shows `Failed`Try exporting it as a plain PDF and uploading that version instead. Complex formatting in Word documents can occasionally cause issues. ## Updating your content Your knowledge base is not set-and-forget. Keeping it up to date is the single most important thing you can do to keep your assistant accurate. ### When to update * Your **pricing or plans** have changed * You launch a **new product or feature** * Your **policies or processes** are updated * A document contains **outdated information** ### How to update You have two options: **Replace a document** — Delete the old version and upload the new one. Your assistant will immediately use the updated content. **Edit a URL source** — If you added a webpage, you can schedule a frequency to re-scrape it at any time to pull in the latest version of that page. `In progress` Knowledge Management Actions — showing a document list with delete and re-sync buttons on each row ## Removing content If a document is outdated or no longer relevant, remove it. 1. Find the document in your **Knowledge** tab 2. Click the **delete icon** next to it (You can also multi-select items for deletion) 3. Confirm deletion Deleting a document removes it from your assistant's knowledge immediately. If the document contained answers to common questions, your assistant will no longer be able to answer those questions until you upload updated content. ## Tips for a great knowledge base Upload content that directly answers the questions your users actually ask. Broad, general documents are less useful than targeted, specific ones. Review your knowledge base once a month. Remove anything outdated and add any new content your users might need. Well-formatted documents produce better answers. Avoid scanned images of text — Droog reads text content, not images within PDFs. After adding or removing content, spend a few minutes testing your assistant to make sure it's responding correctly. *** ## What's next? After updating your knowledge base, test your assistant to check its responses. Control how your assistant responds when it can't find an answer. **Have a question?** Reach us at [contact@droog.io](mailto:hi@droog.io) # Testing Your Assistant Source: https://documentation.droog.io/guides/testing-your-assistant Check how your assistant responds before your users ever see it, and catch issues early. ## Test before you go live Before your assistant is seen by real users, it's worth spending a few minutes testing it yourself. This helps you catch gaps in your knowledge base, spot unexpected responses, and build confidence that your assistant is ready. Droog has a built-in test console so you can do this without any technical setup. UI ## How to open the test console 1. Go to your **Dashboard** and open the assistant you want to test 2. Click the **Test Assist** tab 3. Click on **Start Conversation** 4. Type a question in the chat box, just like a real user would 5. Review the response That's it. No special configuration needed. The test console uses your live knowledge base. This means any documents you've added or removed will be reflected immediately in test responses. ## What to test The goal of testing is to make sure your assistant answers correctly, stays on topic, and handles edge cases gracefully. Here are the key areas to check: ### Core questions — does it know what it should? Start with the most common questions your users are likely to ask. These are the questions your knowledge base was built to answer Ask yourself: * Is the answer **accurate**? * Is the answer **complete** — or is something important missing? * Does it sound like it fits your brand? ### Out-of-scope questions, does it stay in its lane? Try asking your assistant something it shouldn't answer, something completely unrelated to its purpose. A well-configured assistant should politely decline and redirect the user, rather than trying to answer something it has no business answering. If your assistant answers out-of-scope questions confidently, revisit your **Bot Identity and Mission** settings and add a constraint like: *"Only answer questions related to \[your topic]. For anything else, direct users to \[your support contact]."* ### Unknown / relevant questions what happens when it doesn't know? Ask something that isn't covered in your knowledge base at all. Your assistant should acknowledge that it doesn't have that information, not guess or make something up and instantly record the user's query as an escalation, where the human agents can review and revert to the user. | What you want to see | What to do if you don't | | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | "I don't have that information — please contact our team at \[email]" | Upload a document covering that topic, or add a fallback instruction in your assistant's constraints | ### Follow-up questions → does it remember the conversation? Droog assistants support multi-turn conversations — meaning the assistant remembers what was said earlier in the same chat. Test this by asking a follow-up question that only makes sense in context: > *"What documents do I need to apply?"* *(assistant replies)* *"How long does it take to process them?"* The assistant should understand that "them" refers to the documents mentioned earlier, not start from scratch.
## Common issues and how to fix them Likely cause → The relevant document wasn't uploaded, or the content is too brief Fix → Upload more detailed content covering that topic Likely cause → Outdated document is still in the knowledge base Fix → Delete the old document and upload the correct version Likely cause → No constraints defined Fix → Add topic constraints in the **Extra Intelligence** field Likely cause → Document is still processing Fix → Wait for the document status to show `Active`. Press the `Re-sync` In the knowledge base, then test again Likely cause → Personality settings are too generic Fix → Revisit **Voice and Personality** and add more specific tone guidance ## Test after every change Testing isn't a one-time step. Anytime you make a change to your assistant or knowledge base, it's worth running a quick test to ensure everything still works as expected. Check that the assistant can now answer questions about the new content. Confirm the assistant handles questions about deleted content gracefully. Verify that tone, constraints, and behaviour changes are reflected correctly. Always do a final test run before activating or reactivating a live assistant. *** ## What's next? Once you're happy with how your assistant responds, deploy it to your website. After going live, track how real users are interacting with your assistant. **Have a question?** Reach us at [contact@droog.io](mailto:hi@droog.io) # What is Droog assist Source: https://documentation.droog.io/index An intelligent conversational assistant **Droog Conversational Assistant** is an AI-powered chat assistant that enables businesses to provide intelligent, real-time conversations powered by their own data. It combines Retrieval-Augmented Generation (RAG), modern language models, and enterprise integrations to deliver accurate, contextual, and reliable responses to users. Instead of relying only on a general AI model, Droog connects your knowledge sources—documents, websites, databases, and internal content—to generate answers grounded in your information. This allows organisations to deploy conversational experiences that are trustworthy, scalable, and domain-specific. ## Why Droog Traditional chatbots rely on scripted flows or static FAQs, which quickly become outdated and require manual maintenance. Droog replaces rigid bot logic with an adaptive conversational system that: • Understands natural language queries\ • Retrieves relevant knowledge in real time\ • Generates contextual, human-like responses\ • Continuously improves as knowledge updates This enables users to receive accurate answers instantly without navigating complex documentation or websites. Droog Benefits ## Key Capabilities Droog answers questions using your own data sources, ensuring responses are accurate and relevant to your domain. The assistant maintains conversation context, allowing users to ask follow-up questions naturally. Deploy assistants across websites, products, or internal tools without rebuilding logic for each use case. Droog can be integrated into web apps, SaaS platforms, customer portals, or internal enterprise tools. Updating your knowledge sources automatically improves assistant responses without retraining models. # Quickstart Source: https://documentation.droog.io/quickstart Go from signup to a live, embedded AI assistant in under 10 minutes. ## Overview Droog Assist lets you deploy a conversational AI assistant trained on your own content — no code required. In three steps, you'll create an account, configure your assistant, and embed it live on your website. ## Step 1 — Create your account and organisation **Estimated time: \~2 minutes** [Sign up at app.droog.io](https://app.droog.io) using your organisation's email address. Droog Assist Sign Up Screen During registration, you will be asked to provide: 1. **Organisation name** — this becomes your isolated tenant workspace 2. **Primary email** — a one-time password (OTP) will be sent here for verification 3. **Password** — set after email verification is complete Once registration is complete, you are redirected to your [Dashboard](https://app.droog.io). Your account starts on the **Trial plan** with limited provisions. Each organisation gets a fully isolated workspace — users, assistants, and knowledge bases are **never shared across tenants**. ## Step 2 — Configure your assistant and knowledge base **Estimated time: \~5 minutes** (longer if uploading large documents) From your dashboard, click **Create Agent**. This opens a guided setup wizard. ### Assistant identity Fill in the following fields to define how your assistant behaves: | Field | Description | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Industry** *(required)* | The domain your assistant operates in — e.g. Healthcare, Finance, Education, Legal | | **Voice and Personality** *(required)* | The tone your assistant uses — e.g. Professional, Friendly, Technical | | **Bot Identity and Mission** *(required)* | A clear description of the assistant's purpose, who it helps, and how it should respond. A detailed mission produces a more accurate and consistent assistant. | | **Extra Intelligence** *(optional)* | Additional rules, constraints, sample phrases, or company-level context to guide behaviour — e.g. "Do not discuss competitors", "Always escalate billing queries to support" | All required fields must be filled before proceeding. The more specific your **Bot Identity and Mission**, the better your assistant will perform out of the box. ### Build your knowledge base Your assistant answers questions using the content you upload here. You can also skip this step and add knowledge later from the **Knowledge** tab in your dashboard. **Supported file types:** Each uploaded file goes through an ingestion pipeline — text extraction, chunking, embedding, and indexing. Wait until all uploaded documents show a `completed` status before testing your assistant. Querying against partially indexed content produces unreliable or incomplete results. When importing content from websites, ensure you have the rights to use that content. Always follow applicable copyright and data usage guidelines. ## Step 3 — Publish and embed **Estimated time: \~1 minute** ### Publish your assistant Click **Publish** from your assistant dashboard. This changes your assistant's status from `draft` → `published` and makes it accessible to users. ### Embed on your website Once published, navigate to the **Deploy** tab. Copy your unique embed snippet and paste it before the closing `` tag on any webpage where you want the assistant to appear. ```html theme={null} ``` Replace `data-widget-id` and `data-bot-id` with the actual values shown in your **Deploy** tab. These are unique to each assistant you create. Your assistant is now live. Open your website, and the chat widget should appear in the bottom-right corner. ## What's next? Use the built-in test console to evaluate responses before going live with real users. Add, update, or remove documents and URLs from your assistant's knowledge. Fine-tune tone, constraints, fallback responses, and escalation rules. Serve your assistant from your own domain with full TLS support. **Need help?** Reach us at [contact@droog.io](mailto:hi@droog.io) or visit your dashboard to open a support request.