Top
Best
New

Posted by garygao 4 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!

29 points | 114 commentspage 2
dubcanada 3 hours ago|
How is this any different then

https://blooio.com/ https://www.sendblue.com/ https://www.lindy.ai/ etc?

I will say I am the exact opposite of your market, I want absolutely nothing like this. In fact I'd prefer iMessage to allow ZERO programmatic interfacing.

garygao 3 hours ago|
While Blooio and Sendblue are more focused on B2C agents and sales, we're more focused on 2-way conversational business use cases such as customer service that require scale and stability.
dave_xt 3 hours ago||
Lol not true. Blooio also starts at $39 for shared and $98 for dedicated. Source: I'm the co-founder of blooio. https://blooio.com/
garygao 2 hours ago||
The $98 dedicated line is inbound only. A lot of our application comes in the form of warm, consented outbound.
dave_xt 2 hours ago||
We have that too for $195/line for 6+ lines. We also have a full API you can find it here :) https://docs.blooio.com

RCS fallbacks, Emoji reactions, typing indicators, even changing chat background

liamcardenas 2 hours ago||
do you support iMessage app payloads?
dave_xt 2 hours ago||
Depends on the app payload. Reach out to our team and we will work w/ you! enterprise@blooio.com
dgellow 2 hours ago||
> the blue bubble interface, typing indicators, and reactions made agentic conversations feel more human than ones on SMS/RCS

Would you mind detailing your reasoning why agents should feel humans, when they very obviously aren’t? Why should we want AI to impersonate humans?

Yannaner 2 hours ago|
we don't think AI should by any means to pretend to be human, and we are not trying to hide that an agent is involved.

What we mean is that conversation should feel natural and low-friction for the person receiving it. These interactions: blue bubble interface, typing indicators, and reactions will make it less like an automated SMS message and more like a normal messaging flow.

We are trying to make agentic communication clear, useful, and native to channels people already use!

trollbridge 1 hour ago|||
How is blue more human than green?
antiframe 1 hour ago||
For me personally, if I saw an Agent sending me iMessages I would feel it's for the sole reason of deception. Every other company uses SMS and they feels right to me.
xena 3 hours ago||
What is your plan to prevent spam from bad actors?

How do you ban bad actors so they can't spam again?

Does a user have to initiate contact in order to have messages sent to them?

garygao 3 hours ago|
1. Since we're not fully self-serve right now, we can choose to only partner with businesses with use cases that are opt-in and non-spam. 2. If we find that one of our customers is using this for spam, we'll reach out to them asap and determine next steps 3. Not necessarily. We support both inbound (user texts the phone line first) and opt-in outbound (we text the user first) use cases
xena 24 minutes ago|||
How do I as an iOS user permanently opt-out of your services before I get spammed to death with them?
dgellow 2 hours ago|||
And what would be the next steps? Would you block them from using your services, even if they are paying customers? Do you have agreements in place with your users to cover those situations? Is there a way for end users to report to you what they see as spam or unsolicited content? How do you monitor customers activity to determine if they are bad actors?

You should have answers for those points if you want to build trust with end users

garygao 2 hours ago||
For prospective customers, we would most likely try to work with them to brainstorm use cases that are consent-based and non-spam. For current customers, if we do see that they're using our services for spam, we'll reach out to them asap.

Also, while we can't see the exact messages that our customers are sending due to encryption on our servers, we do know when a phone line is close to being banned from our health checks. When that happens, we'll reach out to our customers asap and learn more about what is going on.

tequila_shot 4 hours ago||
This is a very simple integration and the fallback is also pretty straightforward to implement technically. What’s the differentiator? Why would companies use your product?
garygao 3 hours ago|
I'd say mainly scale and stability. While people can definitely do this on their own through Bluebubbles or custom Applescript, stability is difficult to maintain, especially at scale. For most businesses, iMessage is not the core product they want to think about and maintain. They just want a reliable API and support/team to talk to so that they can reliably integrate it as a part of their existing business structure.
zerozerotwo 2 hours ago||
how is it possible to build this whole thing and not know there is a very rich first party api that does the same thing and more in iMessage https://www.apple.com/ios/business-chat/
garygao 2 hours ago|
iMessage for business has a very long and restrictive registration process, gray bubbles instead of blue bubbles, and is inbound only. We're democratizing iMessage for businesses that have good intentions on helping their customers more but can't afford to go through the long approval process.
zerozerotwo 1 hour ago||
Right gray bubbles and validated businesses for commercial and blue for people. Apple business chat is not inbound only. 100% of your features including the ability to redirect voice calls to iMessage are already offered by Apple via an api and its integrated into every major crm
littke 3 hours ago||
As much as I want to applaud your progress here, as a user I want transactional stuff to stay in my email inbox. My iMessage is already starting to become overwhelming from spam and apps — I want fewer messages not more.
garygao 3 hours ago|
Yeah I agree. Our goal behind this is not to clutter up people's iMessage inbox with more transactional messages. It's to replace the SMS/RCS conversations that people are already having with customer service and scheduling agents with something more conversational and human.
PantaloonFlames 3 hours ago|||
Why is iMessage "more conversational" than RCS? and "more human"??

I don't get the distinction you're making. I'm not an expert in mobile messaging so maybe I am missing something obvious.

And what about WhatsApp?

garygao 2 hours ago||
iMessage is more conversational because it's what most people are used to using and seeing. People generally associate green bubble messages with spam/transactional messaging and blue bubble with trust. Additionally, iMessage also has additional features such as typing indicators and reactions (likes and loves) that makes the interface feel more conversational. WhatsApp could also be very conversational, but most people in the US use iMessage.
kreitje 2 hours ago||
Reading your responses it seems like your angle is to fake looking like a human by using the blue bubble. Are you worried your users will ruin the trust of the blue bubble thus killing your product with your product?
frumplestlatz 3 hours ago|||
My existence couldn’t possibly be any more digital, and I can’t remember a single time I’ve had a SMS/RCS conversation with customer service or a scheduling agent. I don’t want to have one either. My message inbox is already full enough.

My iMessages are for conversations with people that I actually want to talk to. The notifications are high priority because it’s with people that I want to talk to.

I can’t imagine my annoyance if I were to receive an iMessage notification while I’m expecting an important message, only to find that it’s more spam.

My email inbox is already a wasteland because of this. The absolute last thing I need or want is for the same thing to happen to iMessage.

garygao 3 hours ago||
That's why we're making sure that all of the use cases are non-spam and also of high importance to the user. As we've seen through our customers, an after-hour customer support agent for their apartment, as an example, could be a contact of high importance for the user and definitely not spam in their iMessage
the_arun 2 hours ago||
Assuming we have more customers using WhatsApp over iMessage, How did you decide to use iMessage over WhatsApp messaging?
Yannaner 2 hours ago|
we started with iMessage because it is still the most dominant, trusted channel in the US.
MuffinFlavored 1 hour 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 1 hour ago|
They are a photon + linq wrapper. Very surprised YC backed this actually
frumplestlatz 3 hours ago||
> iMessage is intended for communicating with family and friends, and is not for conducting commercial activities or disseminating unwanted messages. iMessage misuse may result in service limitations.

https://www.apple.com/legal/privacy/data/en/messages/

Seems pretty damn clear.

garygao 3 hours ago|
We are not "disseminating unwanted messages". A lot of what we're doing (e.g. customer support or missed call text back) would be things that users would already be doing conversationally over iMessage.
icedchai 2 hours ago|||
You can't guarantee one of your customers isn't going to do that dissemination though, right? No spammer is going to sign up saying "I'm a spammer that just got banned from <other service>! Can you guys help?"
nvme0n1p1 2 hours ago||||
Are you "conducting commercial activities"?
antiframe 1 hour ago||
Getting a spam message about an abandoned shopping cart item is clearly "commercial activities" to me.
qwertyuiop_ 1 hour ago|
Why shouldn't Apple shut this down to prevent spam in order to defend the Apple customer experience.
garygao 1 hour 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 1 hour 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 56 minutes ago|||
> real user pain point

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

More comments...