It works alongside the X app, not instead of it. You pick the public accounts, we send their new posts to you. Try it at wallawhats.com/signin

The same code verifies where alerts will be delivered, so setup and sign-in happen in one step.

You enter your WhatsApp number or email, get a one-time code within seconds, and type it in. That's it.

We built WallaWhats, which sends alerts from X accounts to WhatsApp, and we chose to skip passwords. Sign-in is a 6-digit code. wallawhats.com

Builders and holders: what security evidence do you look for before trusting a product with your inbox? Details: zellbox.com/blog/zellbox-pas… #CRM

Against Callbell, AgendaPro or Doctolib, we compare on capability, not customer count. We are early-stage, and a certified Google integration is a concrete capability.

BWS ships several products: badges.ninja, wallawhats, xbot.ninja, ipfs.ninja and Zellbox. Zellbox is a CRM with WhatsApp reminders, Google Calendar sync and a shared inbox, built for appointment-driven SMBs.

For the $BWS ecosystem this matters: the audit is run by Google's process, with an outside lab testing the app, not a self-declared badge. It is evidence of engineering discipline in a working product.

A security milestone, not a roadmap slide. Zellbox, one of the BWS solutions, passed an independent Google audit required for apps with Gmail and Calendar access. $BWS 0xaADE1D6701173Bd924c9de2d56a00eF4e3d9de4d

Try it free at badges.ninja. Documentation: badges.ninja/docs/guide/badg… #DigitalCredentials

Issuers get durable, verifiable credentials. Recipients get badges whose images still load years later, on any Open Badge v2.0 verifier.

Edit a badge later and the previous CID stays reachable. Awards already issued keep their original artwork indefinitely.

IPFS is content-addressed: each image gets a CID derived from its content, so the artwork a recipient sees can't be quietly swapped.

Credentials should outlive any single server. badges.ninja pins every badge image to IPFS for permanent, decentralized storage. #OpenBadges $BWS 0xaADE1D6701173Bd924c9de2d56a00eF4e3d9de4d

Caps are configurable per plan, and the free tier is enough to try it. Details in the FAQ: wallawhats.com/docs/faq

The first posts still arrive within seconds when available. Only the overflow is grouped, and everything stays in notification history with delivery status.

We hit this ourselves. Following a busy account during an event meant dozens of pings in an hour, and the signal got lost in the noise.

We just wrote up velocity caps for WallaWhats: when a monitored X account posts in a burst, the overflow is batched into one WhatsApp digest. wallawhats.com

Builders and holders: which security or compliance milestone would you want to see from every BWS solution? Write-up: zellbox.com/blog/zellbox-pas… #CRM

On capability, Zellbox combines WhatsApp reminders, Google Calendar sync, a shared inbox and signed consents, the territory of Callbell, AgendaPro and Doctolib. It's early-stage, and we're not claiming traction numbers.