HN Explorer

Ask HN: Why is WhatsApp API so bad?

3 points by BraverHeart ↗ HN
- Limited APIs (You can't read previous messages, you have to rely on the Webhook and pray you don't miss anything, you can't even use the same number on a smartphone as a backup or fallback)

- Limited flexibility

- Painful on-boarding experience

- Painful to use for pro-active Customer Support (Users have to initiate messages, you can't get back to them after 24 hours without using an automated template message)

It feels like they are actively sabotaging the potential of this service.

What am I missing? would love to hear from someone at Facebook.

4 comments

[ 3.4 ms ] story [ 22.3 ms ] thread
s1k3s
> - Painful to use for pro-active Customer Support (Users have to initiate messages, you can't get back to them after 24 hours without using an automated template message)

Anything other than this would effectively turn it into a spam machine.

BraverHeart
They could easily implement a reputation system, with checks and balances, and a strict approval process.

Or implement a progressive system that allows you more freedoms as you build a good reputation (Being an honest business, not having spam intentions)

The painful part of on-boarding for me was technical (Setting up API keys, doing initial configuration, etc., the UX is bad), not administrative.

These are just ideas I thought of on the spot, I'm sure they can come up with a better workflow if they needed.

BraverHeart
Also the current limitations don't solve spam, I get spammed on WhatsApp often, it just limits it on the expense of non-offending businesses that want to offer quality service to their customers.
BraverHeart
Their message template feature also has multiple limitations, for instance you aren't allowed to put variables in the footer section, but you are allowed to do so in the header section, which is strange.