Over the past few months, the WAMM.chat team has rolled out dozens of updates across every area of the service. We've made major improvements to the broadcasts section, expanded the capabilities of MAX and Telegram, added reactions and message deletion, new API methods, and many interface conveniences. Some of these updates were initiated by us, others grew out of your support requests — thank you for letting us know where things can be made better. We've gathered everything important into one overview, organized by section rather than by date.

Broadcasts

The broadcasts section received the largest upgrade in recent memory. You can now add tags and an assignee to each broadcast — they'll be automatically applied to all chats that received messages. New columns have appeared in reports: number of chats (not just messages), tags, and the number of chats that replied. An already-created broadcast can now be edited — you can change the interval and sending channel without recreating it from scratch.

File-sending logic has become smarter. Previously, a long interval would also stretch out a "text + image" bundle to a single recipient — recipients didn't understand why they were getting an image with no accompanying text. Now:

  • You can add multiple files to a single broadcast
  • Text and file are sent to one recipient back-to-back, with no delay
  • The interval is applied only between different recipients

Working with the broadcasts list has also become more convenient:

  • A "Download report" button right in the list — no need to open each broadcast
  • Bulk export of reports across multiple broadcasts at once, with the source channel indicated
  • Date range filter (previously — only a single day)
  • The list now shows up to 250 broadcasts instead of 50

Along the way, we fixed a few minor issues: broadcasts now go out properly to WhatsApp and MAX numbers starting with 8, and to Telegram numbers with spaces and formatting characters.

Inbound notifications — now in MAX too

Previously, notifications about new messages only came through the WAMM Telegram bot. Now the same works in MAX. And you can reply right from the notification — tap "Reply", type your text, and the message goes to the right chat. A convenient way to stay on top of things from your phone without opening the interface. Each user connects and configures notifications in their own Profile.

Telegram: reactions, deletion, and stability

We've added several long-awaited things to Telegram that customers have been asking for:

  • Message reactions — visible in WAMM in real time and delivered via webhooks
  • Message deletion (including scheduled messages) — previously you could only edit
  • Video circles in Telegram-bot (already worked for the regular Telegram channel)
  • Auto-updating of chat names and phone numbers — based on events from Telegram, no reloads needed
  • Sender name passed in the API and in webhooks
  • Restoring Telegram channels directly from your account

And one more thing — a new non-delivery status, "STOP SPAM". If Telegram visibly starts limiting sending from your number, we detect it and automatically pause the broadcast to avoid serious blocks. Better to lose an hour than a number.

MAX: extended functionality

We continue to actively develop MAX, especially scenarios involving partial restrictions:

  • A channel in suspended status now works like an authorized one — you can reply to incoming messages and write to people already in your contacts. Only new contacts and broadcasts are restricted
  • The interface now shows when restrictions end
  • We've extended the message deletion window — previously it was only 3 minutes after sending
  • When connecting a channel, contacts and message history are loaded from the phone
  • In MAX Personal you can now see message reactions, text edits, and deletion statuses

For those working with MAX-bot via integrations, a full API for MAX-bot has appeared — receiving and sending messages, just like for other channels.

Interface and workflow conveniences

We've added several conveniences in the account that speed up daily routines:

  • Drag-and-drop files onto a chat to attach them — not just via the paperclip button
  • Sorting the template list by drag-and-drop — arrange the order to suit you
  • A "Clear no-reply indicator" button for an individual chat. If the conversation resumes, the indicator returns automatically
  • The chat counter now responds to the filter and shows the number of filtered chats, not the total
  • You can select multiple values in filters at once — multiple channels, multiple assignees, etc., with the number of matching chats shown
  • Telegram and MAX chat search works by phone number and username (previously — only by name and chat_id)
  • A "Receive messages from group chats" toggle in the channel settings (MAX, Telegram, WhatsApp) — the account administrator can disable group chats for the entire channel with one click, rather than blocking each chat manually

And one more useful detail: when sending from WAMM, a typing indicator is now displayed on the client side for WhatsApp, MAX Personal, and Telegram Personal. This reduces the risk of blocks during active conversations when messages go out too quickly.

One email across multiple accounts + assignee lock

Two changes that large teams will especially appreciate.

One email across multiple accounts. If, for example, you have two departments with different CRMs and each needs its own WAMM account, but the managers are the same — previously you had to create new email addresses. Now the same address can be used in different accounts, and a new account can be registered on an email already in the system. When signing in with such an email, the system will ask which account you want to enter. You can switch freely between accounts.

Assignee lock for a chat. A toggle has appeared in each user's profile: whether to become the assignee when sending a message. If it's turned off, the manually assigned person remains the assignee even when you reply in the chat. Convenient when chats are assigned to specific managers and colleagues only cover temporarily: no need to figure out later whose client this originally was. To write into someone else's chat without "taking it over", just turn this setting off in your profile.

API: new methods and fields

For those working with WAMM through integrations:

  • A full API for MAX-bot — receiving and sending
  • A new method for getting a Telegram chat_id by phone number
  • The phone_real field has been added to contact_get, msg_get_last, msg_get — no need to look up the number separately
  • The user_chats method without specifying a user now returns all open chats of the channel (previously — only those with assigned operators)
  • The msg_get_last response now includes the api_id of the source channel — no need to determine the channel with an additional request
  • The webhook correctly populates the phone_acc field (previously it could come through empty)
  • The method for getting messages by phone number now works for MAX too (previously — only by chat_id)
  • Stable webhooks with outgoing message statuses for MAX and Telegram
  • The phone number and username are correctly saved in the contact card when sending via API and via broadcast in MAX and Telegram

Website widget

The messenger and social network button widget for websites has gained position and size settings — now it can be fitted into any design without overlapping the close buttons of other elements or popups.

Other small things

  • The contacts and messages export for Telegram and MAX now includes a column with the phone number (ID)
  • A second Russian bank account (Tochka) has been added to the requisites and invoices

What's next

We're working on WAMM.chat systematically: some things we do to follow the overall product direction, others — based on customer requests. Thanks to everyone who writes to support with suggestions: without you, half of these improvements wouldn't have happened.

If any of the above is useful to your team but it's not clear how to use it — drop us a line, we'll help you set it up.

And to lift the curtain a little on what's coming: in the near future — integration with VK and our own chat widget for websites (not just messenger buttons, but a live chat right on the page, with conversations in a single WAMM window alongside other channels). Further out — AI-powered features for working with conversations and integrations with popular CRMs. We're not announcing dates in advance, but that's the direction — we'll share more as we get closer to launch.

Ready to improve customer communications?

Start using WAMM.chat right now!

Request a call Sign Up