ExoMind - Exo Insights

feature overview exo insights , also referred to as exomind , is a generative ai powered feature that transforms your chatbot from a flow based system into a dynamic, knowledge based assistant instead of manually building a conversational flow for every possible question, you can create a "knowledge base" by uploading documents, websites, and other resources the bot then uses this knowledge base to understand and answer a wide range of free form user queries in a natural, human like manner this feature is designed to handle the "long tail" of user questions that are impractical to cover with individual, pre defined flows by training exomind on your company's support pages, product manuals, policy documents, or faqs, the bot can intelligently search, synthesize, and present relevant information, complete with source links for verification key capabilities of the exo insights module include knowledge base creation train the bot by uploading various document types (pdf, docx, xlsx, txt, etc ) or by providing website urls natural language understanding allows users to ask questions in a conversational, free flow manner without needing to use specific keywords source referencing the bot can provide a direct link to the document or webpage from which it sourced the answer, enhancing user trust priority management assign priorities to different documents to control which source the bot prefers when information overlaps customizable responses adjust settings like "temperature" to control the creativity of the bot's answers and "strictly answer from knowledge sources" to prevent it from responding outside its training data how to use the feature this guide explains how to enable exomind, build its knowledge base, and manage the content it uses to answer user queries enabling and configuring exomind from the main console menu, navigate to settings > solution settings enable the enable pdf searcher toggle from the choose pdf searcher model dropdown, select exomind (beta) configure the additional settings show source link check this box to have the bot include a link to the source document with its answers temperature adjust this slider to control the randomness of responses 0 is very factual and deterministic, while 1 is highly creative a setting around 0 7 is common strictly answer from knowledge sources enable this to prevent the bot from answering questions if it cannot find relevant information in its trained knowledge base click save building the knowledge base navigate to workflow > exomind(beta) this will take you to the knowledge base management page click on add new source choose the type of source you want to add for documents select "upload documents" and drag and drop your files (e g , pdf, docx, txt) for websites select "add web page" and enter the url after adding the sources, they will appear in the table with a status of "not trained " you must select them using the checkbox and click start training the status column will update to "training" and finally "trained" once the process is complete if it shows "training failed," you can hover over the status to see the reason managing sources assign priority you can set a numerical priority for each document when information conflicts, the bot will prefer the source with the lower number (1 being the highest priority) delete select one or more sources and click the delete button to remove them from the knowledge base download/copy for documents, an icon to download the original file is available for web pages, there is an icon to copy link common examples and use cases hr policy bot upload the company's hr handbook, leave policy documents, and benefits guides employees can then ask natural language questions like, "how many days of sick leave do i get per year?" or "what is the company's policy on remote work?" product support assistant train exomind on technical manuals, user guides, and troubleshooting articles customers can then ask questions like, "how do i reset my device to factory settings?" or "my screen is flickering, what should i do?" website content search provide the url of your main website or support section the bot will crawl the content, allowing users to ask questions about anything on the site directly within the chat window best practices for creating documents for exomind this guide outlines how to create, structure, and maintain documents for optimal performance of exomind , our rag based knowledge ai system for chatbots following these standards ensures higher exomind / rag accuracy 1\ document structure one document instead of multiple documents, have a single collated document for one exomind (in pdf format) main heading should clearly reflect the product or topic (e g , loan, savings account, credit card) each heading should start from a different page sub heading (optional) divide content into logical sections for easier navigation avoid very deep hierarchy keep it two levels only (heading and sub heading) each sub heading should also start from a different page separate sub heading for dynamic content create a separate sub heading for content which is dynamic (changes frequently) sub heading type description update frequency static information core product details, eligibility, features, general faqs rarely (more than 2 months) dynamic information offers, rates, operational updates, announcements frequently (less than 2 months) question / answer format (faq format) inside each heading/sub heading, format the content into question/answer format only questions can be one or more with a common answer there will be unique “question(s)/answer” pairs in any heading / sub heading inside each sub heading, the questions must be mutually exclusive and collectively exhaustible single page faq keep each faq on a single page — the answer must not spill over to the next page (half answer on one page and the remaining answer on the next page) avoid multi topic pages each page should cover a single, well defined topic only very similar questions should be on the same page whenever there is a confusion, it is better to move to another page each page of the document is one rag chunk consistent formatting maintain the same font, header hierarchy, and spacing across all documents 2\ content writing guidelines do not have the same question twice with different answers in the document this is most important to ensure exomind accuracy the answer must be comprehensive it should cover everything, including any potential follow up questions two different questions can have some section in the answer which is common no answer should be more than 3 paragraphs each question must be complete it should make sense without knowing the headers, sub headers etc frame questions as users will ask them focus on key words there should be initial question which help explain the product in simple language ensure every “question(s)/answer” pair is self contained and does not rely on another pair the document should be written in the tone which you want the bot to speak we suggest keeping the tone friendly and helpful avoid jargon as much as possible if you need to use any jargon, define the jargon within brackets if you are using any acronym, add the full form in brackets each time you use the acronym (not just at the beginning) remove product specific tags exclude internal terms like “jiffyearn” or “#jiffyearncash” unless necessary for comprehension example ❌ “how to open a jiffyearn or #jiffyearncash time deposit?” ✅ “how to open a time deposit in jiffy bank?” avoid cross references like “see above” or “refer below” or “same as above” do not use different terms for the same thing avoid inconsistent terminology (“fixed deposit” / “time deposit”) either use both words at all places, or use one single word at all places and one faq where it is explained that both these mean the same thing do not add screenshot of text do not add any image (any non searchable text) or scanned pdfs 3\ document naming, priority and sanity testing the document/pdf should be named with version or date use consistent naming if multiple documents have to be added in an exomind examples loan faq 25 nov 2025 pdf, creditcard 20 nov 2025 pdf use “priority setting”, if there are multiple documents with different confidence levels note we recommend using a single pdf document only for exomind internally maintain version history when updating faqs to ensure traceability test for accuracy after each upload, test key faqs and confirm the responses get pulled from the correct section 4\ continuous improvement cycle regularly review and refine documents using analytics and failed queries frequency activity monthly review top failed queries and restructure content if retrieval gaps persist quarterly refresh dynamic data (rates, offers, contact details) ongoing maintain naming consistency and terminology alignment across all sources 5\ testing and debugging protocol (post go live) when sharing or analyzing test results, always include timestamp and date of the test full conversation screenshot (for debugging context) if an issue is found go to home in the test interface re ask the same query confirm if the issue still persists if yes, capture full logs and share with the exotel support team 6\ common mistakes to avoid mistake impact uploading scanned or image based pdfs text unreadable → poor accuracy forgetting to click “train sources” source ignored by model overlapping or duplicate content reduces ranking precision missing priorities bot gives outdated or inconsistent answers expecting transactional behavior exomind handles q\&a, not workflows long multi topic pages reduces relevance of retrieval