The user input No match apology happens in addition to what is set in the actions.
Yes what is available allows for maybe more granularity than what you are after. But for us at least we do want to be more specific about what wasn't understood rather than just a generic message. Eg no match on a product color option, sorry I didn't understand the color you were after, for product x you can pick from red, green or blue etc. As apposed to no match on a service type request.
Not sure how you would achieve what you are after at a global level, other than having a communication list which you copy to each flow, and then set the no match to that list. Which yeah means updating multiple flows if you want to update it, but not sure what other option there is for your use case.
Original Message:
Sent: 03-16-2025 18:12
From: Brady Harrison
Subject: Jumping from No Match to a Reusable Task, Or Setting up a No Match Strategy using global No match
Hi Anton, Thanks for your reply.
This unfortunately needs to be set at each digital bot menu separately, which isn't ideal when we may have digital flows with multiple decision points.
What we are trying to do is an over arching no match strategy that doesn't need to be set at a node level, but allows for this kind of function, which I cant seem to find as a possibility.
I was looking at the general No match under User input, which doesn't have the option for multiple messages, or the capability to send the user to a reusable task where we could handle our no match strategy at a global bot level. I looked through expression builder and was hoping it could be possible using an expression that counts up and uses if statements to emulate a switch, but Im unsure if that's worth pursuing as an option.

------------------------------
Brady Harrison
Original Message:
Sent: 03-16-2025 16:30
From: Anton Vroon
Subject: Jumping from No Match to a Reusable Task, Or Setting up a No Match Strategy using global No match
This is built in now. I am assuming this is for a digital bot?
Under No Match click customize no match

Select literal type, then + Communication to build your order of prompts


And then it follows the normal no match pathing after there, which you can control through booleans set before/after to determine where you were up to etc etc etc.
------------------------------
Anton Vroon
Original Message:
Sent: 03-14-2025 21:31
From: Brady Harrison
Subject: Jumping from No Match to a Reusable Task, Or Setting up a No Match Strategy using global No match
Hi Jason, I've had a look at that article and it doesn't really give what I'm hoping for. The user input section is where I have been looking,
I'm trying to do something as follows on a global (not reusable task / digital menu) level.
User enters bot
Bot : Hello
User : sdjkgdhg
Bot : (No match 1) I'm sorry, I didnt understand that
User : dsfgjdfgd
Bot (No Match 2) I still didnt get that, can you try to rephrase
User : fsdjgdfjk
Bot : (No match 3) It looks like I'm having some trouble here, Let me get you through to someone who can help (offers a contact button)
In the User input section, I can configure a number of no matches, however, it always gives the same message. I Want to either:
a : Jump to a reusable task on no match (globally, not just on digital menus) which I can use to build the above type of strategy
b : Code the strategy to work using expressions
The core reason is to simplify build, so we dont need to assign a specific no match condition to every node that could have a no match. we also want this strategy to govern the overarching "no match" of the bot, as not all bots will open with a digital menu or a node capable of assigning a specific no match option to.
hope this helps explain what Im looking for.
Regards
Brady
------------------------------
Brady Harrison
Original Message:
Sent: 03-14-2025 17:03
From: Jason Kleitz
Subject: Jumping from No Match to a Reusable Task, Or Setting up a No Match Strategy using global No match
Hello Brady,
I was looking at this article in the Resource Center. There is a "No Match Detected" field that can be configured to have a maximum amount of retries.
------------------------------
Jason Kleitz
Online Community Manager/Moderator
Original Message:
Sent: 03-13-2025 20:05
From: Brady Harrison
Subject: Jumping from No Match to a Reusable Task, Or Setting up a No Match Strategy using global No match
Hi All!
I'm looking at options for how we can set up a Layered "no match" strategy. Ideally I want to provide different messaging and count up the number of no matches, then when the counter exceeds a certain amount. offer a new message with a button to contact us / transfer.
The easiest way I could think of, was having a reusable task with some logic, but we don't want to have to set this on every digital menu or wait for input node. so I went into the User Input section for no match
I had a look at the expression builder but I don't think I can jump to a reusable task from there, I also couldn't find a way to make no match go to a reusable task by default at a global level.
Is this a possible feature or how would we best handle this in a digital bot flow (text based)
#ConversationalAI(Bots,AgentAssist,etc.)
------------------------------
Brady
------------------------------