Founder of Robotipy. Building Melonhelp, a help desk for WhatsApp, Slack and email with unlimited agents.
Thanks Shishir! That’s the idea: adding someone in peak season shouldn’t change the bill. Same reasoning for MIA, a fixed price is easier to plan than paying per resolution.
@avdeev Yes, WABA on Meta’s Cloud API. The customer connects through Meta’s signup flow inside Melonhelp, and the WABA gets created during that flow, so nobody has to set it up by hand.
It also supports coexistence: you keep the same number in the WhatsApp Business app on your phone, and Melonhelp receives and replies through the API at the same time. Or you can go dedicated if you run everything from Melonhelp.
Are you working with WhatsApp too?
@neotecsoft Thanks Luciano! 🙌 Exactly, in LATAM WhatsApp is the main channel, so it had to be first-class.
On MIA: by default it’s confidence-based. Every answer has to be grounded in your knowledge, and if confidence is low or the request is outside the agent’s instructions, it hands the ticket to a person instead of guessing. On top of that, each team sets its own rules with instructions, skills, flows and tools, since MIA runs on Melonhelp Agents.
On automations: Tickets already has signed webhooks (ticket created, assigned, closed, reopened and inactive), so an RPA flow can pick up a ticket the moment it’s created. The REST API to create and update tickets is in private beta, and the Answer API returns a needs_human flag your flow can use to decide when a bot can finish the job. If you want to try the beta with an RPA flow, write me and I’ll add you.
¡Abrazo desde Chile!
@royalseo700 Thanks! Glad the free plan makes it easy to try. Appreciate the support today 🙌
@jmsiro Thanksl! 🙌 Really glad it helped your CS team keep requests organized. Thanks for taking the time to share it here.
@mariela Thanks! 🙌 Glad email and Slack are working well for your team. Any feedback on what we should improve next is always welcome.
@ayushdhanani369 Thanks! Both. By default it’s confidence-based: every answer has to be grounded in your knowledge, and if confidence is low or the question is outside the agent’s instructions, MIA hands the ticket to a person instead of guessing. Tickets turns the AI off for that ticket and notifies your team, with the full conversation.
On top of that, MIA is built on our Agents platform, so you set your own rules with instructions, skills, flows and tools (for example, “always hand off refunds” or “escalate if the customer asks for a manager”). It also stops replying as soon as someone on your team answers, and you can turn it off per ticket.
Small support teams break in the same place every time: a WhatsApp on someone's phone, a Slack thread that sank, an email two people assumed the other had answered. And the tools that fix it charge per agent, and now per AI resolution too.
MelonHelp puts WhatsApp, Slack and email into one ticket inbox. Flat price by volume, unlimited agents. The AI agent (MIA) answers the repetitive stuff and hands off to a person when it does not know, at a fixed price.
I am building it in public from Chile. Happy to answer anything about pricing, the WhatsApp API or how the AI handoff works.
This is the first time I’ve seen a tool with ‘workflows’ for PDFs, and I had no idea I needed that feature. I was looking for an app to sign PDF and would be a good option "mark" the pdf with some certificate
@alignbase Not yet. Today it works as draft and publish: edits stay in draft until someone publishes, so the live instructions only change on an explicit publish. Version history with rollback is on the roadmap, and tying each ticket to the version that answered it is a good point, I’m noting it for that work.
Is this more for compliance or for debugging answers?