Hi HN, I'm Rolands - cofounder of Balsio (previously BirdyChat).
Some of you may remember us from January, when BirdyChat became the first app to go live with WhatsApp interoperability under the EU Digital Markets Act: https://news.ycombinator.com/item?id=46746476.
Since then we renamed to Balsio, added workspaces for teams and made the app more agent-friendly.
/ The problem we're solving:
Many small teams in Europe run their work on personal chat apps. They're OK for critical communication, but they are not built for work - personal and work chats get mixed, other people see your personal phone number, group chats have no threads and they get noisy quickly, no schedule send, limited possibilities to integrate your tools, etc. We don't think that personal chat apps will get any better for doing work in the future and so we decided to build Balsio.
/ What we do:
Balsio is a free work chat built and hosted in the EU. You sign in with your work email and that becomes your username. You can message your team and people at other companies using their email addres. You can also message WhatsApp contacts directly from Balsio.
You can add agents to chats through our API. Separately, you can connect your own AI (Claude, ChatGPT or anything that supports MCP) to your account so it can read and write on your behalf.
/ Tech details:
- Backend is Elixir
- Clients: SwiftUI for iOS and Mac, Jetpack Compose for Android, React for Web and Windows app
- Service hosted in Europe
- Interoperable with WhatsApp
/ Current limitations:
- WhatsApp chats only work in the European Economic Area, only for one-to-one chats, and only on iPhone, iPad and Android. Group chats are on our roadmap
- The WhatsApp contact has to turn on "Third-party chats" in their WhatsApp settings before you can message them
- You can't create agents inside the app yet, our users need to bring their own agents to the app through the API
/ Business model:
The product is free. We plan to charge larger companies for additional features like single sign-on, more data storage and advanced user management.
/ Feedback I'm looking for:
1. If you have built agents that work in chat, is there anything you're missing in other communication apps that you'd like to see to improve your agent experience?
2. If you run a small team or company, what agent use-cases (besides coding and customer support) do you have or have seen?
rmesters•58m ago
Some of you may remember us from January, when BirdyChat became the first app to go live with WhatsApp interoperability under the EU Digital Markets Act: https://news.ycombinator.com/item?id=46746476.
Since then we renamed to Balsio, added workspaces for teams and made the app more agent-friendly.
/ The problem we're solving: Many small teams in Europe run their work on personal chat apps. They're OK for critical communication, but they are not built for work - personal and work chats get mixed, other people see your personal phone number, group chats have no threads and they get noisy quickly, no schedule send, limited possibilities to integrate your tools, etc. We don't think that personal chat apps will get any better for doing work in the future and so we decided to build Balsio.
/ What we do: Balsio is a free work chat built and hosted in the EU. You sign in with your work email and that becomes your username. You can message your team and people at other companies using their email addres. You can also message WhatsApp contacts directly from Balsio.
You can add agents to chats through our API. Separately, you can connect your own AI (Claude, ChatGPT or anything that supports MCP) to your account so it can read and write on your behalf.
/ Tech details: - Backend is Elixir - Clients: SwiftUI for iOS and Mac, Jetpack Compose for Android, React for Web and Windows app - Service hosted in Europe - Interoperable with WhatsApp
/ Current limitations: - WhatsApp chats only work in the European Economic Area, only for one-to-one chats, and only on iPhone, iPad and Android. Group chats are on our roadmap - The WhatsApp contact has to turn on "Third-party chats" in their WhatsApp settings before you can message them - You can't create agents inside the app yet, our users need to bring their own agents to the app through the API
/ Business model: The product is free. We plan to charge larger companies for additional features like single sign-on, more data storage and advanced user management.
/ Feedback I'm looking for: 1. If you have built agents that work in chat, is there anything you're missing in other communication apps that you'd like to see to improve your agent experience? 2. If you run a small team or company, what agent use-cases (besides coding and customer support) do you have or have seen?
Thanks!