Connect a supported WhatsApp account through QR for practical contact and group routing, or use Meta Cloud API for approved business messaging workflows. Route conversations to shared inboxes, email, Slack, CRM systems, webhooks, automation and other supported destinations.
Use a supported QR session or Meta Cloud API setup.
Send messages where the right people already work.
Continue conversations through inbox or automation workflows.
QR connects a supported WhatsApp account for practical contact, group and team-routing workflows. Meta Cloud API connects supported WhatsApp Business messaging governed by Meta templates, conversation rules and business requirements.
Scan a QR code to connect a supported WhatsApp account. This option is useful for forwarding to contacts and groups, shared visibility and practical team routing.
Connect supported WhatsApp Business messaging through Meta Cloud API for approved templates, webhooks, automation and supported reply handling.
Automatically route supported messages to the people, channels and systems that need them instead of manually forwarding each conversation.
Route supported messages into sales, support, dispatch, booking or operations groups.
Create searchable message copies, shared inbox alerts and email-based support workflows.
Route sales, support and operational alerts into the Slack channels your team monitors.
Pass supported WhatsApp events into CRM, ticketing, reporting or custom applications.
Use n8n, Make.com or custom logic to classify, route, notify and respond where supported.
Send one important event to a group, email archive, Slack alert and backup workflow.
Send urgent WhatsApp activity to a normal phone number as a supported SMS alert.
Notify an owner, manager, assistant or backup phone when important WhatsApp messages arrive.
WhatsApp is not only a source. Supported rules can take an incoming SMS from Android, iPhone or Twilio and route it into a connected WhatsApp contact or group so the team can see it where they already communicate.
Notify a specific person when an important text reaches the business number.
Share selected SMS with sales, support or operations teams.
Supported WhatsApp conversations can appear alongside SMS activity in the AutoForward Text dashboard. Give teams visibility, preserve context and reply through available channel-specific workflows.
Monitor supported SMS and WhatsApp activity from one dashboard.
Reply from the inbox or connected workflow when the channel and connection support it.
Review recent supported messages before responding or handing the conversation to a teammate.
Practical account, contact and group routing based on supported QR connections.
Business messaging, webhook and reply handling governed by Meta requirements.
Connect the account, choose a source and destination, apply any routing conditions, then test the workflow before relying on it.
Use the supported QR or Meta Cloud API connection process.
Select a group, email, Slack, webhook, automation, SMS, phone or multiple routes.
Use available contacts, keywords, schedules and filters to control forwarding.
Send a test message, confirm the destination and watch for forwarding loops.
Route customer messages to a shared inbox, support group, email or Slack.
Notify the sales team or manager when a new WhatsApp enquiry arrives.
Send booking messages to the person or group responsible for scheduling.
Route vendor updates, driver messages and confirmations to operations.
Give multiple people visibility instead of relying on one account owner.
Create searchable email or webhook records of selected message activity.
Use a supported QR sender or an applicable approved Meta Cloud template.
Connection type, destination and message format can affect what a WhatsApp workflow supports.
Visit the Help CenterChoose the WhatsApp connection option in your dashboard. Supported setups can connect through a QR-based session or Meta Cloud API, depending on the account and workflow you use.
Supported incoming WhatsApp messages can be routed to destinations such as another phone, a WhatsApp contact or group, email, SMS, Slack, webhooks and multiple destinations.
Yes, supported QR-connected workflows can route messages into selected WhatsApp groups. Group capabilities can vary by connection type.
Yes. In supported WhatsApp-to-email workflows, you can reply from Gmail, Outlook, Microsoft 365, Apple Mail or another compatible inbox. AutoForward Text processes the email response and routes it through the connected WhatsApp account to the original conversation. Reply capabilities depend on the connection type and WhatsApp messaging rules.
Yes. Supported routing rules can take incoming SMS and send the message into a connected WhatsApp contact or group workflow.
Supported WhatsApp message events can be passed to webhooks, n8n, Make.com or your own systems for routing, classification and other business actions.
Media handling can vary by WhatsApp connection and destination. Confirm the supported message types for your setup before relying on media forwarding.
No. Forwarding copies or routes message content. A destination does not automatically become a native synchronized WhatsApp conversation, and reply support varies by workflow.
Connect a supported WhatsApp account and route important messages to groups, email, SMS, Slack, webhooks and the team workflows that need them.
