Macro Handler

Macro Handler

Android Automation Platform

Support

Sign in with your Google account to submit a support ticket.

Checking your session status...

Protected support and trust

Support tickets are tied to account ownership

Why is Google sign-in required?Google sign-in protects ticket ownership, account security, and premium-access context.
Legal and privacy channelsLegal, takedown, and privacy requests can also be started from IP and Takedown Policy / Privacy Policy.
Operational statusFor incident and release updates, use System Status. Official support email: support@macrohandler.com.

Support and settings screens

Support flow matches in-app account and moderation surfaces

Profile settings, app settings, and moderation notifications show which product surfaces feed support requests. These are English 1.0.17 app screens.

Support: account, settings, and moderation source

The clean screenshot teaches users which account, settings, or moderation surface can feed a support request.

Clean profile settings screen
1AccountProfile and subscription details give the correct account context for a support ticket.
2SettingsApp settings, permissions, and device state clarify the support issue.
3ModerationReports, appeals, and block notifications connect to the same safety path as support.

Profile Settings

Profile settings screen

App Settings

App settings screen

Moderation

Moderation notifications screen

Support form learning map

Fill each field correctly before opening a ticket

Live form
Write the issue briefly
Bug, feature, account, or legal
Device model, Android version, affected screen, expected result, actual result, and screenshot link if available.
If an active ticket exists, a new ticket cannot be opened in the same lane.
Submit Ticket

Form usage discipline

What should the support form teach?

Category sends the ticket to the correct lane. Bug report, feature request, account/premium, legal takedown, and moderation appeal are not the same workflow.

The message should include device model, Android version, app screen, reproduction steps, expected result, and actual result. Missing context slows resolution.

After submission, the user should wait for the admin response in the same ticket lane and add a follow-up reply when needed. This avoids duplicate tickets and mixed support chains.

Correct categoryRoutes the ticket to the right team.
Evidence-based messageProvides reproducible issue context.
Single-lane trackingPrevents duplicate tickets for the same issue.