Types of Copilot responses
Watching Copilot at work is like listening to a symphony — of different response times — that blend together in harmony to give the user what they need at the right time.
Below is a breakdown of different ways Copilot can respond to users.
Sometimes, Copilot answers with only text. This is usually the case when the user asks a question like:
- “How do I do X”
- “Is this feature supported on my current plan”
- "What does Y do?"
You can make individual Nudge experiences (tours, surveys, announcements, checklists) available for Copilot to surface to users at the right time. This combination is tremendously powerful. Instead of always guessing when users want to see Nudge experience, Copilot can decide when to show them based on the user’s intent.
Copilot will surface these to users when it thinks that they will help the user, based on their question, previous chat history, and their context (including the page they’re currently on).
When Copilot suggests experiences, they will appear like this in the response, with a button to trigger them.
Copilot will always explain why It's suggesting the experience, so the user understands why they are seeing the option to initiate it.
Experience suggestions are like teaching the user how to fish; action executions are like giving the user a fish-catching-laser-gun they can operate with ease. There are two ways Copilot can handle an action execution:
By suggesting the action
This works similarly to suggesting an experience. The user is presented with a button to initiate the action, and then Copilot will then ask for input corresponding to each of the action’s arguments.
By collecting an argument
Sometimes, users will begin a conversation with a query like “add firstname.lastname@example.org to my team”. This is two things — a request to initiate an action, and an argument value. In situations where Copilot detects this type of query, it will “jump” ahead to that argument.