Feature Requests

Desktop and Mobile Application for Mava
Pain Point: Currently, accessing and managing support tickets through a browser tab is limiting and inefficient—especially for teams who need to quickly triage and respond to tickets across multiple devices. It’s also easy to lose track of Mava among other open tabs, which disrupts workflow and response time. Goal: To improve responsiveness and workflow by having dedicated desktop and mobile applications with native notifications, faster access, and better multitasking support. Detailed Description: I’d like to request the development of native desktop (macOS) and mobile (iOS/iPadOS) applications for Mava. These apps would allow customer support agents to quickly view, assign, and respond to tickets without relying solely on a browser. Key desired features: • Background operation with minimized UI (especially useful on mobile) • Faster load times compared to the web app • Keyboard shortcut support on desktop • Ability to receive push notifications • Offline viewing or draft mode for writing replies • Support for multiple workspaces/accounts A native experience would not only make support agents more efficient but also help us avoid context-switching during busy support days. We believe this would significantly improve the overall user experience and help us stay more engaged with customer conversations. Please let me know if there’s any roadmap around this or if you’d be open to early beta testers if this is under consideration. Thanks a lot!
1
Option to exclude something from ticket views, chatbot builder automations etc.
Pain point: Currently, our system does not allow users to exclude specific categories or tags from their views and automations. This limitation makes it challenging to focus on relevant tickets, as users are often overwhelmed by information that does not pertain to their immediate needs or priorities. Goal: We would like to implement a feature that enables us to exclude tickets with certain categories or tags from their views. For example, a user should be able to create a view that only displays tickets from categories A, B, and C, while excluding all tickets from category X. This functionality will enhance the user experience by allowing for more tailored and efficient ticket management. Detailed Description: The proposed feature should include the following functionalities: 1. Exclusion Options: Users should have the ability to select specific categories and tags to exclude from their views. This can be implemented as a simple checkbox or dropdown menu in the view settings. 2. Dynamic Filtering: The exclusion criteria should dynamically update the view in real-time, ensuring that users only see the tickets that meet their specified requirements. 3. Automation Integration: In addition to views, the exclusion feature should also be applicable to automations. Users should be able to set up automation rules that ignore tickets with the excluded categories or tags, streamlining their workflow and reducing clutter. Benefits • Increased Efficiency: By excluding irrelevant tickets, we can focus on what matters most, improving our productivity. • Enhanced Customization: we can tailor our views to suit our specific needs, leading to a more personalized experience. • Streamlined Workflow: Automations that respect exclusion criteria will help in managing tasks more effectively, reducing the likelihood of overlooking important tickets.
2
Load More