Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
garygao
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Show HN: Put an AI agent on a FaceTime audio/video call (open source, WebRTC)
(github.com)
1 points
by
garygao
3h ago
|
0 comments
2.
▲
by
garygao
4mo ago
We're not trying to be deceptive. In fact, whenever we deploy agents over iMessage, we make it very clear that they're speaking with an AI agent and that they can request human handoff if they want. The goal is to make conversatio
3.
▲
by
garygao
4mo ago
Apple is not necessarily against programmatic messaging. In fact, they actually developed Applescript for people to do so. Beeper was using it to replace the iMessage interface when it already exists, which is why I think Apple was against
4.
▲
by
garygao
4mo ago
I think what we're doing is fundamentally different from Beeper in terms of positioning. Beeper is trying to offer an additional interface to iMessage when it already exists for humans. What we're doing is giving agents the abilit
5.
▲
by
garygao
4mo ago
yes, what I originally meant was that Apple iMessage for Business has gray bubbles for the messages that you're sending (or the ones that would normally be blue)
6.
▲
by
garygao
4mo ago
It's not the "wrong" way, it's just different. iMessage works well for businesses that want to create a conversational experience in their customer service that conveys care and attention
7.
▲
by
garygao
4mo ago
iMessage for Business is very restrictive and has a really long approval process. On top of this, it also sends gray bubbles and doesn't allow any outbound, which prevents consented outbound use cases such as form fill text back.
8.
▲
by
garygao
4mo ago
Yes, this is what we believe! We just want to make existing conversations over SMS/RCS feel more natural and conversational!
9.
▲
by
garygao
4mo ago
Our goal behind this is to make it easier for people to conversationally interact with agents when they want to. Use cases like customer service or form-fill text backs would fit this. People are already getting SMS/RCS conversations i
10.
▲
by
garygao
4mo ago
We're clear on what we want to do and the future we are building towards, which is an agentic future where agents can better assist and interact with humans on a more emotional and personal level.
11.
▲
by
garygao
4mo ago
SMS/RCS is better for some use cases (e.g. transactional messaging, promotions, or order updates) while iMessage is better for others (e.g. customer service). iMessage is better for these use cases because it feels more natural to the
12.
▲
by
garygao
4mo ago
Yes, I agree, which is why we try to make the opt-in clear. Use cases like form-fill text back or cart abandonment after the user has opted in and noted down their number are what we primarily focus on
13.
▲
by
garygao
4mo 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. Th
14.
▲
by
garygao
4mo ago
We do run checkups and keep very closely in touch with our customers. We don't plan to go self serve in the near future and will most likely still have a very personalized onboarding process.
15.
▲
by
garygao
4mo 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 mor
16.
▲
by
garygao
4mo 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
17.
▲
by
garygao
4mo 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 th
18.
▲
by
garygao
4mo ago
We're working to bridge the interaction between humans and bots so that automated conversations feel more natural and comfortable for the end user. In circumstances where the user can't reach an actual human (e.g. off hours suppor
19.
▲
by
garygao
4mo ago
We're helping to support conversational customer support agents that can help users better during off-hours and scheduling assistants that can interact with and understand user requests better than current models over SMS/RCS. Thi
20.
▲
by
garygao
4mo ago
I agree. We're not completely self-serve right now, so we get to talk with each potential customer and learn about their use case before onboarding them onto the platform. This way, we can prevent use cases that involve spam or abuse.
21.
▲
by
garygao
4mo ago
Thanks for the suggestion! Yes, the setup process is extremely long and requires a lot of documents from the side of the business haha. It's definitely one of our goals to create the Vercel for iMessage for Business. Also, for the iMes
22.
▲
by
garygao
4mo ago
The $98 dedicated line is inbound only. A lot of our application comes in the form of warm, consented outbound.
23.
▲
by
garygao
4mo 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.
24.
▲
by
garygao
4mo ago
We have SMS/RCS fallback for non-iMessage devices. Also, in the verticals that we're targeting, the iMessage usage rate is a lot higher than 50%
25.
▲
by
garygao
4mo 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
26.
▲
by
garygao
4mo ago
We work with our customers to make those messages consent-based and feel non-spam.
27.
▲
by
garygao
4mo ago
People don't report our phone lines to be spam because the use cases that we focus on are either mostly inbound (e.g. customer service, the user is the one who texts first) or warm opt-in outbound (e.g. form-fill text back or follow up
28.
▲
by
garygao
4mo 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.
29.
▲
by
garygao
4mo ago
Apple wouldn't ban us since we're not doing anything that would qualify as spam or abuse. Even if that hypothetical event does happen, we have SMS/RCS fallback systems in place so no conversations get stopped or lost
30.
▲
by
garygao
4mo ago
We're not encouraging spam with this. We're mainly focused on existing conversational use cases that's currently done over SMS/RCS. They can be more human and expressive when done over iMessage.
More ›