> ## Documentation Index
> Fetch the complete documentation index at: https://docs.contiguity.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Outbound-first
> When you have to message someone first, and how to do it safely.
You message someone before they've texted you. Appointment reminders, shipping updates, and marketing all start this way.
* It's the only option for proactive, time-sensitive messages like appointment reminders, order updates, and alerts.
* You control the timing
* It looks like spam to Apple's detection systems, regardless of whether you have consent on file
* It needs gradual ramp-up on new numbers, careful pacing, and carries a higher risk of getting flagged, especially at volume or to brand-new contacts
Opt-in status is a legal and compliance concern, not a signal Apple's automated systems can see. A cold send to an opted-in list behaves identically to a cold send to a purchased or scraped one, from Apple's side. Minimize outbound-first sends where you can, even to consenting users.
## Use outbound-first selectively
Most products use a hybrid approach. Reserve outbound-first for messages the customer already expects, such as a reminder for an appointment they booked or a shipping update for an order they placed. Use [inbound-first](/kb/compliance/imessage/strategies/inbound-first) for everything else, especially first contact.
Once a customer replies, later messages in that thread are no longer cold outbound. A shipping update sent to someone who texted you last week about their order is part of an ongoing conversation, not a blast to a stranger.
If the recipient would be surprised to hear from you, treat the message as outbound-first and follow the guidance below. If they're expecting it or have talked to you recently, it's safe to treat it as a reply.
If you need to send outbound-first, follow the personalization, pacing, and ramp-up guidance in [Best Practices](/kb/compliance/imessage/best-practices).
## Scaling with number pooling
Each leased number is capped at 1 message per second sustained, with short bursts allowed up to 5 messages per second. See [Caveats & Limits](/kb/compliance/imessage/caveats-limits#rate-limits) for the full details. To send faster than that, pool multiple leased numbers together to reach the throughput you need. If you need to sustain 10 messages per second, you'll need 10 numbers to do it. Pooling doesn't make any individual number faster, it just gives your business more numbers to send from at once.
It's entirely your decision on how many numbers to pool together, which numbers to use, and how to distribute them. Contiguity enforces hard limits, but ultimately leaves everything else up to you.
When picking a number for a fresh, never-before-contacted recipient, distribute the choice across your pool (round-robin or random) so no single line gets all the new-contact volume. Once that recipient has been assigned a number, keep using the same one for every message you send them.
## Filter number lists beforehand
Before messaging customers, use the Contiguity iMessage Availability Lookup API to check if their phone number supports iMessage. This helps you avoid handling SMS fallback and ensures that, if needed, you only send to recipients using Apple devices.
***
Let the customer message you first, then reply freely.
Still have questions? Join our [Discord community](https://discord.gg/Z9K5XAsS7H) or email us at [help@contiguity.support](mailto:help@contiguity.support).
{
const script = document.createElement('script');
script.textContent = `
document.querySelectorAll('a[href*="mintlify.com"][href*="poweredBy"]').forEach(link => {
link.remove();
});
`
document.head.appendChild(script);
}}
/>