Add a trigger type for the backstop so that plugins can be run as a fallback option

Hey ​@Gmer can you share a more detailed example? Like what types of scenarios do you envision and what type of backstop feedback would you want to collect?

Hi Ajay,

Definitely. 
What I’m envisioning is an agent that tries to be more proactive than the current “but couldn't find any relevant options. Based on info you provided, I am unsure of how to help” message.
 

Ideas I have for the backstop agent would cover use cases like

1. Send a message with statistics on how many other users have also inquired about this subject and the status of solutions in development
2. For knowledge gaps, an agent that creates a ticket with a KB outline for a team to publish missing/ out of date information
3. Initiating a conversation about bot performance improvement, soliciting a request for an agent idea to increase bot functionality.

This is a very interesting & novel idea. It sounds like a form of  “continuous agent improvement” analytics + some insight into the “development backlog” for your agent.

Makes sense being able to kick off these types of flows – we’ll think about how to best support you with this, but it's not presently on the roadmap.