Top
Best
New

Posted by garygao 5 hours ago

Launch HN: Chert (YC P26) – Twilio for iMessage(www.trychert.com)
Hey HN! We’re Gary and Ian, and we’re building Chert (https://www.trychert.com/), an API for businesses to send, receive, and automate iMessage conversations at scale. Check out our demo: https://www.youtube.com/watch?v=SRdwvVxMMoI.

We originally started by building products on top of iMessage because the blue bubble interface, typing indicators, and reactions made agentic conversations feel more human than ones on SMS/RCS. These included a one-shot iMessage agent builder that reached 2,000 users in one week and an automated iMessage outbound sequencer that sent thousands of outbound messages per day.

The hard part is that iMessage does not have a native API like SMS/RCS. Sending and receiving iMessages requires a separate infrastructure that is difficult to set up and maintain, especially at scale.

As we talked to more companies, we realized that the highest-volume use cases for iMessage were not B2C agents or even sales. They were things like customer service, missed-call text-back, cart abandonment, and inbound lead capture in verticals like home services, DTC brands, and property management that drive the highest volume.

Furthermore, these companies often need additional support, such as custom infrastructure setup (e.g. contact card, area code, or local worker sessions), integration support with their existing SMS/RCS or voice agent systems, and a reliable way to scale their volume over time.

We built Chert to be an infrastructure layer for businesses to handle iMessage conversations at scale. Businesses can use our API to send and receive iMessages programmatically, route replies to humans or agents, and integrate conversations into the systems they already use.

To maintain stability across both outbound and inbound use cases, we built phone line health checks and SMS/RCS fallback systems. We also integrate with existing SMS/RCS systems, voice agents, CRMs such as Salesforce, HubSpot, and Attio, and tools like Slack. Finally, we let businesses reliably scale from a few test lines to hundreds of lines with automated line provisioning and a usage-based pricing structure.

We’re working with companies doing conversational messaging in DTC, sports programs, property management, and home services at the scale of hundreds of lines.

We’d love to hear your thoughts on this and other similar verticals where iMessage could be useful. All comments welcome!

36 points | 127 commentspage 3
the_arun 3 hours ago|
Assuming we have more customers using WhatsApp over iMessage, How did you decide to use iMessage over WhatsApp messaging?
Yannaner 3 hours ago|
we started with iMessage because it is still the most dominant, trusted channel in the US.
moralestapia 1 hour ago||
Pricing anywhere?
qwertyuiop_ 2 hours ago||
Why shouldn't Apple shut this down to prevent spam in order to defend the Apple customer experience.
garygao 2 hours ago|
We are solving a real user pain point and not promoting spam. Users want a more conversational interface when they're reaching out for customer support during off hours and businesses want a better medium to talk to their customers. There is value created on both sides. There is no reason for Apple to ban us.
redwinbee 2 hours ago|||
I believe enough people have made it clear in this thread that Apple does already have reason to ban you. Whether or not you promote spam is not the issue, the issue is that Apple already has a feature built for this exact purpose; you can disagree with their approach—and maybe you’re right, I don’t know. But the idea that you won’t blocked by Apple for this is naïve.
smikhanov 1 hour ago|||
> real user pain point

That is obvious from all the upvotes your comments get on here.

MuffinFlavored 2 hours ago||
This is a foothold business living entirely at Apple's discretion.

edit: more research

> Chert is in the Sendblue/Blooio lineage, which runs genuine Apple software on real Macs logged into real Apple IDs. They're almost certainly not doing "Beeper Plus again."

dave_xt 2 hours ago|
They are a photon + linq wrapper. Very surprised YC backed this actually
huhrymuhry20000 4 hours ago||
I like the idea of explaining things like "<brand name> for <brand name>"
garygao 4 hours ago|
Thanks, it felt like the clearest way to describe it haha
smashah 4 hours ago||
It's good YC is funding you because it acts as a later of protection from legal threats by apple. Hopefully if/when Apple litigate this I hope you will fight and set precedent for commercialisation of adversarial interoperability (A digital human right).

I suggest you implement Baileys also to your service so it can also be done with WhatsApp so we can accelerate the inevitable litigation.

Yannaner 3 hours ago|
We are def thinking a lot about interoperability and what it should look like in practice... >:)
plombe 2 hours ago||
AI slop
kakuremi 3 hours ago||
[dead]
npilk 4 hours ago|
Love chatting with an agent via iMessage for the right use case - it feels very natural and human. I hacked my own together with an old laptop and BlueBubbles.

How would you compare your offering with Spectrum (https://photon.codes/)?