Pinned Tweet
WhatsApp for developers.
kapso.com/
Kapso retweeted
Verify businesses for WhatsApp directly from Kapso.
Web, API, MCP. You choose.
This is huge for SaaS and agencies building WhatsApp agents for their customers.
No need to send them to Meta Business Manager anymore.
Kapso retweeted
We made it really easy to connect voice agents to WhatsApp on Kapso.
1️⃣ Connect a WhatsApp number
2️⃣ One-click deploy our open-source repo to Railway
3️⃣ Enable WhatsApp calls
Done, your agent can now take and make calls.
Kapso retweeted
@kapso_com son de lo mejor de lo mejor, este finde me solucionaron la vida y terminé un proyecto en 1 gracias a la solución que tienen 👏🏻 todo me funcionó perfectamente y no tuve inconvenientes alguno
Kapso retweeted
Kapso for Tech Providers is live.
Your customers shouldn't need a credit card in Meta to use WhatsApp in your product.
1️⃣ Your customer connects their WhatsApp
2️⃣ Kapso funds their usage
3️⃣ You set the price and bill them
4️⃣ Kapso pays Meta
Kapso retweeted
You can build some really cool stuff with WhatsApp Flows
1️⃣ Flowso: build and test WhatsApp flows locally
WhatsApp Flows are interactive forms inside WhatsApp.
They're one of the best ways to reduce the number of WhatsApp messages you send.
You send just one message and can collect tons of information.
But until now, building and testing Flows has been hard.
Today we're launching Flowso: an open-source library that lets your coding agents build and test WhatsApp Flows locally.
Just install it and ask your coding agent to build one.
Kapso retweeted
This is huge for WhatsApp Tech Providers!
Keep your direct Meta integration.
And Kapso handles billing for your customers' WhatsApp usage.
Today we're launching Kapso for Tech Providers.
If you're a Tech Provider, Meta bills your customers directly for their WhatsApp messages.
That means your customers have to add a credit card on Meta on top of paying you.
It adds friction and confusion, and it makes for a worse experience.
And you have no control over how much or how your customers get charged.
Today we're launching Kapso for Tech Providers, built on Meta's Multi-Partner Solutions.
You keep your direct Meta integration, and Kapso provides the credit line to fund your customers' WhatsApp usage.
You manage billing for all your customers in one place, and your customers only deal with you.
Today we're launching Kapso for Tech Providers.
If you're a Tech Provider, Meta bills your customers directly for their WhatsApp messages.
That means your customers have to add a credit card on Meta on top of paying you.
It adds friction and confusion, and it makes for a worse experience.
And you have no control over how much or how your customers get charged.
Today we're launching Kapso for Tech Providers, built on Meta's Multi-Partner Solutions.
You keep your direct Meta integration, and Kapso provides the credit line to fund your customers' WhatsApp usage.
You manage billing for all your customers in one place, and your customers only deal with you.
Kapso retweeted
WhatsApp prices are changing in 8 days.
To help everyone prepare, we're launching two new tools:
1️⃣ Flowso: an open-source library to build and test WhatsApp flows locally
2️⃣ Kapso for Tech Providers: fund your customers' WhatsApp usage while keeping your direct Meta integration
Kapso retweeted
Introducing kapso-emulator
The first local emulator for Kapso. Run your whole WhatsApp integration on localhost, including signed webhooks, with zero real messages. We've been heavy users of @kapso_com for a while, but we never had a good way to test the whole product end to end until we built this for ourselves.
Kapso retweeted
The Kapso Agent has “modes"
Modes are like big agent skills + tools.
(borrowed the idea from the PostHog Agent)
The agent can decide when to switch to a specific mode based on the task.
It works really well!
And now you can create your own Kapso Agent modes.
Example:
If you want to create a “Support Assistant,” you can add:
- Add a custom prompt
- Connect an MCP server to provide tools
- And even connect GitHub repos containing relevant knowledge or code.
Then, in the Inbox, you can ask the Kapso Agent for help with any support task, and it will automatically switch to your Support Assistant mode.
Kapso retweeted
You can now add the Kapso Agent to your Slack workspace.
It can search your logs, monitor your Inbox, and help you tune your AI agents.
And you can call it via API too 👀
Kapso retweeted
Estamos explorando algo muy interesante en @lapyme_ar, inspirado en el artículo de ai-sdk-factory
Nuestro soporte funciona por WhatsApp con @kapso_com. Armamos un agente con @eve que lee cada conversación y la clasifica en consulta general, feature request o posible bug.
Cuando detecta un posible bug, delega el caso a un subagent "Analyst".
Este agente analiza el mensaje (incluso con videos, imágenes o transcripciones de audios), busca evidencia del error en la base de datos y en el repo que está en producción. Todo read-only y datos personales "redacted".
Si encuentra evidencia suficiente, crea una issue con toda la info. De ahí lo agarramos con Codex y abrimos la PR que lo arregla.
A medida que los issues generados, vamos a sumar otro subagent tipo "Implementador" para que directamente arme el PR que arregla el problema, iterando sobre las reviews automáticas y humanas. Siempre pasando por una verificación humana antes de mergear.
Kapso retweeted
One of the things we were focused on when building Findings was making it extendable.
Would you like to have other signals? Findings tracks your custom events as well
Want to tailor the default events? Feel free to edit the workflow that categorizes conversations directly
