Hello team,
@Darshan R @Rithvik Sridhar @Khalees V
I'm creating this request on behalf of our customer Ciena.
Firstly, thank you for delivering the long-requested enhancement in the AI Draft module related to tag selection. However, during testing, They’ve encountered a critical limitation that is affecting their ability to fully leverage this functionality.
Key Observation : The new AI Draft module does not allow them to use Any or All in parallel with the Exclude option. While this may appear minor, it significantly impacts how they use tags during AI Drafting, especially because this combined filtering capability was available in the legacy Auto Respond module, and they have built our entire tagging structure and content strategy around it.
Real-World Use Case :In their NMS product line, they use a layered tagging structure - e.g., L0, L1, L2, L3 - and each clause is mandatorily tagged with one of these levels along with other contextual tags such as technology (AIPA-SM, etc.) and functionality. Let’s say they want AI Draft to pick:
- Clauses tagged as either
L0 or L1 (i.e., using Any), - But explicitly exclude those tagged with
AIPA-SM.
In the current version of AI Draft:
- Using
Any brings in AIPA-SM tagged clauses as well, which we they to avoid. - Using
All isn't practical because the exact tag combinations vary and would not work across different sections. - Using
Exclude alone forces us to over-specify, which is unscalable with our large clause base and would require listing numerous tags we want to avoid.
Previously, with Auto Respond, this wasn’t a problem — They could combine include and exclude logic easily. This flexibility was crucial in enabling targeted, context-aware responses across various RFP sections.
Impact :
- Their existing tag nomenclature becomes less effective, impacting tagging hygiene.
- We’re unable to scale or automate response drafting with confidence for high-volume or multi-tag filtered content.
- The AI Draft Instructions field is also being ignored, even for basic prompts, reducing control over tone and context.
Request :They strongly urge our product/tech team to reinstate the ability to combine Any or All with Exclude, similar to how it worked in the Auto Respond module (see image below). This would restore critical flexibility and enable us to maximize the value of the AI Draft feature with precision and scalability. Also, some other tag filters like 'Only' and 'Not Tagged' are entirely missing.
Thanks!
Kindest regards,
Sathish
Sr. Customer Success Manager (APAC & EMEA)
