The core purpose of AutoForward Text is to automatically forward text messages. It can forward SMS, WhatsApp messages, call logs, and app notifications to email, another phone, Slack, or other supported destinations, helping users avoid missing important messages. The official description states that it supports iOS and Android, that setup takes about 2 minutes, and that it can be canceled at any time.
Main capabilities include:
- Unified inbox and replies: manage received SMS and WhatsApp conversations in one dashboard, and reply without switching between multiple devices.
- Message forwarding automation: automatically forward SMS, MMS, calls, and app notifications to email, another phone, Slack, and other supported destinations.
- Smart rules and auto-replies: control which messages are forwarded through contacts, keywords, schedules, and filters, and automatically reply when appropriate.
- WhatsApp forwarding: after connecting WhatsApp, route received conversations to email, workflows, and connected business tools.
- Call analytics and insights: track missed calls, call activity, and important communication events.
- Slack, Webhooks, and integrations: send received communications to Slack, APIs, Webhooks, and automation platforms without changing how the original messages are received.
In terms of usage, the official website provides a three-step process:
- Create an AutoForward Text account and access the web dashboard.
- Install or connect a phone: Android users install the AutoForward Text app; iPhone users can configure Apple Shortcuts; WhatsApp and Twilio can also be connected in relevant scenarios.
- Start forwarding: choose where received messages should be sent, including email, another phone, Slack, or other supported destinations.
In addition, the official description also introduces how to connect WhatsApp to workflows: through WhatsApp QR code connection or the Meta Cloud API, route received conversations to email, Webhooks, automation platforms, CRM systems, and AI agent workflows. For users who want to keep their existing phone number, they can use an Android phone with an existing SIM card to turn it into an SMS gateway, forward received text messages, send messages through the phone, and connect the number to email, Webhooks, CRM systems, and automation workflows.
Applicable scenarios include: business continuity (important comMessages can still stay connected when they reach another phone), customer support (routing customer messages to the people who need to respond), multi-device access, travel convenience, critical alert routing, and workflow automation and AI (triggering n8n, Make.com, or custom workflows when message events occur).
Official stated limitations and common questions:
- Device-based forwarding requires the connected phone to be powered on and able to communicate with the service. If the phone is offline, messages cannot be forwarded from that device until the connection is restored.
- iPhone users can configure supported forwarding workflows through Apple Shortcuts; for specific steps, refer to the iPhone forwarding instructions.
- Some connected communication channels can be replied to from the dashboard or through available reply/API workflows, depending on the channel.
- The web dashboard can centrally display supported SMS and WhatsApp conversation activity, making it easier to manage uniformly and connect to team workflows.
- An Android phone with an existing SIM card and phone number can receive SMS and expose these messages through Webhooks and APIs, while also supporting programmatic sending and replies.
- Received communications can be passed to automation platforms through supported Webhooks and APIs; automation or AI agents can process messages and, where supported, reply through the original channel.
- Account subscriptions and settings can be managed through the AutoForward Text dashboard.
The official information also mentions that the website uses optional analytics cookies from Google Analytics and Microsoft Clarity to understand website usage, and that basic website functionality can operate without these cookies.
Information such as pricing, specific billing plans, message volume limits, and platform compatibility details is not currently provided in the materials.
