Taskrouter expressions need the ability to invert conditions
Taskrouter expressions are a great concept that allow more dynamic routing not constrained to a traditional hierarchy, while also reducing the need for infrastructure. The idea is great: set up your routing rules and filters, and you're up and running.
The implementation however, omits features severely limiting its usefulness.
I have a number of workers. Those from department A have
@example.com emails, but those from department B use misc domains without any standard convention.
I can easily make a queue for department A like so:
email CONTAINS 'example.com'
However, making a queue for department B workers is currently impossible, as there's no way to invert the rule. These examples do NOT work:
NOT (email CONTAINS 'example.com') !(email CONTAINS 'example.com') email NOT CONTAINS 'example.com'
I feel like the omission of an invert operator is a gross oversight.
Is there any rhyme or reason over this omission? Would you agree Twilio needs to add this feature?
- 83 All Categories
- 19 SIGNAL 2021
- 376 Product Discussions
- 7 Community - Announcements
- 2 Changelog
- 4 Forum UI Updates
- 8 Welcome Guide
- 6 Community - Events
- 2 Twilio Relay Developer Conference 2021 Mega Thread
- 1 External Community Events
- 25 Inspiration
- 17 Community - Other Discussions
- 1 Community- Twilio Startups