Triggers: NLU - Negative examples

We are making final changes to expose the new intents support in the UI. Aiming to launch in early March.

We’re still on track for Preview release in March!

Excited about this one!

1. Did the preview release go as scheduled?
2. When do we expect to see this in full release?

Hey @Matt Stimmel due to an increased focus on Workflows & Plugin Builder -- we will be launching Generative Intents V2 to Preview in April instead. We appreciate your patience. 

Is there an update on this?  Or should we just plan on seeing this when workflows and plugin builder come along?

hey, checking in again - is there an update?

We have a rogue CS Query that keeps triggering when it shouldnt - we’d like the ability to reign it in

Yes @Matt Stimmel apologies about the delays here. This feature rollout date has been deferred in favor of building workflow plugins (launch date is now marked TBD -- instead of March).

Workflow plugins will be rolled out with the generative intents v2 experience by default. We are still tracking this feature for Queries & will update the rollout timeline once we can prioritize it.

Thanks for your patience!

Update: The capability is on-track to be released to Preview by August.

We just released this capability to Preview! 🔥

Key behavior:

• Both Paths & Queries now support negative triggering examples! Negative examples are guaranteed to never trigger.
• Add as many +ve & -ve triggering examples to each plugin (no upper limit).
• End-user triggering is more accurate than before. 

Please check it out & let us know what you think.

For the new Creator Studio Query Triggering enhancement, when I choose what is to trigger, do I have to select any of these options below?

Can I leave it be at ‘Slot Identification is correct’? 

What happens if I do, does it trigger on the entire sentence or is it selecting parts of the sentence like it was before this enhancement?

 

@hundleymf in your screenshot no slot is selected (since {{query}} is not identified). That means the configured utterance will trigger your query plugin but no slot will be extracted.

If you think a specific slot should be extracted from this utterance, you should select “Another part of the utterance should be identified” & type the relevant slot value.

You can choose to leave it as it is if you don’t think a slot should be getting extracted. Let us know if you have more questions.

Thank you! We noticed this the other week. It takes a little longer to create example utterances but this interface change makes it easier for me to configure slot extraction and triggers to work as i would expect them to. 

Thank you! 
-Anthony