iMessage infrastructure for reaching people at scale.

Real iMessage. Outbound and inbound flow over Apple’s iMessage protocol with the blue-bubble UX your customers already trust. We fall back to SMS only if a recipient isn’t on iMessage, and we surface that distinction in the API so you always know which channel a message landed on.

Twilio is an A2P SMS pipe: carrier-filtered, 10DLC-registered, and visibly automated. Chert delivers a peer-to-peer iMessage thread that opens with the blue bubble, supports read receipts and tapbacks, and lives in the same inbox as a recipient’s family and friends. Open and reply rates are categorically different because the channel is.

Because iMessage is end-to-end and tied to Apple ID, it doesn’t inherit the carrier-side filtering that hammers A2P SMS. We rotate sending identities, warm them gradually, and cap volume per identity per day to stay well below the heuristics Apple uses to throttle abusive senders. Anyone promising "unlimited blast" volume is one ban away from disappearing.

We expose a REST API and webhooks for every inbound and outbound event, so you can wire conversations into Salesforce, HubSpot, or an internal data store with a few hours of work. We also ship native sync for the common cases (lead created, meeting booked, opt-out received). If you’d rather not build, we’ll handle the integration during onboarding.