real WhatsApp groups of up to seven arrive once Meta approves the business
account. The demo on that page shows the approved experience, so it needed
saying.
from the footer.
requirements for real WhatsApp groups.
The home page now says plainly that rooms run on the relay right now, and that
New press kit at /press with facts, boilerplate, assets and a contact, linked
Two-step verification is now on for the Chilly number, which clears one of the
Beta 1.7
Money, measured.
plan, rooms, last activity and whether their workspace is paying. Phone
numbers stay encrypted and are never shown.
collected, every subscription, and what the service costs to run, split
between model tokens, WhatsApp conversations and fixed hosting.
token counts, and every person reached on WhatsApp is counted once a day,
because WhatsApp bills per conversation and not per message.
The admin area now has three tabs: Overview, Users and Revenue.
Users lists every person across every workspace with their role, workspace,
The new Revenue page reports recurring revenue, what has actually been
Cost is now measured rather than guessed. Every model call records its real
While Stripe stays in test mode, every revenue figure is labelled as test money.
Beta 1.6
Sign in with Google.
Managers can sign in with a Google account as well as an email link.
The consent screen carries the Chilly Chat name, logo and our own domain, because the flow runs in our code rather than through a third party.
Beta 1.5
Every email now looks like the same product.
Sign-in, confirm, invite, change-email and password-reset emails carry the Chilly Chat design instead of the stock template they shipped with.
All five are version controlled in the repo, so they can be changed deliberately rather than by hand.
Beta 1.4
Ready to host real users.
Sign-in links now send through our own domain. The previous setup was capped at a handful of emails an hour and would have failed silently on launch day.
Nothing fails quietly any more: failed deliveries, a room hitting its daily ceiling, a WhatsApp outage or email trouble all raise an incident, show on the dashboard and email whoever needs to know.
An hourly self-check watches the WhatsApp connection, quality rating and email delivery, and clears the alarm by itself when a problem passes.
Flood and join-attempt limits on inbound messages.
Estimated daily cost alongside usage in the admin dashboard.
First automated tests, covering encryption, quiet hours, engine choice and the message formatting rule that broke delivery earlier today.
Beta 1.3
The relay now behaves like a room, not a bot.
Reply to any message and everyone sees what you were answering, quoted above your words.
Consecutive messages from the same person no longer repeat their name, the way a real chat app groups them.
Chilly marks your messages as read, so you can see it picked them up.
Joining tells you who is already in the room; leaving tells the room.
Your first message comes back with confirmation of how many people received it.
Members in more than one room see the room name on each message, so nothing is ambiguous.
Beta 1.2
Groups eligibility, measured rather than assumed.
Tested the WhatsApp Groups API against the live number: Meta returns "not eligible" because the account is not yet an Official Business Account.
Admin dashboard now tracks every requirement for the green tick with live values read from Meta.
Wrote up the application plan, including the fact that an API group holds only 7 people plus Chilly.
Beta 1.1
Email and teams.
Weekly reports now arrive by email as well as WhatsApp, with a per-workspace address you choose in Settings.
Managers are told by email when a member switches analysis off, and can turn that notice off.
A welcome email when a workspace is created.
Invite co-managers by email. Invitations expire after 14 days and can be revoked.
Admin dashboard shows email delivery health and the last ten messages sent.
Beta 1.0
First public beta.
Relay engine for rooms of any size, with the native WhatsApp group engine behind a flag until Meta approves it.
Tension detection with a single neutral intervention per thread, and one private nudge per unanswered question.