> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuco.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Line Health & Apple Sending Restrictions

> What can restrict or ban a Tuco iMessage line, the warning signs, what Tuco does to protect you, and how to recover — plus how to avoid it.

**Apple can throttle or restrict your iMessage line if it behaves like a spam sender — most often from cold, high-volume, identical outreach to people you've never contacted.** A restricted line still *receives* messages and your existing conversations keep working, but Apple stops resolving **new / cold** outbound recipients, so messages to strangers start failing or downgrading. The fix is prevention: keep sends personalized, warmed-up, consented, and triggered — not blasted.

## What a restriction looks like

* Messages to **existing conversations** keep delivering normally.
* Messages to **new / cold** recipients start failing, downgrading to SMS, or silently not resolving.
* You may see a rise in `failed`/`fallback` statuses concentrated on one line.

## What causes it

Apple's spam systems react to sender *behavior*, not to Tuco. The main triggers:

* **Cold outreach at volume** — messaging many people who never opted in.
* **No warm-up** — a brand-new line sending at full volume on day one.
* **Identical, templated blasts** — the same message fired to a large list (this is why [iMessage should be triggered, not blasted](/guides/send-bulk-imessage)).
* **High daily volume** relative to the line's history.
* **Reports** — recipients marking messages as junk.

## What Tuco does to protect you

Tuco is built to keep lines healthy:

* **Per-line rate limits** and warm-up so one send can't torch a line's reputation ([rate limits](/features/rate-limits)).
* **Spam monitoring** that flags rising failure rates as risk before a ban ([spam monitor](/features/spam-monitor)).
* **Health checks** that detect a down or degraded line and route around it.
* **Availability checks** so you don't burn sends on non-iMessage numbers.

## How to recover

A restriction is not always permanent, but recovery is **not instant** and isn't guaranteed:

1. **Stop the risky sending immediately** — pause cold/high-volume campaigns.
2. **Reduce volume and warm up** — return to a low, personalized cadence.
3. **Clean your audience** — only message consented, opt-in contacts; honor every STOP.
4. **Contact support** ([support@tuco.ai](mailto:support@tuco.ai)) — we'll review the line and advise on next steps.

## How to avoid it in the first place

* **Personalize every message** — no identical mass blasts.
* **Trigger sends off events** (new lead, reply, stage change) rather than dumping a static list.
* **Warm up new lines** gradually; add lines to scale instead of pushing one harder.
* **Only message people who opted in**, and honor opt-outs fast.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why was my line restricted by Apple?">
    Almost always sending behavior that looks like spam — cold, high-volume, or identical messages to people you've never contacted. Apple restricts the line's ability to resolve new/cold recipients while leaving existing conversations working.
  </Accordion>

  <Accordion title="Is a restricted line permanently banned?">
    Not necessarily, but recovery isn't instant or guaranteed. Stop the risky sending, reduce volume, warm up, message only consented contacts, and contact support.
  </Accordion>

  <Accordion title="How do I avoid getting my line restricted?">
    Send personalized, event-triggered messages to consented contacts within your per-line limits, warm up new lines, and never blast identical messages to a big cold list.
  </Accordion>

  <Accordion title="Will Tuco warn me before a line gets banned?">
    Tuco's spam monitor flags rising failure/risk rates and health checks detect degraded lines, so you get early signals — but you're responsible for the sending behavior that drives the risk.
  </Accordion>
</AccordionGroup>

<Card title="Bulk iMessage — safely" icon="layer-group" href="/guides/send-bulk-imessage">
  Why iMessage should be triggered, not blasted — and how to reach a list without getting flagged.
</Card>