Slack notification messages are configured individually on each routing path. Admins with routers that have many paths, such as 25 or more, who need to send the same Slack message at the end of each path have to configure and maintain that message in every path separately. Any time the message needs updating, every path must be edited individually. There is no way to define a Slack notification template once and reference it across multiple paths or routers.

Admins should be able to create named Slack notification templates and apply them to individual paths or routers by reference, so that updating the template propagates the change everywhere it is used.

At scale, path-level Slack notification configuration becomes unmanageable. A template system eliminates the need to touch every individual path when a message needs to change, reduces the risk of inconsistency across paths, and brings Slack notification management in line with how other reusable components work in well-designed routing tools.