Updates for Sep 22: Discord-style presence and recurring meetings

This batch brings four features: team presence, repeating meetings, webhook node testing in Automations, and the conversation an agent starts. Alongside them, dozens of improvements to conversations, voice, and contacts.

Presence and custom status

Everyone in the organization now shows what state they are in, and you pick yours from your avatar menu.

Four states: Online, Away, Do not disturb, and Invisible. The dot shows up in lists, headers, and next to names.
Automatically away after 10 idle minutes; you return to Online as soon as you come back.
Do not disturb silences sound, on-screen alerts, and phone notifications. Counters keep updating — you lose nothing, you just stop being interrupted.
Invisible announces your presence to no one.
Custom status: a line of your own next to your name, with an expiry so it clears itself.

Where: your avatar menu, in the corner of the screen.

Recurring meetings

A meeting can start life as a series instead of being recreated every week.

Pick the weekdays and the time when creating it; the meeting row shows the summary, like “Mon–Fri at 09:00”.
Recurring appears as a label in the list, separating the series from a one-off meeting.
Calendar adds the series to your own calendar, in the right time zone.
Each occurrence opens its own room, and cancelling one does not take down the others.

Where: Meetings → create meeting → Recurring.

Test the webhook before publishing

The Call webhook node in Automations can now be tested right in its panel, without publishing the automation.

Test call runs the real request with the configuration on screen and shows the response below it, under Last call.
Paste cURL builds the node from a command you already have.
The body is written as key-value fields that become JSON with the right types.
The WhatsApp template is found by searching, not by scrolling.

Keep in mind the call is real and variables from earlier steps stay empty in this test.

Where: Automations → open the automation → Call webhook node.

Start the conversation yourself

Until now an exchange only began when the customer wrote first. Now you begin it.

New conversation, in the Conversations list toolbar, takes the phone number and an optional name.
The next step tells you whether the person already has a record, shows their tags, and lists the WhatsApp inboxes.
Start conversation opens the conversation empty, already assigned to you and with AI disabled. You write the message or send an approved template.
The contact record, under Contacts, has the same door.

Only WhatsApp inboxes appear: Instagram and Telegram reach only people who messaged first.

Where: Conversations → New conversation.

Improvements and fixes

WhatsApp’s 24-hour window becomes a state of the composer and offers the template once the window has closed.
Reply quoting a message, and the quote reaches the contact’s WhatsApp. Double-clicking a message also opens Reply.
Text you typed but did not send survives switching conversations and pages.
Bold and italic in each channel’s own dialect: on WhatsApp an asterisk is bold, and Ctrl+B/Ctrl+I mark up correctly on Telegram and Instagram too.
Audio: a waveform with real amplitude, Stop and send, and the composer returns while the audio uploads.
Quick replies you created come first; the organization’s come below.
Contacts store phone and email on the record, and merging duplicates carries both keys over.
{{name}} is now the first name, and {{full_name}} exists for the whole name.
The rooms and conversations column is resizable, and the people list is alphabetical.
Replying in a thread carries over the text you had already typed in the room, and notifies whoever started it again.
WhatsApp template button replies now arrive as messages.
Calls: joining with a failing connection now tells you why — device busy, permission blocked, or a camera this computer does not have.
Meeting notes: people who administer permanent rooms can read their notes again.