Client Accounts
Route recognized client contacts to the appropriate account team.
Turn Client Messages Into Shared Agency Workflows
Route supported client texts, WhatsApp conversations, campaign enquiries and missed-call activity to account teams, shared inboxes, Slack, CRM systems and automation—without leaving every conversation on one employee’s phone.
Client RoutingShared InboxAccount TeamsCampaign Workflows
Share client visibility
Move supported conversations beyond individual phones.
Separate accounts
Create distinct routes for clients, campaigns and services.
Connect delivery teams
Alert account, creative or technical owners as needed.
Agency communication
Keep Client and Campaign Messages With the Team Responsible for Delivery
Agencies often manage multiple client numbers, campaigns and internal specialists. Routing helps preserve ownership without forcing every message through one account manager.
Campaign Leads
Send supported campaign enquiries to sales or lead-management workflows.
Creative Requests
Make selected feedback and asset messages visible to delivery teams.
Client Support
Separate urgent service requests from routine account communication.
Multi-client routingExplore Rules & Auto-Replies
Create Clear Routes for Each Client, Campaign and Service
Use supported contacts, source channels, keywords and schedules to connect incoming communication with the correct account owner or shared destination.
Create dedicated destinations for key clients and retained accounts.
Route campaign keywords and source numbers to matching lead workflows.
Escalate selected service issues to account and delivery owners together.
Shared client context
Reduce the Risk of Client Messages Living With One Person
A shared, permissioned workflow can help preserve communication visibility during leave, staff changes and busy campaign periods.
Continuity across the team
Keep supported client context available to authorized colleagues.
Clear ownership
Use routes and destinations to show which team should act next.
Forwarding destinations
Bring Client Communication Into Your Agency Stack
Route supported messages to the collaboration, account-management and automation systems your team already uses.
Shared Inbox
Review supported conversations from a web dashboard.
Create searchable alerts in individual or shared inboxes.
Slack
Notify the right team channel when selected messages arrive.
Route supported alerts into connected WhatsApp workflows.
Another Phone
Forward priority communication to an owner or duty phone.
CRM or Business System
Add supported events to customer and operational records.
Webhooks & APIs
Pass available event data into your own applications.
Automation & AI
Trigger n8n, Make.com, Zapier or custom logic.
Example workflow
From Client Message to Account-Team Action
Keep the route simple enough that account ownership remains obvious to everyone involved.
1
Client Messages
A supported message reaches an agency-managed channel.
2
Rule Matches Context
Available client, source, keyword or schedule information selects a route.
3
Account Team Is Alerted
The configured inbox, Slack or phone destination receives the event.
4
Delivery Is Coordinated
The team follows up and records context in its approved system.
Client data governance
Respect Client Boundaries Across Shared Workflows
Agencies should configure access, retention and destinations separately where contracts, confidentiality or account boundaries require it.
Separate client access
Do not expose one client’s messages to another account team.
Review contractual duties
Follow client agreements for data handling and retention.
Control offboarding
Remove former staff and rotate credentials promptly.
Confirm sender consent
Use lawful, permission-based outbound communication practices.
Agencies FAQ
Agency Client Messaging Questions
Capabilities vary by source channel, country, permissions, destination and integration configuration.
Discuss Your WorkflowWhich AutoForward Text channels can a agency team connect?+
Available options include supported Android phones and SIMs, virtual phone numbers, Twilio and WhatsApp configurations. Choose the source based on whether you need to retain an existing number or add a cloud channel.
Where can incoming messages be forwarded?+
Supported events can be routed to email, another phone, Slack, WhatsApp, the AutoForward Text inbox, webhooks, APIs and connected business workflows.
Can routing rules send different messages to different teams?+
Yes. Supported rules can use available sender, contact, keyword, schedule and source information to select destinations and follow-up actions.
Can the team reply to forwarded messages?+
Supported inbox, email, WhatsApp and gateway configurations can provide reply workflows. Availability depends on the source channel, destination and permissions.
Can incoming communication be connected to a CRM or business system?+
Supported message events can feed connected systems through available integrations, webhooks or APIs. The exact fields and actions depend on the destination configuration.
Can AutoForward Text forward missed-call activity?+
Supported Android and virtual-number setups can make missed-call records visible in team workflows. Available call data depends on the channel, device and permissions.
Does forwarding remove our privacy or consent responsibilities?+
No. Your organization remains responsible for lawful access, consent, privacy, retention, carrier and local communication requirements.
Does an Android source phone need to remain online?+
Yes. Device-based Android forwarding requires the phone to remain powered, connected and allowed to run in the background. Cloud channels do not rely on that Android device.
Connect agency communication
Give Client Messages a Clear Route Into the Agency.
Keep supported conversations visible to the account and delivery teams responsible for acting on them.