Zapme allows you to configure the name, position, or department of the customer service representative and insert this identification into the message field of WhatsApp, WhatsApp Business, or another editable text field active on the device.
With Zapme, you can standardize customer service communication and make it clear who made each contact. The app helps differentiate representatives, positions, or departments, speeding up the inclusion of this identification in the conversation text.
You save an identification, choose simple formatting options, and use the floating Z button to insert the text when you want. The user controls when the identification will be inserted: the action happens when tapping the Z button.
The app offers formatting options such as line breaks, bold, italics, and frames. There is also the "Send automatically (BETA)" option, which inserts the identification at the beginning of the already typed message and attempts to activate the send button identified on the screen.
Zapme does not have official integration with WhatsApp, WhatsApp Business, Meta, or any other service. It works through the Android Accessibility Service to interact with editable fields on the active screen.
USING THE ACCESSIBILITY SERVICE
Zapme uses the Android Accessibility Service to display a floating Z button over other applications and insert the user's saved ID into an editable field in the active window.
The service is configured to receive the accessibility events typeViewFocused and typeWindowStateChanged. The code does not limit the service to specific packages, so it was not possible to confirm from the analyzed code that it only monitors WhatsApp or WhatsApp Business. The onAccessibilityEvent method does not perform its own processing of these events.
When the user taps the floating Z button, the service temporarily accesses the active window via rootInActiveWindow, traverses the AccessibilityNodeInfo tree, and looks for an editable field. First, it tries to identify the editable field in focus; if it does not find it, it looks for the first available editable field.
In standard mode, Zapme executes performAction with ACTION_FOCUS and ACTION_SET_TEXT to populate the editable field with the saved name, job title, or department, replacing the field's current text. When the “Send automatically (BETA)” option is enabled, the service locally reads the current content of the editable field, inserts the saved identifier at the beginning of the text, adjusts the selection with ACTION_SET_SELECTION, executes ACTION_SET_TEXT, and then traverses the interface to look for a send button by text, content description, or identifier containing terms such as “send” or “enviar”. If found, it executes ACTION_CLICK.
Zapme can run in the background while the Accessibility Service is active, displaying the floating Z button when there is a saved identifier and the option to hide the button is not checked.
The content accessed from the screen is temporarily used and processed locally to populate the editable field or, in BETA mode, prepare and attempt to send the message. The app only stores locally the saved name, formatting preferences, acceptance of the accessibility explanation, and preference to show or hide the Z button. The analyzed code does not declare internet permission, does not contain network integrations, and does not transmit content to servers. The analyzed code does not collect, share, or sell data.
The user can disable the service at any time in the Android accessibility settings.
Zapme inserts the agent's ID in the message field.