Last time I wrote about Javara, a dual WhatsApp setup was still on the next list: Meta Cloud API alongside the current provider. That item can come off.

Yesterday I got the Meta Cloud API ecosystem connected — WhatsApp and Instagram. The agent can now reply to chats, reply to comments, and post.

Why this one mattered

Javara already had a WhatsApp and Instagram DM concierge. It worked. It just did not sit on Meta's official path. Fine while we were proving the idea. Not the version I wanted merchants to depend on.

Meta Cloud API is the official door. WhatsApp Business messaging, Instagram DMs, comments, and publishing live in the same Graph API family. One app, one review process, one webhook. That is the boring reason.

The product reason is simpler. Indonesian F&B customers do not open a dashboard to talk. They WhatsApp. They comment on a post. If the agent cannot live there, it is not a concierge.

What the agent can do now

• Chat. Incoming WhatsApp and Instagram DMs go through the same agent loop. The model sees the thread and the merchant context it is allowed to see — menu, hours, loyalty, the rest — then drafts a reply.
• Comments. Instagram comments are the public version of the same job. "Masih buka?" "Ada yang vegan?" "Promo apa hari ini?" The agent can answer without the owner living in the notifications tab.
• Posts. The content studio already generated marketing from real sales data. Now it can publish, instead of stopping at a draft.

The principle has not changed: owner approves, Javara does the work. The agent writes. For anything that represents the brand in public, a human still gets the last look.

What this unlocks

A customer can ask about today's promo on Instagram, get a reply that knows the actual menu, and continue on WhatsApp if the conversation moves there. The owner sees the thread. The agent does the typing.

That is closer to the product I meant when I wrote owner approves, Javara does the work. For an F&B owner, a lot of the work is answering people.

What's next

The Meta path still needs to sit alongside the current WhatsApp provider for a while — dual setup, as planned. Merchants should not feel a cutover. After that, make the agent boringly reliable on the boring questions, and keep a human in the loop for everything else.

A connected API does not acquire customers. Distribution is still the bottleneck. But at least the product can now talk where the customers already are.