EB Chat by EButler

What Happens When You Open the App for the First Time

The first screen after login shows a unified inbox. Messages from WhatsApp, Instagram, Messenger, and live chat all appear in one list. Each message is tagged with the source channel. A green dot indicates an unread message. Tapping a message opens a threaded view showing the full conversation history. The reply box sits at the bottom. You type a response, hit send, and it goes to the customer through their original channel. The app does not show which channel the reply will use—it just works. This is the core promise of an omnichannel inbox: one interface, many channels.

The onboarding process requires a business account. There is no option to use the app as a personal user. This is a B2B tool. The login screen asks for an email and password. Below that, a "Forgot password?" link. No social login options. The design is functional, not flashy. The colour scheme is blue and white. Icons are standard Material Design. The app feels like a utility, not a consumer product. That makes sense—it is built for customer support teams, not for casual chatting.

How Two Features Work Together: Inbox Threading and Channel Tagging

The inbox threading feature groups messages from the same customer across different channels. If a customer starts a conversation on WhatsApp and then follows up on Instagram, the app threads those messages together. The channel tag shows where each message came from. This is useful for context. A support agent can see the full history without switching between apps. The tagging also helps with reporting. The app can generate statistics on which channels generate the most messages. This is not mentioned on the Play Store page. It is an observation from the research. The threading and tagging work together to create a single customer view. This is the real value of the app—not just aggregating messages, but making them coherent.

However, there is a limitation. The app does not support voice messages or video calls. It is text-only. This might be a problem for businesses that use WhatsApp for voice notes. The app also does not integrate with email. It is focused on chat channels only. This is a deliberate choice, but it limits the app's usefulness for businesses that rely on email support.

Real-World Performance: What the Changelog Reveals

The Play Store changelog says "Fix issues and improve performances." This is vague. It does not specify what issues were fixed or what performance improvements were made. This is a common problem with SaaS apps. The developer, EButler Inc, is based in Qatar. The app is part of a larger ecosystem that includes EButler - Request Anything, EB Delivery, and Volante Dubai. The company has a presence on Crunchbase and LinkedIn. The app has been updated regularly, with versions like 5.00.4, 7.09.04, and 8.00.00. The latest version is 8.00.00. The app size varies between 56 MB and 80 MB depending on the version. There is no information about crash rates or user-reported bugs. The Trustpilot page for e-butler shows a 1.5/5 rating, with complaints about service disconnection and lack of support. This is a red flag. However, it is unclear if these complaints apply to the chat app or the broader EButler service.

The app's performance seems stable based on the version history. Regular updates suggest active development. But the lack of detailed changelogs makes it hard to know what has changed. Users are left guessing.

Permission Required: Storage Access for Media Sharing

The app requires storage permission to send images and files through the chat. This is standard for messaging apps. Without this permission, users cannot share photos or documents. The app does not request location or contact permissions. This is a positive sign for privacy. The data safety section on Google Play states that data is encrypted in transit. The developer also allows users to request data deletion. These are good practices. However, the app does share data with third parties, including personal information, photos, and videos. This is mentioned in the data safety section. Users should be aware of this before using the app for sensitive conversations.