SMS Automation - Auto Forward

Automation routines for your phone. Set a trigger, a condition and an action once — the app repeats the action automatically every time the trigger occurs. Build as many routines as you need; several can run on the same event.

HOW TO SET UP A ROUTINE

1. Trigger — an incoming SMS or MMS, a Samsung Chat+ (RCS) message, a messenger notification (KakaoTalk, LINE, WhatsApp, Telegram, Instagram) or a missed call.
2. Condition — a sender, a keyword, a number prefix, or every event.
3. Action — send an SMS to a number you set, or an app push to your own paired device (pair once with an 8-character code).
Turn each routine on or off any time. Every run is logged in Transfer History with a result notification.

TRIGGERS FROM THREE AREAS OF YOUR DEVICE

• Messaging — SMS and MMS
• Calls — missed calls from phone state changes
• App notifications — RCS/Chat+ and messengers
Routines keep running in the background, after a restart and in battery saver.

EXAMPLE ROUTINES

• Bank SMS arrives → push it to my tablet
• SMS contains "delivery" → SMS it to my work phone
• Missed call → send the caller's number to the phone I carry
• One message, two routines → SMS to my work phone and push to my tablet at once

FREE EVERY MONTH

• SMS → SMS routines: unlimited
• MMS, Chat+/RCS and messenger notifications → SMS: 10
• App push actions: 10
• Need more now? Watch a reward ad to top up instantly.

Routines and history back up to a local file.

WHY THESE PERMISSIONS ARE REQUIRED

A routine runs in three steps: detect the trigger → check the condition → execute the action. Without the permission for a step the routine cannot run; each permission is used only for that step. The app explains the purpose in-app before asking for SMS, call log or notification access.

1. RECEIVE_SMS — Detects the SMS trigger.
2. RECEIVE_MMS, RECEIVE_WAP_PUSH — Detect the MMS trigger (RECEIVE_WAP_PUSH is required for MMS on Android).
3. READ_SMS — Reads message and sender to check the condition.
4. SEND_SMS — Executes the SMS action.
5. READ_PHONE_STATE — Detects the missed-call trigger.
6. READ_CALL_LOG — Gets the missed caller's number (Android 10+ omits it from phone state broadcasts). Used only for missed-call routines.
7. READ_CONTACTS — Shows contact names instead of bare numbers.
8. POST_NOTIFICATIONS — Shows routine results and incoming app pushes.
9. RECEIVE_BOOT_COMPLETED — Re-arms, after a restart, the reminder to open the app so routines keep running.
10. REQUEST_IGNORE_BATTERY_OPTIMIZATIONS — Keeps routines running in battery saver or doze mode.
11. Notification Access — Required for the RCS, Chat+ and messenger triggers: Samsung Messages and Google Messages deliver RCS as app notifications, not SMS broadcasts. Notifications from apps that are not part of your routines are ignored — never stored or transmitted.

DATA HANDLING

• The SMS action stays entirely on your device: content, call logs and contacts are matched locally and sent straight to the number you chose. No server involved.
• The app push action reaches your other device over the internet: the message is relayed through Google Firebase, retained for up to 30 days after delivery, then deleted automatically. App push is not end-to-end encrypted.
• Why 30 days: so the receiving device can fetch the full text of a truncated alert or restore a missed one.
• No account required: Firebase anonymous authentication only — no email, phone number or Google account. Devices use a random installation ID.
• The app is supported by Google AdMob, which collects an advertising ID (AAID), IP address, approximate location (IP-based) and ad-interaction data to serve and measure ads.
• In the EEA, the UK and other applicable regions, a consent prompt (Google User Messaging Platform) is shown before personalized ads; if declined, non-personalized ads are served.

See the Data Safety section on the Play Store and our Privacy Policy for details.