Enate logo
Enate
Create
Roadmap
Feedback
Feature Suggestion
464

    Boards

  • Feature Suggestion

  • Integration Suggestion

  • Documentation Suggestion

Powered by Canny

Feature Suggestion

You speak, we listen. Your voice is influenced at every stage of the Product Life Cycle. Submit feedback to the Product Team to help us release the highest quality for you
New Pattern : Custom fields population with email and files
Enate AI to automatically populate custom card fields on work items based on files and emails available on that work item.
5
·
Enate AI
Email classification AI - to understand Category 2 and if nothing on Category 3 - use Category 2 + Triage as a default category, rather than defaulting it to connector routing
As a user working on ticket, I would like to have an incoming email classified based on just category 2 and if it does not identify anything in Category 3, then it should make sure it is falling under identified Category 2 Triage bucket Example: we are having offices as cat 2 So the incoming can have the information of Cat 2 - but doesn't real have the value of Cat 3 So to default it - we should consider a Cat 2 Triage if it is defined and use that to categorize, rather than default it to Connector level triage
2
·
Enate AI
Powered by Canny