Chert

What is Chert?

Chert is an infrastructure product for sending and receiving messages over Apple’s iMessage protocol through a single API. It is designed for product and GTM teams that want to run conversations on iMessage while still handling delivery state, webhooks, attachments, and fallback behavior in a programmatic way.

The platform positions iMessage as a channel for outbound and inbound workflows such as booking meetings, support conversations, onboarding, and conversational AI. The source describes blue-bubble messaging, verified senders, live delivery telemetry, and SMS/RCS fallback when the recipient is not on iMessage.

Key Features

• Single API surface for iMessage workflows: Chert exposes one API for outbound and inbound messaging so teams can build iMessage-based experiences without managing each message flow separately.
• Real iMessage threads: Messages flow over Apple’s iMessage protocol, with blue-bubble threads and support for read receipts and tapbacks where available.
• SMS/RCS fallback: If a recipient is off-platform, Chert can reroute to SMS and surface that channel change in the API.
• Attachments and rich thread content: The product supports sending photos, PDFs, and links directly in the conversation thread.
• Live delivery telemetry: The platform shows delivery state and message-level status so teams can track whether a message was delivered or queued as fallback.
• Webhooks and CRM sync: Chert provides REST API and webhooks for inbound and outbound events, with native sync for common events such as lead creation, meeting booking, and opt-out receipt.

How to Use Chert

Teams typically start by scheduling a kickoff and deciding which workflow they want to move onto iMessage. From there, they connect Chert to their product or internal tools through the API and webhooks, then route outbound messages and inbound replies through the same thread.

In practice, a team might use it to send a welcome message after signup, respond to a support request, or book a meeting from an outbound outreach sequence. The platform also surfaces whether a message landed in iMessage or fell back to SMS, which helps teams handle follow-up logic and reporting.

Use Cases

• Lifecycle onboarding: Send a welcome message or short product tour right after a new user signs up, using iMessage as the initial contact channel.
• Customer support: Handle customer questions in a thread instead of routing people to a ticket portal, which keeps the conversation in the messaging app they already use.
• Conversational AI agents: Build B2C agents that can answer questions, reschedule appointments, or continue a short back-and-forth conversation in a more natural thread.
• Cold outbound sales: Reach prospects with iMessage-based outbound messages to request a reply or book a meeting, with fallback handling for recipients who are not on iMessage.
• Internal workflow routing: Pass message events into tools such as CRM systems, sales tools, voice agents, or internal data stores so teams can trigger follow-up actions from the conversation.

FAQ

Is Chert sending real iMessage messages? Yes. The source says outbound and inbound messages flow over Apple’s iMessage protocol, and SMS is used only as a fallback when the recipient is not on iMessage.

How is Chert different from SMS infrastructure? It is built around iMessage threads rather than carrier-mediated A2P SMS. The source highlights blue-bubble messaging, read receipts, and tapbacks as part of the iMessage experience.

Can Chert connect to existing systems? Yes. The source says Chert exposes a REST API and webhooks for inbound and outbound events and offers native sync for some common events.

What kinds of workflows is it meant for? The page emphasizes GTM and product workflows such as onboarding, support, outbound meeting booking, and conversational AI.

Alternatives

• SMS infrastructure platforms: Traditional SMS tools are built for carrier-delivered text messaging and typically use A2P SMS flows rather than iMessage threads.
• General messaging API providers: Broader messaging APIs may cover multiple channels, but they are usually centered on SMS or omnichannel messaging rather than a dedicated iMessage workflow.
• In-app chat or support widgets: These keep conversations inside a product or website instead of using a user’s phone inbox.
• Email outreach tools: Email is often used for outbound and lifecycle messaging, but it is a different channel with different response behavior and conversation structure.