Home Nimbus Nimbus Integrations Copilot

Copilot - Send exit signals to Nimbus

Use an “Exit” event

To sent an exit silently to Nimbus map the value of the exit event in the Bot Response Template. Note that in Nimbus, parameters must be declared with $, so the full string is: $['value']:

Now you can to use the Event activity to send an Exit event to Nimbus Add Virtual User Activity.

Copilot Studio - Message Activity	Nimbus - Add Virtual User Activity
Send a fixed Message with a value like `Classification completed` as an event to Nimbus, so that Nimbus recognizes when Copilot's work is finished. 💡Examples below: Exit Event “Classification completed”: Indicate that the work has been successfully done in the Copilot (i.e. classify the intent). Exit Event “Queue Call”: Indicate that Copilot failed to make a classification.	Catch the `completed` keyword of the event value to exit. Catch the `failed` keyword of the event value to exit.

💡Regex Tip: If you are not sure about the returned values, ensure that variants of a word are covered to avoid false-postives:

For example:

\bfail(?:ed|ing|s)?\b

\b ensures word boundaries so it matches whole words only.
fail is the root.
(?:ed|ing|s|ure)? matches optional suffixes:
- failed
- failing
- fails
- failure
- fail (base form)

Use a spoken message as exit

Any text message which is spoken out to the customer will also be considered in the exits of the Virtual User Workflow Activity. Nimbus uses Regular Expressions matching on the text sent from Copilot to determine the exit path.

💡The table shows below shows some examples,

Luware Knowledge

Nimbus

Recording

Resource Library

Copilot - Send exit signals to Nimbus

Use an “Exit” event

Use a spoken message as exit

Luware Knowledge

Nimbus

Recording

Resource Library

Use an “Exit” event

Use a spoken message as exit

Related Articles