Releases

A lead captured in one workspace often has to be worked by another: sales passes it to operations, an enquiry desk passes it to the branch that will service it, a partner workspace picks up an account you sourced. You can now send that lead across, with its details, your brief and the files the customer sent, instead of retyping it into a message or a spreadsheet.

📤 Send a lead to another workspace

Start from the inbox conversation or from the contact in the Contact Hub. The client name, telephone and email fill themselves in from the contact record and cannot be edited, so what you send always describes the person you were actually talking to.

Alongside those details you choose what travels with the lead:

• The request and special notes, in your own words, so the receiving team knows what this lead wants and what you promised.
• Documents, ticked from the files the customer already sent in the conversation. Nothing to download and re-upload, and no second copy taking up your storage.
• Who to notify, chosen from the members of the destination workspace.

The lead arrives as an ordinary contact in the target workspace, ready to work. Matching is done on the phone number, so a customer who has been shared before is updated rather than duplicated.

🔔 The receiving team knows it arrived

Everyone you selected gets a notification in the dashboard and an email carrying the client, the request, the special notes, the document count and who sent it. Both arrive in each person's own language, and the notification links straight to the new contact record.

📋 One log for both sides

A new Handover page sits under MaxCRM, next to Contact Hub, listing every lead shared in or out of your workspace with the date, client, phone, both workspaces, request, documents, status and sender.

• Direction reads from where you stand. The same record shows as Sent in the workspace that shared the lead and Received in the one that got it, so a single log serves both teams.
• Search by customer number, name or notes. Phone numbers match however you type them, with or without the country code and spacing.
• Filters for direction, status and date range, applied across the whole log rather than the page in front of you.
• Progress tracking: the receiving team moves a lead from New to In progress to Completed, from the log, the contact page, or the inbox sidebar.
• Client names link into the contact record, opening the right one for whichever side you are on.

🗂️ History follows the customer

Every lead shared for a phone number appears as Handover history on the contact page and in the inbox sidebar. An agent picking up a returning customer sees at a glance that this person has been through before, and which team handled them.

Select View form on any record to reopen exactly what was sent: the fields, the request, the special notes, who was notified, and each document.

🔐 Who can see what

Leads move only between workspaces that belong to the same account, never outside it. A shared document is readable only by the two workspaces party to that record. Where your account has a single workspace the feature stays hidden, since there is nowhere to share to.

📱 On mobile and in the API

The same capability is available through the API: list shared leads, read one, create one, move its status, and fetch a contact's history. Every endpoint follows the dashboard's rules, so a workspace sees only what it sent or received.

✅ How to use it

1. Open the conversation or the contact for the lead you want to pass on.
2. Choose Send to another workspace.
3. Pick the destination, write the request and special notes, tick the documents, and choose who to notify.
4. Track it from Handover under MaxCRM.

Available in all 11 dashboard languages.

A broadcast is no longer something you start and then just watch. You can stop it, pause it, and pick it back up, and a run that ends early now tells you why.

⏸️ Stop, pause and resume

• Pause a running send and resume it later. It carries on from where it stopped rather than starting over, so nobody is messaged twice.
• Stop a send outright when you spot a wrong template or the wrong audience, without waiting for it to work through the list.
• Automatic stop when WhatsApp blocks the sending number itself, so a broadcast does not keep burning through your list against a number that cannot deliver.

📊 A stopped broadcast stays in your reports

Stopped runs remain in Campaign Reports with the reason recorded, and their failure list is there to open. Previously a stopped broadcast was hard to find afterwards, which is exactly when you most want to look at it.

🎯 Only real account blocks stop a send

Automatic stopping is now much more precise. WhatsApp returns some errors that are about one recipient, not about you: a person who has hit their own marketing message limit, or a number that cannot receive. Those no longer count towards stopping the run.

They still appear in the error report and in the per contact retry, so you keep the full picture. What changed is that a handful of recipient-side rejections no longer ends a broadcast that is otherwise delivering fine.

✅ How to use it

1. Start a broadcast and open it while it runs.
2. Use Pause to hold the send, Resume to continue it, or Stop to end it.
3. Open Campaign Reports afterwards to see the outcome and any failures.

If your bot speaks a language where certain words come out wrong every time, you can now correct them properly instead of respelling the text. ChatMaxima supports ElevenLabs pronunciation dictionaries in both the Audio block and live voice calls.

🗣️ Why respelling was not an answer

The old workaround was to rewrite a word phonetically in the block itself. That falls apart the moment the words are generated at runtime, for example when the spoken text comes from a variable such as an AI response, because there is no fixed text to edit. A dictionary fixes the word everywhere it appears, however the sentence was produced.

📖 Pick a dictionary, not an ID

Create the dictionary in your own ElevenLabs account, then choose it in ChatMaxima from a named list showing how many rules each one holds. The version is filled in for you, which matters because that value never appears in the ElevenLabs dashboard at all.

• Up to 3 dictionaries per block.
• Always current: reopen the block and each row re-points at the dictionary's latest version, so editing a dictionary in ElevenLabs takes effect rather than leaving the block speaking old rules.
• Scoped to ElevenLabs, so a dictionary cannot ride along on a send to another voice provider.

🎙️ Both the Audio block and live voice

The Audio block covers recorded replies, including when your AI agent speaks by calling it. The AI Prompt block's voice section covers real-time voice calls, which run through a different pipeline and needed their own setting.

One thing worth knowing: phoneme rules written in IPA are only honoured by Eleven v3. Other models, including Eleven Multilingual v2, quietly ignore them and speak their default, so ChatMaxima says so in the block rather than letting you build a dictionary that does nothing. Word replacement rules work on any model.

✅ How to use it

1. Create a pronunciation dictionary in your ElevenLabs account and add your rules.
2. In the builder, open an Audio block set to ElevenLabs, or the voice section of an AI Prompt block.
3. Choose your dictionary from the list.
4. For IPA phoneme rules, select Eleven v3 as the model.

Bulk Assign, the tool you already use to set status, agents and departments on many conversations at once, now also marks conversations read or unread.

📥 Two new bulk actions

• Mark as Read, for clearing a backlog of conversations that no longer need attention.
• Mark as Unread, for flagging a batch your team still has to work through.

Both run on the same selection you already make for status and agent changes, and they work on large selections rather than a page at a time, so a queue of dozens goes in a single pass.

⚡ Your inbox updates as it runs

Conversations change state in the open inbox while the bulk action runs, on desktop and in the mobile app, so you are not left refreshing to find out whether it worked. Read receipts on the conversations you mark are unaffected and behave exactly as they do when you open a conversation yourself.

✅ How to use it

1. Open Bulk Assign.
2. Filter to the conversations you want and select them.
3. Choose Mark as Read or Mark as Unread and apply.