MW asking questions to assess user needs ?

Hi,

Currently MW is not trying to clarify the needs of the user by asking questions when the inputs of the users are not explicit enough. Is it a design consideration that is not going to change ? Or could it be submitted as a product idea.

An example of an unsatisfactory outcome is tickets filed through MW landing on ServiceNow queue with Summary/Short description looks like that : 

“I want to create an IS ticket.”

“I want to create a ticket in ServiceNow”

“I want to create a new ticket for an issue.”

Those are real examples of logged tickets from our ServiceNow instance.

The bot is only going to propose to file a ticket and if the user isn’t going to edit the “file a ticket” box it’s going to trigger a ticket as is. If MW would engage with the end-user to assess better the needs either to pull a better plugin answer or to file a ticket with more details it would be best. It feels one-way currently, trying to pull a plugin request as soon as possible even if query is unclear.

Another example for which we are expecting the copilot to probe/assess would be as below :

Ideally the bot would ask which application to try to pull an adequate/specific answer instead of a generic one. 

Regards

Valerian