Slots: Entity resolution via Queries (fka. Query-triggered Paths)

Latest update: we plan to release Query-triggered Paths as Query resolvers under Experimental Features in August (previously scheduled for Preview Q3 2024). This will be made available to all customers on an opt-in basis.

Q. What are Query resolvers?

A. They allow you to resolve natural language user inputs (e.g. transfer ownership for cysco) into structured, system slots (e.g. Cisco systems record with sys_id: cis123). They allow users to clarify a specific record they want to act on after reviewing options retrieved using a Query API response. Here’s an example:

Please note, given this is an experimental feature, the experience may exhibit the following issues in Copilot:

• Reliably showing record details: Copilot may not show details of your Query records.
• Reliably keeping the plugin in context: Copilot may drop-off from your multi-turn Query resolver due to missing slots.
• Lack of acknowledgement: Copilot may not inform users about the record it selected sometimes.

We will be addressing these with the entity resolver experience for Plugins Workspace.

Some additional examples where we’re seeing Query resolvers being utilized by customers:

• Report application outages after querying & selecting an application.
• Adding a comment to a specific invoice
• Act on a system approval (approve / deny)

NOW AVAILABLE!

This feature has been made available to all customers under the "Experimental Features" tab in Creator Studio.

It is compatible with both Copilot & Classic but remember: you must pass data from your Query API to your Path followups. Note you may experience some experience issues (listed in the update above).

Link to developer docs on how to setup a Query resolver. This feature will remain an experimental feature, and we will mature our investment in entity resolution through the upcoming Plugin Workspace.

Let us know what you think. Thanks!