Bugs

The SALLAH event for abandoned cart notifications is sending the template message to customers repeatedly every few seconds, instead of just once. This issue is causing the same message to be sent over and over again on WhatsApp, potentially causing inconvenience to customers and risking the number being blocked. Expected vs. actual results: Expected result: The abandoned cart template message should be sent to the customer only once, notifying them of the items left in their cart. Actual result: The template message is sent repeatedly every few seconds, resulting in multiple WhatsApp messages being sent to the customer. Steps to reproduce: Trigger an abandoned cart event on the platform. Monitor the WhatsApp messages received by the customer. Observe that the same template message is sent repeatedly every few seconds. List of affected platforms: ACC1677 ACC1741 Visual proof/screenshot: https://drive.google.com/file/d/13Q8tn0TU-oCzW50OU6ffDvfWbM9201Ue/view?usp=sharing https://drive.google.com/file/d/1IQW8pcS9m9fTYMLD7YzYyNXJof8GV9SW/view?usp=sharing

Issue Description: We have identified a significant issue on our platform where customer-sent photos fail to display for our team members. This bug persists until the cache is manually cleared. Impact: This bug severely disrupts our workflow, leading to delays in customer service and potentially impacting customer satisfaction. It is imperative to resolve this issue promptly to ensure the smooth operation of our platform and uphold our commitment to delivering exceptional service to our customers. Proposed Solution: I recommend conducting a thorough investigation into the root cause of this issue. This may involve examining the photo upload and caching processes to identify any discrepancies or malfunctions. Once the cause is identified, implement the necessary fixes to ensure that customer photos display correctly for team members without requiring manual cache clearance. Urgency: Given the critical nature of this bug and its direct impact on customer service, I urge the development team to prioritize this issue and allocate resources accordingly for swift resolution.

Summary: The customer sent a WhatsApp campaign to a label containing 941 customers. After the campaign finished, the number of customers with the label was reduced to 935 customers. Expected vs. Actual Results: Expected Result: The number of customers with the label should remain 941 after the campaign. Actual Result: The number of customers with the label was reduced to 935 after the campaign. Steps to Reproduce: Create a label with some customers. Send a WhatsApp campaign to the label. After the campaign finishes, check the number of customers with the label. Observe the discrepancy in the customer count. Environment: Browser: Chrome Operating System: Windows 10 Account Information: ACC Number: 911 ACC Name: mayamurt ACC ID: 213 Visual Proof and Screenshots attached

Despite diligently activating notifications in both the platform settings and the mobile application, users continue to face a stubborn issue where notifications remain elusive. This issue persists whether they access the platform via a PC browser or through their mobile phones. Steps to Reproduce: On Browser: Navigate to settings. Proceed to profile settings and select the notification section. Enable the desired notification preferences. Allow browser push notifications. Despite completing the above steps, notifications fail to trigger for messages sent, conversations created, or assignments. On Mobile App: Access settings within the mobile app. Navigate to the notifications section. Enable the desired notification preferences. Despite activating notifications, messages sent, conversations created, or assignments fail to generate notifications. Environment: Browser: Exhaustive troubleshooting measures applied, including clearing cache and history, and testing in incognito and inprivate windows. Tested with: 1. Google Chrome. 2. Microsoft Edge. PC Operating System (OS): Windows. Mobile Operating System (OS): iOS. Android. Affected Accounts: Account: ACC748, ID: 1490. Account: ACC1877, ID: 8453.

Description: Problem: After uploading a contacts file on the platform, there is a significant delay in updating the data of existing contacts. The upload process has been ongoing for approximately 24 hours without completion. Symptoms: Inability to update existing contact data for an extended period. Import section displays a persistent message: "Import is in progress in the background," obstructing any action. The file status remains pending with no data read, indicating a delay in processing. Here is a video to further illustrate the issue : https://drive.google.com/file/d/1g6m8Bsy9hgHPc7spkmOwhfwBHfoZpm_B/view?usp=sharing

Problem: The business chat platform experiences frequent crashes, resulting in unresponsiveness and making it challenging to handle customer inquiries and contact customers. Users encounter a message stating, "This page isn't responding," accompanied by platform freezing. Symptoms: Regular crashes of the business chat platform. Occurrence of the message, "This page isn't responding," during usage. Complete platform freeze, rendering it unusable for customer interactions. Impact: Disruption in handling customer inquiries affects customer service quality and responsiveness. Inability to contact customers promptly may lead to dissatisfaction and loss of business opportunities. Reduced productivity and efficiency for users due to frequent interruptions and platform freezes. Expected Behavior: The business chat platform should operate smoothly without frequent crashes or unresponsiveness. Users should be able to handle customer inquiries and contact customers without encountering platform freezes or error messages. Urgency: Given the critical impact on customer service and business operations, resolving platform stability issues is of utmost importance and should be addressed with high priority to minimize disruptions and maintain user satisfaction. Accounts currently experiencing this issue: ACC1295

When attempting to load additional conversations within the module, the option to load more conversations is obstructed by an unnecessary white box positioned at the bottom of the conversations list. This obstructs the view of the load of more options and disrupts the user experience. Expected Outcome: The expected outcome is that there should be no presence of a white box at the bottom of the scrollable conversations list. All elements within this part of the module should be fully visible without any interruptions, allowing users to seamlessly access and load additional conversations as needed. Additional Information: This issue occurs consistently whenever attempting to load more conversations within the module. The presence of the white box obstructs user interaction and hampers the functionality of the conversation module. Ensuring the removal of this white box will significantly enhance user experience and streamline the process of accessing conversations within the module. Steps to Reproduce: Access the Conversation Module within the platform. Attempt to load additional conversations beyond the visible list. Observe the presence of the unnecessary white box obstructing the view of the load more option. Impact: The presence of this issue negatively impacts user experience and functionality within the Conversation Module. It leads to frustration and difficulty in accessing additional conversations, potentially hindering user productivity and satisfaction with the platform. Priority: Given the impact on user experience and functionality, this issue should be addressed with high priority to ensure optimal performance of the Conversation Module.

Description of the Problem: At times, when users send images or documents through our omnichannel platform, these attachments fail to appear on the desktop interface. However, it's worth noting that these attachments are visible without any issue on the mobile application of our platform. Expected Behavior: Images and documents shared by users should consistently appear on both the desktop and mobile versions of our omnichannel platform, ensuring a seamless user experience across all devices. Impact: This bug is affecting user experience and may lead to miscommunication or delays in workflow, particularly for users relying on the desktop version of our platform. Proposed Solution: We need to investigate and address the root cause of this issue promptly to ensure consistent performance across all platforms. This may involve debugging the codebase, testing different scenarios, and implementing necessary fixes to ensure proper rendering of images and documents on the desktop interface. Important Note: But sometimes when we clear all cookies its work normally.

ACC Number : 1812 ACC ID : 7100 ACC Name : wbj-sa Issue: Users encounter a problem in the mobile app where opening conversations displays a grey screen instead of messages. Scrolling down doesn't load conversations, and grey screens persist in the background. Expected Behavior: Opening conversations should promptly show messages without visual glitches. Scrolling through conversations should be smooth without encountering grey screens. Attachments: Google Drive Video https://drive.google.com/file/d/15dIySp9T9MFlPkTYpIzfLQFkDlklow96/view?usp=sharing Screenshots (Attached) Steps: Log in. Open a conversation. Note the grey screen. Try scrolling down. Observe grey screens upon opening conversations. Additional Info: Platform: Mobile app App Version: Latest Version Frequency: Consistent Recent updates: No recent changes Error messages: No error messages displayed Impact: Severely affects user experience by hindering message access, leading to frustration and disengagement. Priority: High priority due to its significant impact on user satisfaction.

ID : 6548 NAME : خدمة عملاء مرسال للإتصالات والأجهزة الإلكترونية ACC NUMBER : ACC1773 Issue Description : المشكله تظهر حين تشغير اى بوت اخر غير الوحيد الذى عمل ما يقبل و يعرض رساله الخطا موضحا ان لا يمكن تشغير البوت نظرا لتخطى الحد الشهرى المسموح علما بان الحد الشهرى المسموح هو 5 سير عمل و كل الذى يعمل من سير العمل هو 1 فقط Expected Behavior : المتوقع وجوده ه تنفيذه هو ان البوت يكون متاح للعمل طالما لم يتم تجاوز العدد المحدد شهريا وفقا للتعاقد