🧑‍💼 WHO: Ayush Bisen ⚙️ WHAT: Remove the push notification Player ID before team member logout. Re-register the Player ID with the owner account after logout. Ensure logout continues even if notification cleanup fails. 🚨 WHY: To prevent incorrect notifications after switching accounts.

🧑‍💼 WHO: POC ⚙️ WHAT: Implement backend API support for filtering broadcasts by broadcast type, message type, and other criteria to enable the frontend to display filtered broadcast lists based on user-selected filter options. 🚨 WHY: Currently, the broadcast listing API does not support filtering by broadcast type (scheduled, sent, draft) or message type (text, image, video, template, carousel, etc.), forcing users to manually search through all broadcasts to find specific ones. This creates poor user experience when managing large numbers of broadcasts, makes it difficult to analyze specific broadcast categories, and wastes time scrolling through irrelevant results. Adding backend filter support will allow the frontend to implement filter UI that enables users to quickly find broadcasts by type, status, message format, or other criteria, significantly improving broadcast management efficiency and user productivity.

🧑‍💼 WHO: POC ⚙️ WHAT: Expand the "Choose Content Type" menu in Flow Builder to include additional node options beyond the current nine types (Text Button, Media, List, Single Product Message, Multi Product Message, Single AI Message, Template, WhatsApp Pay, Date and Time) to provide users with more functionality and ease of use when building flows. 🚨 WHY: The current content type menu has limited options that may not cover all the messaging and automation capabilities users need when building WhatsApp flows, forcing users to work around limitations or use inappropriate node types for their use cases. Adding more node options such as delay nodes, condition nodes, variable assignment, webhook calls, API integrations, form messages, location requests, contact card sharing, or other WhatsApp-supported message types will provide users with more powerful flow building capabilities, reduce workarounds, enable more complex automation scenarios, and improve overall user experience and product competitiveness.

🧑‍💼 WHO:POC ⚙️ WHAT: Create a compound index on the contacts collection for { userId: 1, settingId: 1, createdAt: -1 } to optimize the faceted listing aggregation query that currently loads 204,738 documents and sorts them in-memory, taking 1,842ms. 🚨 WHY: The contact faceted listing query filters by userId and settingId using an existing index, but then must load all 204,738 matching contact documents into memory to sort by createdAt because the index does not include the sort field, causing massive memory consumption, slow query execution taking nearly 2 seconds just to return 10 results, and contributing significantly to the contact-related libuv pool blocking issues seen in profiling. Adding createdAt to the compound index allows MongoDB to return pre-sorted results directly from the index without loading all documents into memory, reducing query time from 1.8 seconds to milliseconds, eliminating memory pressure, and resolving a major contact performance bottleneck affecting list display and navigation

🧑‍💼 WHO: POC ⚙️ WHAT: Fix the validation error "No key provided for update" that appears when users attempt to change the country code in the phone number field while updating a contact. 🚨 WHY: Users cannot update contact phone numbers by changing the country code because the system displays "No key provided for update" error preventing the contact from being saved. This blocks a basic contact management operation and creates poor user experience where changing country code triggers validation failure instead of accepting the update. The error indicates either missing validation logic that checks required fields before allowing update, incorrect form state handling where the key/ID is lost when country code changes, API expecting a field that's not being sent, or client-side validation incorrectly rejecting the update request. Users need to be able to update contact country codes without encountering validation errors to properly manage contact information.

🧑‍💼 WHO: POC ⚙️ WHAT: Conduct comprehensive research into implementing voice calling functionality in Pabbly Chatflow including understanding technical requirements, server resource consumption patterns, bandwidth requirements, infrastructure costs, scalability challenges, and overall impact on existing server architecture and performance. 🚨 WHY: Need to understand whether adding voice calling functionality is feasible given current infrastructure, what server resources (CPU, memory, bandwidth, processing capacity) would be required, how voice calling would affect existing system stability and performance, what additional infrastructure investments would be needed, whether current servers can handle simultaneous voice calls plus existing webhook and API load, what latency and reliability implications exist, whether current database and caching systems would scale with call metadata, and what costs would be associated with implementing and maintaining voice calling at scale to make informed product decisions about feature feasibility and whether to pursue voice calling capability or focus optimization efforts elsewhere