Hello Fanchon,
Thank you very much for your feedback. This is very interesting and particularly impressive given the volume of users involved.
I was wondering whether you had used webhooks to allow certain tickets to directly trigger a Dust agent. For example, when a ticket is created in Jira, Jira could automatically call a Dust agent: If so, when the Dust agent takes a relatively long time to answer, what approach do you use to ensure that the agent can then send its response back to Jira for the right Ticket, either by adding it to a dedicated column or by automatically updating the ticket status?
My second question concerns the progressive enrichment of the knowledge base. As Jira processes tickets and validated requests contribute to building up the company’s use cases and knowledge, how do you leverage this information to feed a semantic knowledge base or create accessible FAQs, for example in the form of Spaces in Dust?
Thank you very much for your feedback.