How many pieces of content can my AI support agent use in its answer?
Your AI agent will look over all the help documentation, knowledge articles and content you add, and . This means that the answer will reference at most 6 different webpages, help documents or knowledge articles, but it may only reference 1 if all pieces of text came from the same source.
Do you answer based on multiple pages or pieces of content?
Yes, when you ask a question the most relevant text is taken from across all your knowledge and help articles at once to find the pieces that can be used to answer your question. This could mean that it answers based on a single article, multiple articles, or across 6 or more separate sources.
How long are the answers?
The length of answers varies depending on:
The knowledge articles and content you have uploaded.
The complexity of your question.
In short - it depends!
What content can I add to my AI support agent?
The following content can be added to your AI agent to "train" it:
Websites (publicly accessible)
Documents have a 30Mb limit and the following file types can be uploaded:
csv
For csv files, each row resides on its own line, and each element within the row has the header of its corresponding column added to it as a prefix.
Google Drive, up to 10Mb per file
OneDrive, up to 10Mb per file
Zendesk knowledge articles
Intercom knowledge articles
Freshdesk knowledge articles
Confluence knowledge articles
Shopify pages, products and customer data
You can add up to 10,000 pieces of content across these connections, please contact us via chat if you need more.
Can I train my AI support agent on my support tickets?
While it is possible to train your AI support agent on your support tickets on historic conversations, we strongly advise against it for a few reasons:
Agent responses are highly variable and inconsistent depending on the agent's tone, experience and demeanour, this will all feed into the AI's answers
Knowledge in tickets can very quickly become dated, an answer about a feature 1, 3 or 6 months ago may no longer be relevant today so customers will get poor-quality responses that may be inaccurate.
If you have a large volume of tickets then managing this knowledge can quickly become a very difficult task as you look through the thousands of agent responses to work out which are still relevant, and which you need to update.
Ultimately, the golden knowledge source should be your help documentation and knowledge articles, as these will have been verified, reviewed, and kept up to date. Keeping them updated also means that the customers who don't use your chat still benefit from the updated knowledge.
References
Will it output page numbers in the references and sources?