Releases

Two people can now work on the same bot at the same time without one of them losing an afternoon. If someone saves while you are editing, ChatMaxima merges the two versions instead of silently overwriting yours.

🔀 What happens when both of you save

When you publish a bot that changed underneath you, the builder no longer rejects the save. It compares the two versions block by block and tells you exactly what the other person did: how many blocks they changed, added or deleted.

• Different blocks and both sets of edits are kept automatically. Nothing is lost and nothing to decide.
• The same block and you are asked to pick a version for that block, with a preview of each side.
• One edited, one deleted and you choose whether to keep the block or accept the deletion.

You can also discard your own changes and reload, if the other person's version is the one you want.

✅ How to use it

1. Edit and publish as normal.
2. If someone saved before you, a merge dialog opens with a summary of their changes.
3. Resolve any block you both touched, then choose Merge and publish.

The combined version is published as one revision, so the bot's history stays readable.

Available in all 11 dashboard languages.

Two new reports show what your Meta ads actually produced: not how many people tapped, but how many held a conversation. You will find them under Reports in the sidebar, as WhatsApp Ads (CTWA) and Meta Ads.

📊 One row per ad

Each report lists every ad that brought you traffic in the window you choose, with:

• Contacts and clicks, so repeat clicks by the same person stay visible separately
• New versus re-engaged, so fresh acquisition is not confused with existing contacts clicking again
• Paid or organic, so post call to actions and tracked links are measured beside paid placements
• Contact detail coverage, the share of that ad's contacts who left an email or phone number

A daily trend chart sits above the table, split between paid and organic, so you can see whether a campaign is still pulling or quietly stalled a week ago.

💬 The number that matters

Every ad row shows how many of its contacts sent more than the opening message. That distinction matters: a Click to WhatsApp ad opens the chat with a message already written, so on paper everybody replies once. The engaged count is the people who said something after that, which is the real difference between a click and a conversation.

👥 The contacts behind each number

Select View contacts on any ad to see the people it brought in, with whether they replied, when they were last active, and an Open chat button that takes you straight to that conversation in your inbox. Contacts who have opted out are flagged so they are easy to leave out of a follow-up, and the whole list exports to CSV.

🚀 How to use it

1. Open Reports and choose WhatsApp Ads (CTWA) or Meta Ads.
2. Set your date window. The default is the last 30 days.
3. Read the engaged column before the contacts column: quality before volume.
4. Select View contacts on your best performing ad and work the list.

Messenger and Instagram figures begin from when ad capture went live on those channels, because Meta does not send referral data for past conversations.

You can now hand a chatbot to someone in a different ChatMaxima workspace without exporting anything or rebuilding the flow by hand. A workspace admin sends a one-time link, the recipient copies the bot into a workspace of their choice, and it arrives ready to open in the builder.

🔗 Sending a bot

Find the bot in your list and choose Share to another workspace. Enter the recipient's email, pick how long the link stays valid, and send it. Both of you get an email with the details.

• One-time link that expires in 24 hours, 3 days, or 7 days, whichever you choose.
• Bound to the recipient, so the link only opens while they are signed in as that address. Forwarding it to anyone else does nothing.
• They pick the destination, so someone who belongs to several workspaces chooses which one receives the copy.
• Admins only, so a bot cannot leave your workspace without an owner deciding it should.

The recipient needs an existing ChatMaxima account before you can share with them.

🔒 What stays behind

The flow is stripped before it travels. Channel accounts, integration connections, and any credentials held inside API blocks stay in your workspace, so the copy can never send on your channels or with your keys.

The recipient gets a plain list of what was removed, so they know exactly what to reconnect on their side. The copy appears in their bot list straight away and will not receive messages until they connect it to a channel of their own.

📋 Tracking and revoking

A Shared bots page lists everything you have sent out of the workspace, with the recipient, the expiry, and the current status: awaiting acceptance, accepted, expired, or revoked. Revoke a share that has not been used yet and the link stops working immediately.

Available in all 11 dashboard languages.

When someone taps a Meta ad and lands in a conversation, ChatMaxima now records which ad it was, on WhatsApp, Messenger and Instagram alike.

📣 One shape for all three channels

Click to WhatsApp was already captured. Click to Messenger and Click to Instagram now are too, and all three are stored the same way, so a flow written once works across every channel.

• Was this an ad? {sys_contact_metadata.ad_referral.is_ad} returns Y or N
• Which ad {sys_contact_metadata.ad_referral.ad_id} and {sys_contact_metadata.ad_referral.ad_title}
• Where from {sys_contact_metadata.ad_referral.source} and {sys_contact_metadata.ad_referral.channel}

🤖 Use it in a flow

The most useful thing you can do is treat ad enquiries differently from everyone else. Add an If/Else block on {sys_contact_metadata.ad_referral.is_ad} and route ad traffic to a qualifying flow, tag it for your sales team, or greet the customer with the offer they clicked.

🔁 Existing setups keep working

WhatsApp contacts still carry the original Click to WhatsApp fields at {sys_contact_metadata.ctwa_referral.ctwa_clid}, {sys_contact_metadata.ctwa_referral.source_id}, {sys_contact_metadata.ctwa_referral.source_type} and {sys_contact_metadata.ctwa_referral.source_url}, so any flow you have already built is unaffected.

The ChatMaxima API now enforces rate limits. If you have an integration running today, this changes what your code can receive, so it is worth a quick look.

⏱️ The limits

Limits are counted per API key, per minute, and apply to api/v2.

• Sending WhatsApp template messages: 300 requests per minute
• Writing contacts and tickets: 120 requests per minute
• Reading lists and records: 300 requests per minute

The send limit sits well above what Meta itself accepts, so a legitimate bulk send is not the thing that will hit it.

📊 Every response tells you where you stand

Three headers come back on every API response, so you never have to guess:

• X-RateLimit-Limit your ceiling for this window
• X-RateLimit-Remaining how many requests you have left
• X-RateLimit-Reset when the window resets, as a Unix timestamp

🚦 What happens when you go over

You get a 429 with a Retry-After header and a JSON body:

{
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Please retry after 24 seconds.",
    "details": { "limit": 120, "window": "60 seconds", "retry_after": 24 }
  }
}

Wait for Retry-After seconds and retry. The window resets on a fixed clock, so a client that backs off correctly recovers on its own.

✅ What to check in your integration

1. Handle 429 as a retry, not as a failure.
2. Respect Retry-After rather than retrying immediately.
3. If you poll for lists, read X-RateLimit-Remaining and slow down as it approaches zero.