Line Flagging vs. Throttling: What's the Difference?
What is Throttling?
Throttling is a preventative measure that Linq automatically applies when your response rate
drops below 15% over a 7-day period.
What happens during throttling:
- Your messages are intentionally delayed before sending (typically between 1-30 minutes)
- Messages still send, just slower than normal
- Calling is not affected and works normally
- This is temporary and reversible
Why it happens:
- Response rate dropped below 15%
- Sending too many messages without getting replies back
- One-way messaging patterns that look spam-like to Apple
How to fix it:
- Stop sending to contacts who aren't responding (remove after 2-3 unanswered messages)
- Make messages more conversational with open-ended questions
- Space messages 24+ hours apart
- Target 30-40% response rate on first messages
Recovery timeline: 3-7 days of improved messaging behavior
What is Flagging?
Flagging is a reactive measure that Apple applies when your line has been engaging in
spam-like behavior that throttling couldn't prevent.
What happens when flagged:
- Outbound messaging is blocked (messages fail to send)
- Calling is not affected and works normally
- Recovery requires intervention from Linq and Apple
- More severe than throttling
Why it happens:
- Response rate stayed below 15% despite throttling
- High-volume sends without engagement
- Spam reports from recipients
- Aggressive workflows that kept firing despite low engagement
How to fix it:
- Stop all outbound workflows immediately
- Linq works with Apple on recovery (you cannot fix this yourself)
- Review and fix your messaging approach during recovery
- May require line replacement if recovery fails
Recovery timeline: 24+ hours minimum (Apple controls timeline, can take longer)
Key Differences
| Aspect | Throttling | Flagging |
|---|---|---|
| Type | Preventative | Reactive |
| Severity | Warning sign | Critical issue |
| Messages | Delayed (1-30 min) | Blocked/Failed |
| Calling | Works normally | Works normally |
| Recovery | You can fix it | Requires Linq/Apple intervention |
| Timeline | 3-7 days | 24+ hours (varies) |
| Reversible | Yes, with behavior changes | Yes, but may need line replacement |
The Progression
Think of it this way:
Healthy Line →
Response rate drops →
Throttling (warning) →
Behavior doesn't improve →
Flagging (blocked)
Throttling is your warning sign that you need to change your messaging approach
before things escalate to full flagging.
What You Should Do
If you're being throttled:
- Act immediately to improve response rate
- You still have messaging capability (just delayed)
- Fix the behavior before it escalates to flagging
If you're flagged:
- Support will reach out once your line is flagged via email
- Stop all outbound messaging immediately
- Review workflows and messaging strategy during recovery
- Be prepared for potential line replacement if recovery fails
✅ Best practice: Monitor your response rate proactively and adjust your messaging
before throttling or flagging occurs.