Skip to main content
gmerrill
Employee
March 15, 2024
4. Future Consideration

Proactive tracking for users that block a bot

  • March 15, 2024
  • 8 replies
  • 140 views

Raising this on behalf of clients who need to be notified whenever a user blocks a bot.

 

We need a feature that detects that the bot is being blocked and either alerts an administrator or generates a report that can power an automated email to get those blocking users back on the bot.

This feature should ensure that it checks the roster to stay up to date with current employees and do a check so that users that unblock the bot on their own get removed from the report.
 

8 replies

gmerrill
gmerrillAuthor
Employee
March 15, 2024

@ewebb I’ve made this post to push visibility for the request you made on this post: 


If the Incomm team can upvote this feature request the product team can work it into the roadmap.

kyril.remillard
Community Manager
March 22, 2024

Thank you for submitting your Product Idea. We understand this is not currently supported, we appreciate your feedback and will consider it in the future as we continue to build and improve our product. Please keep up to date with our latest release notes here.

kyril.remillard
Community Manager
March 22, 2024
1. New4. Future Consideration
hundleymf
Inspiring
January 31, 2025

Any update on this?

Human by Day, Chatbot Whisperer by Night! 🤖
michael.stephens
New Participant
August 20, 2025

Any update on this future consideration? We have a few processes that rely on bot notifications and it would be very helpful to have this feature.

hundleymf
Inspiring
August 21, 2025

As we were just onboarded into the Webhooks Limited Preview program and plan to send more notifications through our bot—especially ones that need people to take action, like approvals—we would like to have a way to track and see who has the bot blocked as well. 

Human by Day, Chatbot Whisperer by Night! 🤖
Community Manager
February 24, 2026

We are currently planning to include this in our H1 roadmap.

Known Participant
April 1, 2026

@sagarika :Any update on this feature?