Route customer SMS, on-call escalations, delivery pings, and shared 2FA codes into a team channel your whole team monitors. Install Re:Text on the iPhone receiving these SMS, add Slack/Teams/Discord as a destination with the channel's webhook URL, and configure filters to keep noise out. The team channel becomes the single source of truth for SMS-based signals.
When one person's iPhone is the choke point for critical SMS — customer support numbers, on-call rotations, delivery services — the team is fragile. That one person becomes indispensable: if they miss a message, are asleep, or off duty, the signal is lost.
The fix is simple: get the SMS into a shared team channel that multiple people watch. Slack, Microsoft Teams, and Discord all have Incoming Webhooks that make this straightforward with Re:Text.
Common team SMS scenarios
🎧 Customer support inbox
Customer SMS arriving on a support phone need visibility for the whole support team, not just whoever holds the phone.
Setup
Slack → #customer-support channel
Filter: sender phone numbers of known customers, or all incoming SMS
📟 On-call escalation
PagerDuty and Opsgenie send critical SMS to on-call engineers. Route those into the engineering channel so the team sees them too.
Setup
Slack → #ops-oncall channel
Filter: keyword ALERT, P0, P1, or PagerDuty shortcode
📦 Delivery notifications
Business deliveries (equipment, samples, supplies) need to reach the operations team, not stay on one purchasing manager's phone.
Setup
Teams → Logistics channel
Filter: carrier shortcodes (UPS, FedEx, USPS)
🔐 Shared 2FA codes
Verification codes for shared team accounts (analytics, ad platforms, tools) need to be accessible to multiple team members.
Setup
Slack → #team-access private channel
Filter: keyword code, OTP, verify
💬 Field team check-ins
Sales reps, field engineers, and remote workers texting a central number should reach coordinators without delay.
Setup
Discord → #field-updates channel
Filter: sender numbers of field team
🏥 Patient / client appointment reminders
Practices receiving appointment confirmations via SMS need coverage across staff.
Setup
Teams → Reception channel
Filter: keyword appointment, confirm, reschedule
Which team tool to pick
| Feature | Slack | MS Teams | Discord |
|---|---|---|---|
| Setup complexity | Easy | Moderate | Easy |
| Notification reliability | Excellent | Excellent | Good |
| Cost for small teams | Free tier limited | Free tier available | Free unlimited |
| Enterprise features | Excellent | Best | Limited |
| Third-party integrations | Extensive | Growing | Community bots |
| Compliance certifications | SOC 2, HIPAA | SOC 2, HIPAA, more | Limited |
General guidance:
- Slack — best default choice for tech teams, startups, and mid-size companies.
- Microsoft Teams — best for enterprises already on Microsoft 365.
- Discord — best for gaming, community, and startup teams with limited budget.
- Mattermost — best if data sovereignty or self-hosting matters. See our Mattermost guide.
Setup: route SMS to your team channel
- On the iPhone receiving the SMS you want to share (support phone, on-call phone, ops phone), install Re:Text SMS Forwarder.
- Create a Slack Incoming Webhook (or Teams, Discord — same pattern) pointing at your team channel. See our destination guides:
- In Re:Text, add the destination and paste the webhook URL.
- Configure filters to route only relevant SMS (see next section).
- Optionally add schedules so on-call SMS only fire during business hours.
- Test with a real SMS and confirm it appears in the team channel.
Filters: avoiding alert fatigue
Best practices for filter design:
- Start with the most restrictive filters and loosen over time. It's easier to add matching SMS than to remove noise.
- Prefer sender-based filters over keyword filters. Sender IDs are more reliable — keywords catch too much.
- Use separate destinations for separate severity levels. Critical alerts to a channel that pings; nice-to-know SMS to a channel that doesn't.
- Add schedules for non-24/7 operations. Sales team SMS during business hours, on-call escalations 24/7.
- Test filters before enabling. Send yourself SMS matching and not matching each filter case.
- Review monthly. Filter effectiveness drifts as your business evolves.
Advanced: multi-severity routing
Teams with 24/7 operations often need tiered channels:
Tier 1 — Critical (wake someone up)
P0 outages, high-value customer issues, security incidents.
- Destination: Slack #ops-alerts with @channel notifications
- Filter: keywords
P0,DOWN,CRITICAL, sender = PagerDuty - Schedule: 24/7
Tier 2 — Urgent (during on-call hours)
Warnings, high-priority customer requests, expected but not immediate.
- Destination: Slack #ops-warnings
- Filter: keywords
P1,WARN, sender = monitoring shortcode - Schedule: On-call hours + 30 min buffer
Tier 3 — Informational (business hours only)
FYI, low-priority SMS, batch summaries.
- Destination: Slack #ops-info (no @-mentions)
- Filter: everything else matching Ops sender pool
- Schedule: Business hours only
Team-wide setup patterns
One central phone forwards to all
Best when a single company-owned iPhone receives all customer SMS. That phone has Re:Text installed, forwarding to team channels. Individual team members' phones don't need Re:Text at all.
Multiple team members with individual forwards
Best when each team member's own iPhone might receive relevant SMS (on-call rotations, sales calls). Each team member installs Re:Text on their iPhone and forwards to the shared team channel using the same webhook URL.
Hybrid: shared channel + personal filters
Team members forward filtered SMS to a shared team channel using the shared webhook, but also have personal destinations (email, Telegram) for their own reference.
Frequently asked questions
Which team tool is best for SMS forwarding?+
It depends on what your team already uses. Slack has the largest ecosystem. Microsoft Teams integrates with the Microsoft 365 stack. Discord is popular for gaming, dev, and community teams. All three work equally well with Re:Text via Incoming Webhooks.
How do teams avoid alert fatigue?+
Use filters and schedules aggressively. Only forward high-priority SMS to team channels. Route lower-priority SMS to lower-priority channels or personal destinations. Set schedules for on-call hours.
Can multiple team members set up SMS forwarding?+
Yes. Each team member installs Re:Text on their iPhone and configures their own forwarding rules. All can post to the same shared team channel via the same webhook, or use their own personal webhooks.
Do I need Re:Text Premium for team SMS forwarding?+
The free tier supports one destination — enough for a single team channel. For multi-tier routing (critical + urgent + informational) you'll need Premium's unlimited destinations.
Is forwarding customer SMS to a team channel compliant?+
Depends on your industry and jurisdiction. Customer SMS may be subject to privacy regulations (GDPR, CCPA, HIPAA). Review your compliance requirements before routing customer content into shared channels — and consider using self-hosted Mattermost for regulated data.
What about high-volume SMS forwarding?+
Team chat platforms have webhook rate limits (Slack ~1/sec, Discord ~30/min, Teams ~4/sec). For very high volumes, distribute across multiple webhooks or filter aggressively.
Bring SMS visibility to your whole team.
Free forever with 1 destination. Premium unlocks multi-tier routing.
Download on the App Store