Changelog

16 October 2026 — sums, dates and text in workflows, ten more apps, records in any CRM module, and fewer “connect ETIMEDOUT” send failures

New

• Change how a detail looks before it is sent. In any workflow step, click Insert, then Change it next to a detail. Pick from about 90 changes in plain words: show money as money, add 18% GST, round a number, put a name in capitals, keep only the first name, show a date as “Thu, 15 Oct at 2:30 pm”, move a date 3 days later, show the time in another country, count the days until a booking, add up a list, and more. The Try it box shows the answer with an example before you insert it. See Workflows for the full list.
• New step: Do a calculation. Type a sum using details from the workflow, like the order total times 18%, and keep the answer for later steps. The answer appears under the box as you type. If a detail is empty you choose whether to count it as 0 or stop, and if a detail is words instead of a number, the step stops and tells you which one.
• New step: Change a value. Start with any detail, add changes from the same list, and keep the result, for when several later steps need the same changed value.
• If / Else rules can compare a worked-out value. Click the wand next to a rule’s detail to change it first, for example “days since the order is more than 3”.
• Ten more apps in workflows. Workflows can now use Zoom (create a meeting and send the link), LeadSquared (find, add and update leads, log activities, create tasks, change scores), ElevenLabs (turn text into a voice note), Canva (fill in a design or export one), Bitly (shorten a link), Razorpay (create a payment link), IndiaMART (read what a buyer asked about), Google Business Profile (get your review link), Facebook and Instagram (post to your Page or account) and X (post). Connect them under Integrations first.
• More you can do with Google in workflows. Besides adding a row to a sheet, a workflow can now send an email from Gmail, add an event to Google Calendar (and invite the customer), read upcoming events, find a file in Google Drive, and translate text.
• Look people up in your other apps. New workflow actions find a customer in HubSpot, Zoho CRM and Salesforce, read a Zendesk or Zoho Desk ticket, find a Trello card, read or cancel a Shiprocket order, and find a WooCommerce product.
• Save records in any CRM module, including your own. Workflows and chatbots can now create or update a record in any Zoho CRM module, HubSpot object or Salesforce object, not only Leads and Contacts. Your own custom modules, like “Site Visits” or “Admissions”, appear in the list by the names you gave them, with their own fields. Choose to always create a new record, update the one that already has the same phone or email, or update a record you name. Required fields are shown so you can fill them in, and a value that comes out empty is skipped, so it never wipes what is already in your CRM. In a workflow, use the new Create or update a record action on the Zoho CRM, HubSpot or Salesforce step. In a chatbot, add Zoho CRM: Save a record, HubSpot: Save a record or Salesforce: Save a record.
• A help page for Workflows. It explains how to use details in a step and lists every change you can make, with examples.

Changed

• Find steps with everyday words. In the workflow and chatbot builders, you can search the way you talk: “pause” finds Wait, “label someone” finds Add a label, “add up” finds Do a calculation, “create meeting” finds Zoom. Plurals, filler words and the order of words no longer matter.
• Workflow steps explain themselves on the canvas. Each box now shows what kind of step it is, its number in the run, and a sentence saying what it will do, like “Waits 2 days” or “Sends ‘Hi First name’ to the customer”. Details show as small labels instead of codes. Boxes also show hidden settings (only if, retries, a note), what they pass on to later steps, and “not connected” when no line leads to them, so they would never run. Router paths are named on their lines.
• The Insert list shows what earlier steps saved. Under Saved values you now see each saved name, like “result (from Do a calculation)”, instead of one general entry.
• A warning for misspelled changes. If a detail uses a change name that doesn’t exist, the builder warns you before you switch the workflow on, instead of quietly skipping it.
• Typed dates are read the Indian way. In workflow details, a date like 05/10/2026 now means 5 October, and a date without a time is read on your business’s clock, not the server’s. Businesses using US dollars still get the American order.

Fixed

• Everything on the MotherBot AI page is readable. The 1, 2, 3 step numbers under “How it works” were white on white and couldn’t be seen. In dark mode, the step circles, the icons on the “What I can make for you” cards and the small pictures on them were also hard to read. They now use colours that stand out in both light and dark mode.
• Wait steps on the canvas say how long they wait. Every Wait box only said “Wait”, whether it waited ten minutes or ten days, and “Wait for a reply” and “Remember a value” boxes didn’t show their settings either. They now do.
• Money written as “Rs. 1,250” is read correctly. The number and money changes misread amounts that start with “Rs.”: “Rs. 1,250” came out as 0.125. They now read the amount.
• Messages no longer fail with “connect ETIMEDOUT”. Sometimes a template, a chatbot reply or another WhatsApp action failed with an error starting “connect ETIMEDOUT” or “ENETUNREACH”. This happened when WhatsApp took a little longer than usual to answer: MotherBot gave up after a quarter of a second. It now waits the normal time, so these sends go through. If a message failed this way, send it again.

15 October 2026 — mixed template buttons, a guide for AI tools, and a truer features page

New

• A guide to MotherBot for AI assistants. If you or your developer use ChatGPT, Claude or another AI tool to build with MotherBot, give it motherbot.io/llms.txt for a short guide, or motherbot.io/llms-full.txt for everything: every API call, every webhook event, every key permission and every integration in one plain-text file. Both update themselves whenever we add something.
• Quick replies and link or call buttons in one template. When you create a template on the web or in the phone app, choose Both under Buttons to add quick replies together with link, call or offer code buttons. Meta allows this as long as the quick replies stay together, so you choose whether they come before or after the other buttons. People using WhatsApp on a computer are asked to open these messages on their phone.

Changed

• The features page now lists everything you can use. Workflows, MotherBot AI, WhatsApp Groups, using the WhatsApp Business app on the same number, appointments and table booking, WhatsApp calling for your team, reports by email, the spending limit and send approvals, and the MCP server for AI assistants were missing. They are listed now.
• Correct numbers on our website. Our pages said 38 webhook events and 34 integrations; there are now 74 events and 36 integrations, and the pages now count them for you. Logos for apps we don’t connect to directly (Stripe, Freshdesk, Notion and Make) were taken off the features page.
• The AI integration page describes what is really there. It now names all seven AI providers you can connect (OpenAI, Google Gemini, Anthropic Claude, Meta Llama, Grok, DeepSeek and Groq) and the steps you can use in a chatbot, instead of features that were never built.
• Up to 10 buttons on a template. The web template form stopped at 3 link, call or Flow buttons. Meta allows 10 buttons in all, and so does MotherBot now. The preview shows what customers see: the first 2 buttons and a See all options button for the rest.
• An offer code can sit next to links, calls and quick replies. The Offer Code button had to be the only button on a template. Meta allows it with link, call and quick reply buttons, so you can now add those too. It still can’t be used with Flow, WhatsApp call or Share Number buttons.
• Offer codes can be 20 characters long. The sample offer code was limited to 15 characters. Meta now allows 20.

Fixed

• Chatbot messages now show when they are delivered, read or failed. Messages sent by a chatbot on WhatsApp, including chatbots started by a workflow, stayed at one grey tick in Live Chat even after the customer got and read them. Now they get two ticks when delivered, turn blue when read, and show when sending failed. They also now count towards your WhatsApp spending. This applies to messages sent from now on.
• Ticks no longer get stuck when WhatsApp replies very fast. If WhatsApp said a message was delivered or read before MotherBot had finished saving it, for example when a chatbot sends several messages in a row, that update was lost and the message stayed at one tick. MotherBot now keeps the update for a few minutes and applies it as soon as the message is saved.
• Saving a draft in the phone app no longer removes its quick replies. If a draft template had quick replies and a link or call button, opening it in the phone app showed only the link or call button, and saving it deleted the quick replies. Both kinds now open and save.
• Copying or editing a template with both kinds of buttons works on the web. Its quick replies used to show up as broken link buttons. They now show as quick replies, in their original order.
• A link, then a quick reply, then another link is caught before sending. Meta refuses buttons in that order, and a refused template’s name can’t be used again. MotherBot now stops it before it reaches Meta and asks you to keep the quick replies together.
• Offer codes are sent to Meta in the format Meta documents. The web template form sent the sample offer code in a different shape from Meta’s examples. It now matches them. Templates you already made keep working.
• Broadcasts with an offer code no longer fail to send. A broadcast using a template with an offer code made in the web form could stop with an error instead of sending. It now sends the code.
• The phone app no longer deletes buttons it can’t show. Opening a draft with an offer code, Flow, catalogue, WhatsApp call or Share Number button in the phone app and saving it removed that button. The app now asks you to edit that draft on the web instead.
• Limited-time offer codes stay at 15 characters. Meta allows 20 characters for coupon templates but still 15 for limited-time offers, so the limited-time offer form keeps the 15-character limit.
• Labels on the template form are the right size. On the template form, the category and button type names, and the URL, Phone and Offer Code choices, showed at full size unless selected. They now match.

14 October 2026 — clear message when your AI key runs out of credit

Fixed

• “Didn’t answer” now says what’s wrong when your AI key has no credit. If your own AI key is on a prepaid Google Gemini account (or DeepSeek) with no credit left, MotherBot AI said “didn’t answer, please try again” every time — and trying again could never work. Chatbot AI replies, AI Copilot and workflow AI steps now recognise this and say your key has run out of credit.
• MotherBot AI keeps answering when your own AI key stops working. If your own key runs out of credit, uses up its free requests, or is refused, MotherBot AI now finishes your request with the daily messages included in your plan, at no charge to you, and adds a short note telling you to top up or check your key under Integrations → AI Providers. Once your key works again, MotherBot AI goes back to using it. If MotherBot AI can’t stand in, you see a message about your key instead.

14 October 2026 — Zendesk tickets for new contacts, and fixes

New

• Move a table booking to another table. In Appointments → Restaurant → Floor, every open booking now has a Move button: pick another table and, if you like, a new time. A booking with no table yet can be given one. The guest keeps the same booking reference. In the MotherBot app, tap a table on the Floor screen and choose “Move to another table”.
• See every note where a teammate mentioned you. In Live Chat, the new @ button next to the search box lists the notes where someone tagged you. Click one to open that chat. In the app, it’s the @ button at the top of Chats.
• A contact’s consent history, right beside the chat. In Live Chat, the contact panel now has a Consent history section: every opt-in and opt-out for that person, how it was given, and when. In the app, open a chat’s actions and choose Consent history. Only team members who can view consent see it.
• Add a past WhatsApp chat to a contact. On the Contacts page, the new clock button on a contact lets you upload a chat you exported from the WhatsApp app on your phone (Export chat gives you a .txt file, or a .zip with the photos and voice notes). You choose which name in the chat is you, and the messages appear in that contact’s conversation with their original dates, marked “Imported”. Adding the same chat again only adds new messages. These messages are a record only: nothing is sent, they don’t open the 24-hour window for free replies, and they don’t count in your reports or Sent History. Ask MotherBot support to turn this on for your business.
• Put an imported chat in your CRM. After adding a chat, you can add it to Zoho CRM, Salesforce, HubSpot or LeadSquared. For each one, choose how each day of the chat goes in: as Notes, on the Timeline (a completed task or activity — in HubSpot, a WhatsApp conversation), or Both. You can also attach the whole chat as one file. In Zoho CRM you can choose the record yourself: a Lead, a Contact, or a record in any other module, including your own modules such as Channel Partners. If the person isn’t in your CRM yet, we tell you, and Try again carries on from where it stopped. To remove a chat you added by mistake, open the same window and choose Remove this chat.

The app parts arrive with the next MotherBot app update.

Fixed

• The appointments calendar moves a month at a time in Month view. In Month view, Previous and Next moved by one week, so it took several clicks to reach the next month. They now move a whole month.
• Quotation actions run once. Clicking an action on a quotation twice in quick succession — for example Duplicate or Send follow-up — could run it twice. A second click now waits for the first to finish.
• A/B tests on SMS and RCS show Version A properly. Version A is the message you type above, but its row said “The template chosen above”. It now shows your message.
• The quotation preview matches the PDF. A title, note, term or watermark made only of spaces showed an empty heading on screen but not in the PDF. Both now leave it out.
• Disconnecting Calendly ends MotherBot’s access at Calendly too. Before, we only forgot the connection on our side.
• Setting a first password in the app is recorded in the activity log. It now shows as “password set”, the same as on the web.

Changed

• Unused parts removed. We removed parts of MotherBot that no screen used any more, on the web and in the MotherBot app. Nothing you use has changed. In the app, this arrives with the next app update.

13 October 2026 — Groq joins the AI providers

New

• Connect Groq under Settings → AI. Groq gives very fast replies from open AI models such as Llama and GPT-OSS, and has a free tier to start on. Once your Groq key is connected, you can use it everywhere the other AI providers work: AI steps in chatbots and workflows, the ready-made chatbot templates, AI Copilot in Live Chat, the website chat assistant, Call AI Analysis, and MotherBot AI. Its models are listed straight from Groq, with Automatic first. Groq bills you directly for what you use.
• In the MotherBot app too. You can choose Groq and paste your key when setting up AI Copilot in the app you have now. Call AI Analysis in the app works with Groq now; its name shows properly from the next app update.

Fixed

• A key added under the wrong provider is caught. Groq (groq.com) and xAI Grok have similar names. A Groq key saved under xAI Grok was accepted, and then every AI reply failed. Saving it now tells you which provider the key belongs to — on the web and in the app.
• The ready-made chatbot list opens again. After an update earlier today, the list of ready-made chatbots could fail to open. It opens again.
• Chatbots on xAI Grok or DeepSeek can be switched on. A chatbot with an AI step could be refused as “AI not connected” when your only AI key was for xAI Grok or DeepSeek. Every provider now counts.
• Changing to a plan without AI removes every AI key. xAI Grok and DeepSeek keys were left in place when an account moved to a plan that doesn’t include AI. All AI keys are now removed, as the plan change says.

13 October 2026 — AI models that stay up to date

Changed

• Every list of AI models now comes straight from your AI provider. Wherever you choose an AI model — AI steps in chatbots and workflows, AI Copilot, Call AI Analysis and Settings → AI — the list is now read from your provider with your own key, so it only shows models you can use today. Before, it was a fixed list that could include models your provider had stopped offering.
• New choice: Automatic. Automatic always uses your provider’s recommended model and moves to newer ones as they come out, so you never have to update it. It’s the first choice in every list and the setting for anything new. A model you picked before stays as it is.
• A model your provider stops offering no longer breaks replies. If the model you chose has been withdrawn, chatbot replies, workflow AI steps, AI Copilot and Call AI Analysis now use your provider’s recommended model instead of failing. When Automatic is set and a model is overloaded, the next one is used.
• Ready-made chatbots use your AI provider. AI steps in the ready-made chatbot templates now use the AI provider you connected, set to Automatic, instead of always asking for OpenAI.
• Training keeps working when newer models come out. Products and knowledge bases now train with your provider’s recommended training model when you haven’t chosen one. Each knowledge base remembers the model it was trained with and keeps using it, so its search answers stay correct after a newer model is released.
• In the MotherBot app too. The model lists for AI Copilot and Call AI Analysis in the app now come from your provider as well, with Automatic first. This works in the app you have now.

Fixed

• Training with Google Gemini works without picking a model first. If you hadn’t chosen a training model, training products or a knowledge base with Gemini used a model Google has withdrawn, so it failed. It now uses Google’s current one.
• Settings → AI no longer shows models you can’t use. “Models your chatbots can use” was a fixed list. It now shows what your key can actually use, and asks you to connect your key first if you haven’t.

13 October 2026 — template search, address requests and synced Flows

New

• Search your templates in Cards view. A search box now sits next to the account and status filters. It looks in each template’s name, message text and button labels, and the category counts follow what you type.
• See the real header image in a template’s preview. The preview on the Templates page showed “[IMAGE HEADER]”. It now shows the image itself, plays a video header, and shows a document header as a tile you can click to open the file in a new tab. If a template has no sample file saved, the preview says so.
• Bold, italics and lists look as they will on WhatsApp. Template previews on the web and in the MotherBot app now show WhatsApp’s formatting instead of the symbols: *bold*, _italic_, ~strikethrough~, ```monospace```, `code`, bulleted and numbered lists, and quotes. This covers the Templates page, the template editor, broadcasts, sequences, templates you’ve sent in Live Chat, and the app’s template list and preview. Words like order_id and sums like 5*3*2 are left as they are, just as WhatsApp leaves them.
• Clearer numbers in Tutorials. In the step-by-step guides under Tutorials, each number and its label can now sit on any side of the part of the screen it points to, with space around it, so it no longer covers the button you need to see. Labels can run in any direction, and numbers come in three sizes.
• Step-by-step guides for MotherBot AI. Under Tutorials → Automation → MotherBot AI there are seven short picture guides: how to find and use MotherBot AI, and how to have it make a WhatsApp template, contacts, a segment, a chatbot, a workflow and a WhatsApp Flow form — from typing your request to switching it on.
• Actions on every row in Table view. Each template in the table has a Preview button and a menu with Edit draft, Use in Broadcast, Duplicate, Copy name, Copy message text, Get API code and Delete — the same things you can do from a card. Clicking a row opens its preview.

Fixed

• Emojis show in Excel when you export your sent messages. Opening the Sent history export in Microsoft Excel on Windows turned emojis into odd symbols like “😀”, and names in Hindi and other languages were garbled too. The file now opens with every emoji and every language as you sent them. All your other exports already did this, and now none can miss it.
• Address requests with pre-filled details now send. When you filled in a name, street, city or PIN code before sending an address request, WhatsApp turned the message down every time. It now goes through, with those details already filled in for your customer to check. This also fixes address requests saved as quick replies.
• A clear reason when WhatsApp won’t send one. WhatsApp only lets businesses in India ask customers in India for their address. When you sent one from a number outside India, Live Chat showed “(#131009) Parameter value is not valid”. It now tells you the number isn’t an Indian (+91) number, so you know to send it from your Indian WhatsApp number.
• WhatsApp Flows synced from Meta now show their screens. A flow you built in Meta’s own Flow Builder came across with its name and status but an empty form, so there was nothing to see or edit. Pressing Sync on the WhatsApp Flows page now brings in every screen and question too — including flows synced before today. Flows you built here are never replaced by Meta’s copy. If a flow’s screens can’t be downloaded, the message names that flow, and the next sync tries it again.
• Ready-made workflows can be switched on again. Workflows started from a template that send a message — such as Welcome a new customer, Rescue an abandoned cart and Follow up a lead — opened with “1 to fix” saying “Who to send it to is needed”, even though the box already showed “The customer this run is about”, and Switch on stayed greyed out. That choice now counts, so these workflows switch on as soon as their real blanks are filled. Your own workflows with the same step are fixed too.
• MotherBot AI names the right button for workflows. After saving a workflow, MotherBot AI told you to press “Activate”, but the button on the workflow screen is Switch on. It now says Switch on.
• Chatbot steps made by MotherBot AI have proper names in the builder. Question steps and hand-over-to-your-team steps showed just “Node” at the top of the box in the chatbot builder. They now say “Question” and “Hand over to a person”. They always opened and worked normally.
• One field that did nothing is gone. The “Country (name)” box in the address request form was never shown to your customer. It has been removed.
• Numbers that also use the WhatsApp Business app: old chats no longer unlock free replies. When past chats were brought in from the app, a customer who had written just before you connected looked as if they could get a normal reply. WhatsApp only allows a template message there, so the reply failed. Live Chat now goes by messages that arrive after you connect.
• Photos and files in past chats now show. Pictures, videos and files from the last 14 days before you connected stayed as “Unsupported”. They now appear in the chat. Older ones (WhatsApp doesn’t send these) say to open the WhatsApp Business app on your phone to see them.
• Edited messages are updated, not added again. When a customer edited a message, or your team edited one in the WhatsApp Business app, Live Chat added it as a new “Unsupported” message and could send your away message again. Now the original message changes and shows “Edited”. This applies to every WhatsApp number.
• Past chats don’t sign people up for broadcasts. Someone your team only ever messaged from the WhatsApp Business app was added as a contact who agreed to receive broadcasts. They are now added without that agreement. Customers who messaged you first are still recorded as agreeing, as they are for any first message.
• See how bringing in past chats is going. Under Settings → WhatsApp Accounts, a number that also uses the WhatsApp Business app now shows whether its past chats are on their way, how far along they are, or that chat history sharing was turned off in the app. Large histories are also saved more reliably.
• Clearer messages and safer broadcast speed for these numbers. A message only the app can show now says “Open the WhatsApp Business app on your phone to see this message” instead of “Unsupported message”. Broadcasts from these numbers send at most 20 messages a second, which is WhatsApp’s limit for them, so messages are no longer turned down for going too fast. Past messages also show the right ticks (read or failed) instead of all showing as delivered.
• In the MotherBot app: past chats in the right place. Chats brought in from the WhatsApp Business app appeared at the bottom of the conversation, all dated the day they were brought in. They now sit in order with the date they were sent. Messages only the WhatsApp Business app can show also explain that in the app, instead of “This message type can’t be shown”. These work in the app you have now.
• In the next MotherBot app update: edits and past-chat progress. Edited messages show “Edited”, an open chat updates by itself when a message is edited or deleted, and WhatsApp Accounts shows how bringing in past chats is going.

12 October 2026 — MotherBot AI sets things up for you

New

• Describe it, and MotherBot AI prepares it. Open Automation → MotherBot AI and say what you need in your own words. It can prepare WhatsApp templates, WhatsApp Flows (forms), chatbots, workflows, contacts and segments, and change your existing chatbots, workflows and segments.
• A daily allowance for each plan. How many messages you can send MotherBot AI each day now depends on your plan, and shows on your Usage page. It starts again at midnight in your time zone.
• Upload a spreadsheet of contacts from the chat. Use the paperclip → Spreadsheet of contacts, or the Upload a spreadsheet button MotherBot AI offers. It opens the same import as the Contacts page — any size, added in the background.
• Faster answers. When an AI model is overloaded, MotherBot AI moves to another one straight away instead of waiting, remembers which models are struggling, and finishes most requests in fewer steps.
• Reach it from anywhere. Every dashboard page has a MotherBot AI button in the top bar. On Templates, Chatbots, Workflows, WhatsApp Flows, Segments and Contacts it reads “Create with AI” and opens with your request already started. Or press g then a.
• A chat that works like the AI tools you know. Search your chats, see them grouped by day, edit and resend a message, and press Try again if an answer didn’t come through.
• Copy anything it writes. Every message — yours and MotherBot AI’s — and the text of each template and chatbot step has a Copy button.
• Nothing happens until you press the button. Everything it prepares appears as a preview card with one clear button — for example “Submit to Meta for approval” or “Create chatbot (switched off)” — and a Discard button. Chatbots are created switched off, workflows and Flows are saved as drafts, and templates go to Meta only when you confirm.
• It writes as your business. It reads your business profile, your WhatsApp business profile, your knowledge base, your quick replies and your products, so messages use your name and your details. It doesn’t make up prices, hours or links — it asks you instead.
• It follows your plan. It only uses steps and apps your plan includes and that you have connected, and tells you when you have reached a plan limit.
• On every plan, Free included. You can send a set number of messages to MotherBot AI each day, at no extra charge. If your plan includes AI and you have added your own AI key under Settings → AI, it uses your key instead — with the newest suitable model your AI provider currently offers, checked automatically — and your AI provider bills you for that use.

Fixed

• Free Google Gemini keys go further. Google gives free keys a small number of requests a day for each model. When one model’s free requests run out, MotherBot AI now moves to a lighter model that still has some, and each message uses fewer requests. When they are all used up it says so plainly — your key is on the free tier — instead of saying it ran out of credit.
• MotherBot AI keeps going when Google is busy. When a Gemini model was overloaded, MotherBot AI answered “didn’t answer” straight away. It now waits and tries again, then moves to another model your key can use, so your request still gets done.
• New-style Google Gemini keys work everywhere. Google now issues Gemini keys that start with “AQ.”. With one of these, AI replies in chatbots, knowledge-base search, the Test button and the model list failed as if the model did not exist. They now work, and so do older keys.

12 October 2026 — Live Chat picks the right WhatsApp number

Changed

• Conversations open on the number they were last active on. If you have more than one WhatsApp number, Live Chat now opens each conversation on the number with the most recent message — sent or received. Before, it used the number the customer last wrote to, so after you replied (or sent a broadcast) from another number, the chat still opened on the old one and your next reply went out from a number the customer hadn’t heard from lately. You can still switch numbers from the menu at the top of the chat.
• Live Chat starts on your most active number. Before you open a chat, Live Chat now starts on the number your business last used, instead of the first one in the list (which could even be disconnected).
• The app replies from the same number. Replies and scheduled messages sent from the MotherBot app go out from the number the conversation was last active on — the same number the web opens it on.

11 October 2026 — your time zone, everywhere

Fixed

• Zoho CRM notes and calls show your time. Message notes said things like “5:30 AM UTC” for a message that arrived at 11 am. They now show your time and your time zone, and calls logged in Zoho start at the right time.
• Salesforce activities land on the right day. A message logged just after midnight was filed under the day before. It now goes under your day.
• Mapped date fields in Zoho and Salesforce. “Contact created” and “last reply” dates you map into a CRM field are now written in your time zone. They are still the same moment, so date fields keep working.
• Google Sheets rows are dated in your time. New leads and contacts added to your sheet were stamped with the server’s clock. The Date column now shows your time, including rows added from the app.
• Google Calendar events from chatbots are at the right hour. An event booked for “10:00” was created at 10:00 UTC — 3:30 pm in India. It is now created at 10:00 your time.
• Dates inside your messages. Order dates from Shopify and WooCommerce, Calendly time slots, Google Calendar event lists, a contact’s “added on” and “last message” dates, quotation dates, and IndiaMART’s enquiry date and time now use your time zone. Shiprocket orders created by a chatbot carry your date and time too.
• Date filters cover your whole day. Filtering Sent History, Contacts, Calls, Quotations, Broadcasts or IndiaMART leads by date used the server’s day, so “up to 11 Oct” left out the evening of 11 Oct — and on Quotations it left out the whole day. Each date now means midnight to midnight in your time zone.
• Dashboard counts start at your midnight. “Today” and “this month” on the dashboard, “won this month” in Deals, and this month’s AI usage now begin at midnight in your time zone, not at 5:30 am.
• Quotation numbers in the new financial year. A quotation created just after midnight on 1 April was numbered as part of the year that had just ended. It now starts the new year.
• Exports show your time. Every export — contacts, calls, conversations, consent, ad performance, call analysis, quotations, appointments, form answers, IndiaMART leads, and any table you export — now writes times in your time zone (for example 2026-10-11T11:00:00+05:30) and names the file with your date. Spreadsheets and tools that read the old files read these the same way.
• Scheduled report emails are labelled with the right dates. The “yesterday” or “past week” dates at the top of your report email now match your calendar.
• Editing a scheduled message keeps its time. Opening a scheduled message to edit it showed the time on your computer’s clock, so saving it unchanged could move it. It now shows your business time.
• “Broadcast rescheduled for…” is readable. It showed a raw time code. It now shows the date and time in your time zone. Workflow runs held for quiet hours say when they will continue in the same way.
• Calendly and Zoom messages. When Calendly doesn’t say which time zone the customer is in, the booking time is now shown in yours instead of UTC. The Zoom meeting time in a WhatsApp message uses your Zoom default time zone, or your business time zone if you haven’t set one.
• Account transfer emails. The “offer expires” time is shown in the receiving business’s time zone.
• Billing emails show the right date. Payment, renewal and cancellation emails from MotherBot are dated in Indian time, the same as your invoices, instead of a day early late at night.

Changed

• Every screen uses your business time. Broadcasts, Live Chat (message times and the day headers), calls, sequences, appointments, the support desk, number health, integrations and the rest now show times in your time zone, whichever country your computer or phone is in. “Today” on the appointments and table bookings screens is your business’s today.
• Scheduling uses your business time. “Send later” in Live Chat, scheduled broadcasts and Zoom meetings read the time you pick in your business time zone. The earliest time you can pick, and quick choices like “In 1 hour” or “Tomorrow morning”, are based on your business’s clock.
• Shop quiet hours use your business time zone. Quiet hours for Shopify and WooCommerce messages (including abandoned-cart reminders) now follow Settings → Organization → Timezone, instead of the shop’s own time zone — or UTC when the shop didn’t report one.
• Zoom’s default time zone follows yours. New Zoom connections use your business time zone until you choose a different one in Zoom settings.
• Phone notification quiet hours use your business time zone — the same as notifications in your browser.
• Daily send limits reset at your midnight. The daily limits for the Chrome extension, the Zoho CRM widget, Google Sheets & Excel and the WordPress plugin used to reset at 5:30 am in India. They now reset at midnight in your time zone.
• Zoho CRM widget. The time you pick when scheduling a send, and every time in History, now use your business time zone rather than the Zoho user’s browser.
• WordPress chat bubble hours. The “Business hours” you set for the chat bubble are now read in your MotherBot time zone rather than the WordPress site’s.
• Google Sheets: date cells are read as the sheet shows them. A date typed into a sheet set to a time zone ahead of India could arrive a day early. It is now read in the sheet’s own time zone.

10 October 2026 — broadcasts on Telegram

New

• Send a broadcast on Telegram. With your Telegram bot connected, choose Telegram under “Send on” when you create a broadcast — on the web or in the app. It goes to everyone who has started a chat with your bot. Telegram has no 24-hour window and no templates, so you can write whatever you like and send it any time, and Telegram doesn’t charge for it.
• Everything a Telegram bot can send. Pick what to send: a message (with a picture, video, GIF, file, music, voice note or sticker), an album of 2–10 pictures and videos, a poll or quiz, a location pin, a named place, a contact card, or one of Telegram’s dice and games. Use {{contact.name}} and the other contact details to personalise it.
• Link and reply buttons. Put up to 10 buttons under a message, one to three per row. A link button opens a web page. A reply button sends its label back as the person’s answer — it shows in Live Chat, reaches your chatbot, and counts as a click on the broadcast report.
• Poll votes come back. Each vote shows in Live Chat as the answer they chose and counts as a reply. (Turn on anonymous voting and Telegram stops telling your bot, so those votes can’t be counted.)
• Recurring broadcasts on Telegram. A recurring broadcast — every week, every month, or on each customer’s birthday or anniversary — can now go out on Telegram too. Each time it comes round it sends a normal Telegram broadcast you can open and report on.
• Tags and segments work on Telegram. Choose all your Telegram contacts, a tag, or a saved segment. On Telegram the segment’s rules are checked against each Telegram contact, so a “VIP” segment reaches your VIPs’ Telegram chats — including people who also talk to you on WhatsApp.
• Replies are counted. When someone answers a Telegram broadcast, the reply is tied to it, so the broadcast report shows who replied.

Fixed

• WhatsApp and SMS broadcasts no longer include Telegram followers. A Telegram chat number looks like a phone number, so a WhatsApp or SMS broadcast to “everyone” or to a segment used to try to send to your Telegram contacts as if they were phone numbers. Those sends failed — or could have reached a stranger. They are now left out, so the number of recipients you see is the number who can really receive it.
• “Its WhatsApp account no longer exists” when launching. The launch confirmation, on the web and in the app, looked for a WhatsApp number on every broadcast — so SMS, RCS and Telegram broadcasts could be created but never launched. It now checks the right channel and shows who it’s sent from (for example “Telegram · @yourbot”) and what it costs.
• Replies in the Broadcast performance report. The report showed 0 replies and a 0% reply rate for every broadcast, on every channel. It now counts the real replies, the same number the broadcast’s own page shows.
• No more “0% read” for channels that can’t report reads. Telegram and SMS never say when a message is read. Reports, the broadcast page and the app now leave the read figure blank (“—”) for them instead of a 0% that looks like a bad result.
• A Telegram chat number is no longer shown as a phone number. Sent History, the message details and the Sent messages report showed Telegram contacts with a made-up “+” phone number. They now show the person’s @username, and the Phone column holds only real numbers.
• Resume and Retry work for SMS and RCS broadcasts. Pressing Resume on a paused SMS or RCS broadcast, or Retry on its failed messages, used to stop with “WhatsApp account not found”. Both now carry on, on the right channel.

Changed

• The channel is named everywhere. The broadcast page shows a WhatsApp, SMS, RCS or Telegram badge and says what it was sent from; each message in Sent History says its channel; and every report has a Channel column.
• “Smart send time” now shows only on WhatsApp broadcasts. It appeared on SMS and RCS broadcasts too but was never applied there, so it has been removed from those screens rather than left as a switch that does nothing.

10 October 2026 — no more double sends from Google Sheets and Excel

Fixed

• Pressing “Confirm & send” twice no longer sends twice. On a big sheet, the button gave no sign it had been pressed, so people pressed it again and every row got the message two or three times. The button now locks the moment you press it, shows a spinner, and says how many people it is sending to. The Send button also shows a spinner while it reads your rows.
• A send can’t go out twice, even after an error. If the add-on loses touch with MotherBot during a send and you press Send again on the same rows, MotherBot recognises it and shows the first send’s result instead of messaging everyone again.

10 October 2026 — deleted contacts and clearer call errors

Fixed

• A number you deleted can be found again. When someone had messaged you on WhatsApp and also through your website chat, Contacts showed them once. Deleting them removed the WhatsApp contact but left the website chat one hidden. Contacts looked empty, but adding the number again said it was “already in your contacts”. Now the website chat contact shows in Contacts after a delete, so you can open it or delete it too. Contacts hidden this way before the fix appear the next time you try to add their number.
• A clearer message for a number you already have. It used to say “on the webchat channel”. It now tells you the person messaged you through your website chat, and to search for them in Contacts.
• A clear reason when you’ve asked to call someone too often. WhatsApp limits how often you can ask the same person for permission to call them. When a broadcast or a Live Chat message went over that limit, you saw a long technical error from Meta. It now says you asked this contact recently, to wait a few days, and that a call with them that connects resets the limit. Broadcasts also stop retrying these messages, because every retry would be refused too.

10 October 2026 — Live Chat stays where you are reading

Fixed

• Scrolling up in a chat works. When you scrolled up to read older messages, the chat kept jumping back to the bottom: when older messages loaded, when a message was delivered or read, and when the customer wrote. It now stays exactly where you are reading.
• A “New messages” button instead of a jump. If a customer writes while you are reading further up, a “New messages” button appears at the bottom of the chat. Click it to go to the latest message. If you are already at the bottom, or you send a message yourself, the chat still moves down on its own.
• Opening a chat goes straight to the latest message. It no longer slides down from the top. On a phone, a chat used to open at its oldest message instead.
• Older messages load on a phone. Scrolling to the top of a chat on a phone never loaded the earlier messages. It now does, the same as on a computer.

10 October 2026 — the right templates in Google Sheets

Fixed

• Templates follow the WhatsApp number you pick. In the Google Sheets add-on, the template list loaded once for the first number, and switching to another number kept showing that list. It now reloads every time you change the number.
• Every template you can send is listed. When two of your numbers share one WhatsApp Business Account, they share its templates. The Google Sheets, Excel, Chrome, Zoho and WordPress add-ons only showed the templates saved under the number you picked, so some approved templates were missing. They now show all of them, as your dashboard does. Lists are no longer cut off at 200 templates.

New

• The Google Sheets add-on tells you when to update it. The add-on is code you paste into your own sheet, so our fixes only reach you when you paste the new version. From now on, the add-on shows “Update available” when a newer version is out.

10 October 2026 — contact imports run in the background

New

• Start an import and get on with your day. When you import contacts from a CSV or Excel file, we upload it in a few seconds and do the importing on our side. You can close the window or leave MotherBot. When it’s done, you get a notification on your phone and in your browser, plus an email, showing how many contacts were added, updated and not imported.
• See every import on the Contacts page. Imports that are running show their progress at the top of the Contacts page, and ones that finished in the last day show their result. Click Recent imports to see your last 20. Each report lists the rows that weren’t imported and why, such as “Not a phone number we can use” or “The same number is earlier in the file”, with each row’s number in your file. You can download those rows, fix them and import them again.
• Stop an import part way. Click Stop on a running import. Contacts that are already in stay in.
• Choose the country code for your file. The import now asks which country code to use for numbers that don’t have one. It starts on your own country’s code. It is only added to numbers with 10 digits or fewer; longer numbers already have a code and are kept as they are. Before you import, it shows how many numbers will get the code.

Changed

• Much faster imports. We now check and save many rows at once instead of one at a time, so large files finish much sooner.
• A new notification setting. “Contact import finished” is on for everyone. You can turn it off in Settings, then Notifications, on the web or in the app. Only the person who started an import is told about it. Staff see only their own imports; admins see everyone’s.

10 October 2026 — the right country code on your contacts

Fixed

• Numbers without a country code get your country’s code. When you typed or imported a number without a country code, some accounts got the wrong code in front of it, for example +94 (Sri Lanka) instead of +91 (India). This happened when your business phone number had been saved without its country code. We now use the country in your organization details, so an Indian account always adds +91.

Changed

• You choose the code in Settings. Go to Settings, then Organization, then Country. The code for that country is added to every number you add without one, whether you type it, import it or another app sends it in. The page now shows which code that is. A change takes effect straight away.

10 October 2026 — announcements that fit your phone

Changed

• A fresh look for our offers, festival greetings and notices. The bar at the top of the page, the card on your Home page and the popup have all been redesigned. They are easier to read, can show a small tag such as “Limited time”, and show the time left on an offer as a clear countdown. Some announcements now have no button at all, just a message you can read and close.
• Swipe between announcements. When more than one is showing in the top bar, a thin line shows when the next one is coming. Swipe it on a phone, or tap the dots, to move between them. Pointing at it or moving to it with the keyboard pauses it.

Fixed

• The announcement bar fits on a phone. On a phone, the bar squeezed the headline, the countdown and the close button into one line above the page title, so the headline was cut into a few words per line. The headline now has the full width, and the countdown and button sit on their own line underneath.
• The menu button no longer covers the announcement. On full-screen pages such as Live Chat, the phone menu button sat over the first words of the announcement bar. It now moves down below the bar.
• The popup has room around it on a phone. It used to touch both edges of the screen with square corners. It now has a margin and rounded corners, and scrolls on its own on a short screen.

10 October 2026 — integrations in plain words

Changed

• A clearer Zoho CRM Extension tab. It now starts with three steps to get going: make your token, paste it into Zoho, switch it on. Each step is ticked once it’s done, and a line tells you when the last message went out from Zoho. Every setting has an icon, a one-line description and a “?” for more, grouped under What your team can do, Limits, Who can use it and WhatsApp calls. Phone fields, the History list in Zoho and your own Zoho modules each sit in a card you open when you need it. Making a new token now asks you first, because the old one stops working straight away.
• Every integration explains itself in everyday words. We rewrote the descriptions, buttons, settings and messages on all of the Integrations cards, from Zoho, HubSpot and Shopify to IndiaMART, the property portals and the AI services. Words like “webhook”, “sync”, “node” and “auth token” are gone wherever you don’t need them. Where another app makes you look for a field by its own name, such as LINE’s “Webhook URL”, we still use that name so you can find it. Messages like “Failed to save settings” now say what happened and what to do, for example “Couldn’t save your settings. Please try again.”
• A proper WhatsApp look on the Channels page. The WhatsApp section, its card and the WhatsApp Button card now show the WhatsApp logo on its own green tile, the same way Telegram, LINE and Viber appear beside it. The card says how many of your numbers are working.
• The Messenger and Instagram card says what it does. It only mentioned posting to your Page. It now says first that it brings your Facebook Page messages and Instagram DMs into Live Chat.

Fixed

• “Connect” and “Manage” show on phones and tablets. On the Integrations and Channels cards, the “Connect” or “Manage” link only appeared when you pointed a mouse at the card, so on a phone or tablet it never showed. It now always shows on touch screens, and appears when you move to a card with the keyboard too.
• Zoho CRM shows the right region. Once connected, Zoho CRM showed your region with the wrong web address, for example “US (us.zoho.in)”. It now shows the real one, such as zoho.com or zoho.in.

10 October 2026 — the phone apps on iOS 27 and Android 16

Changed

• The Android app turns sideways on tablets and foldables. On a tablet or an unfolded foldable, the app now follows the way you hold the device instead of always staying upright. Android 16 asks every app to do this on large screens. On phones the app stays upright, as before.
• A clearer template library in the phone app. The template library — the book icon at the top of Templates — is easier to browse on iPhone and Android. More templates fit on the screen, each card shows a short preview with how many details you fill in and how many buttons it has, and long descriptions are no longer cut off. Tap a template to see the whole message, what you'll fill in and anything to do before you submit, with Use this template always in view at the bottom. The back arrow returns you to the same search and filters. The library opens faster too, and a Clear filters link resets your search in one tap.
• Search panels keep their size while you type. In the phone app, panels you search in — the template library, Send a template, Quick replies, and long lists such as Country and Language — no longer shrink and grow with every letter you type.
• A leaner Android app. The next Android update is built with extra size and speed optimisations that Google Play recommends, so the app uses less memory on your phone.

Fixed

• “Tomorrow morning” means tomorrow. When you scheduled a message before 9 AM, Send later → Tomorrow morning picked 9 AM the same day. It now always picks 9 AM tomorrow. After 6 PM the evening choice reads Tomorrow evening, and every choice shows its time the same way, such as 12:15 PM.
• The Android app opens reliably. The part of the Android app that handles WhatsApp calls could close the app the moment it opened, before the sign-in screen appeared. The next Android update fixes this.
• Panels in the iPhone app fit the screen again. In the latest test version of the iPhone app, panels that slide up from the bottom — such as New broadcast after you pick a template, or the actions list in a Live Chat conversation — were wider than the screen. Text ran off both edges and the fields were pushed out of view. They now fit the screen, and long text wraps onto the next line.
• The iPhone app opens on iOS 27. The first test version of the app made for iOS 27 closed the moment it was opened, before the sign-in screen appeared, because iOS 27 asks every app to start up in a new way. The next update starts up the new way and opens normally. If you were testing that version, install the next update when it arrives.
• Super Admin’s Channels page loads again. The page listing every connected WhatsApp number, Facebook Page, Instagram account, Telegram, LINE and Viber bot, SMS, RCS and email sender and website chat showed an error instead of the list. It now loads.

9 October 2026 — clearer messages, and more fixes for phones

New

• Offers, festival greetings and notices from MotherBot. You may now see announcements from us — an offer, a festival greeting, or notice of planned maintenance — as a bar at the top of the page, a card on your Home page, or an animated popup that appears once. Some include a countdown to when an offer ends. Most can be closed with the ✕ and won't come back; closing one on the web closes it in the app too. Urgent notices, such as planned downtime, stay until they end.
• A clearer Zoho CRM settings page. Each setting now has an icon, a one-line description and a “?” you can tap for more. Every field mapping is a card that shows which way the data goes — for example “Zoho Lead → Segments” — and how many fields are set up, without opening it. Pick Leads or Contacts with one tap. The webhook details for developers are tucked away at the bottom. Salesforce, HubSpot and LeadSquared field mappings get the same cards.
• Use the Zoho record owner in your broadcasts. Open Zoho CRM → Settings and choose which owner details to copy onto your contacts: name, first name, last name, email, phone, mobile or role. Save each one in its own field or in one of your custom fields. They then appear as variables when you send a broadcast, so a message can say “Your advisor Asha will call you from +91 98260 00001”. When you give a lead to someone else in Zoho, the details update on the next sync. Name and email work straight away. Phone, mobile, last name and role need permission to read your Zoho user list, so if you connected Zoho before 9 October 2026, disconnect and connect it once more.
• Build segments by Zoho record owner. Every owner detail you copy from Zoho is now a field in the segment builder, such as “Zoho owner name is Asha Rao”. You pick from the owners your contacts actually have instead of typing a name. Like Lead Status, the segment checks Zoho again before it counts and before a broadcast sends.
• Owner details in broadcasts sent straight to Zoho leads. When a broadcast’s audience is your Zoho Leads or Contacts, each template variable can now be filled with the record owner’s name, first name, last name, email, phone, mobile or role.
• Zoho leads and contacts can come in on their own. Until now, connecting Zoho CRM did not add anyone to your MotherBot contacts. Only the Import buttons did, once, and the hourly sync just kept existing contacts up to date. Now you can open Zoho CRM → Settings, switch on “Bring Zoho records into MotherBot” and tick Leads, Contacts or both. Every 15 minutes, new Zoho records are added as contacts with their Lead Status and other mapped fields. A status you change in Zoho reaches your segments within 15 minutes too. It is off until you switch it on. Contacts you already have are connected to their Zoho record rather than added twice, and anyone who has opted out stays opted out.
• A MotherBot button next to every phone number. With the Chrome extension, a small round button now appears after phone numbers on the websites you visit. Click it to send a WhatsApp message, add the person to your customers, or copy the number. It is on by default: Chrome asks you once to allow it, and you can hide it on any site or turn it off in the extension’s settings. MotherBot only looks for numbers in your own browser and never sends the page anywhere.
• More extension settings. Choose what the button does, its size, which numbers get one and the sites where it’s hidden. Choose the side the message box opens on and the message type it starts with. “Choose for me” picks a template when the customer hasn’t written in 24 hours. You can also set a country code, ask again before sending to many people, and close the box after sending.
• Saved replies and shortcuts in the extension. Insert your Quick Replies into a text message, open a customer’s chat in MotherBot from the message box, and use Alt+Shift+W to message the number you selected.

Changed

• Street address is optional when you set up your account. On the Finish Setup page you still choose your country, state and city — your state decides how GST is split on your invoices — but the street address can be left blank and added later in Settings.
• Clearer, more accurate legal policies. We rewrote our Privacy Policy and Terms of Service for India’s Digital Personal Data Protection Act and the IT Rules, and added a Cancellation & Refund Policy and a Data Processing Addendum. They now say exactly where your data is kept (our database is in Mumbai and our servers are in Singapore) and how long each kind of data is kept. Messages are never deleted on a timer. Plan prices are shown before GST, with 18% GST added. They also explain how to use your rights and how to reach our Grievance Officer. The Cookie Policy now lists only the cookies we really use. We use no analytics or advertising cookies.
• The Chrome extension keeps your data closer. Only the website’s name, never the full page address, is sent with a message, and you can switch even that off. Your access token is only sent over a secure (https) connection, and parts of the extension that run on websites can no longer read it. Files over 10 MB are refused straight away instead of after a long upload. Remembering recent numbers is off unless you switch it on.
• Clearer steps to turn on WhatsApp calls. When calls are off, the Calls page now says exactly where to switch them on: Integrations, then WhatsApp, the settings button next to your number, the Call tab, and Allow Voice Calls. The extra step in Meta’s own App Dashboard is only shown if you connected a number with your own Meta app.
• New accounts never reply to customers on their own. Since 1 October 2026 Meta charges for replies after the first 1,000 each month on every number. So a new account starts with every automatic reply switched off: the away message, the satisfaction question, the STOP and START replies, the missed-call message, the website chat assistant, chatbots, workflows and sequences. Nothing sends until you switch it on yourself. Accounts that already have these switched on are not changed.
• Big numbers fit in small spaces. On the Billing page’s usage bars, Number Health and the phone app’s Usage screen, large figures now show as 1.3K, 5M or 2.1B instead of 50,00,000. Point at a figure (or use a screen reader) for the exact number.
• 70 more icon buttons say what they do. Copy, search, add and show-or-hide buttons that showed only a picture now have a label when you point at them, and screen readers read it out.

Fixed

• “Number protection is off” is said once, not over and over. If you switched number protection off, a broadcast that Meta was holding back sent you the same warning email and phone alert every half hour for as long as it ran, and the Number Health page filled up with copies. You now get that warning once per broadcast. The checks shown before you launch, and the banner on the Number Health page, appear in full the first time and as one short line after that.
• No more “[object Object]” in Zoho broadcasts. In a broadcast sent straight to Zoho leads, a variable filled from a Zoho field that links to another record could reach your customer as the words “[object Object]”. It now sends the linked record’s name.
• The Finish Setup page no longer opens blank after your first sign-in. After signing up with email and signing in for the first time, the Finish Setup page could stay empty until you refreshed it. It now opens straight away.
• No saved logins in the WhatsApp setup form. When you connect a WhatsApp number by entering its details yourself, your browser or password manager could fill the Phone Number ID, WABA ID and Access Token boxes with a saved email and password. Those boxes now start empty and are only filled by what you type.
• Tutorial buttons stay in one place. In tutorials, the step description and its Next button switched between the left and right of the screenshot from one step to the next. They now always sit on the right, so Next is where you left it.
• Zoho Lead Status segments count every imported lead. On the Zoho CRM integration, “Import Leads” and “Import Contacts” added your customers but did not keep which Zoho record each one came from. So MotherBot could not read their Lead Status, and a segment like “Lead Status is Contacted” counted only some of them. Imports now keep that link and read the Lead Status straight away. Customers you already had are connected to their Zoho record instead of being skipped. Imports also used to stop at 2,000 records without saying so; now every lead is brought in, up to your plan’s contact limit. If you imported from Zoho before, press Import again to bring in the rest — nobody is added twice.
• Calls counts cover all your calls. On the Calls page, Inbound, Outbound, Missed and the cost estimate only counted the calls on the page you were looking at, while Total Calls counted all of them. All five now count every call that matches your filters.
• The Calls page fits on a phone. The counts at the top now sit two to a row, and each call shows its details on one line and its status, length, cost and time on the next. Before, everything was squeezed into one line until it overlapped.
• The menu button stays in the right place. On a phone, when a billing notice or the “you are viewing as” banner was showing, the menu button sat over the banner or was hidden under it. It now moves with the page title.
• Short error words became clear sentences. Some messages showed a single word such as “forbidden”, “Unauthorized” or “Not found”. They now say what happened and what to do, for example “You don’t have permission to do this. Ask your admin if you need it.” This also covers errors shown on the page itself, not only in pop-up messages.
• The Home greeting matches your time of day. In the evening in India, Home could briefly say “Good afternoon” before changing. It now greets you by your own clock.
• Pages with “5 minutes ago” times open smoothly. On Flows, Contacts, Live Chat, Broadcasts and other lists, a page could flicker and redraw itself while opening if a minute ticked over at that moment. Times like these now load cleanly.
• Tables no longer make the page slide sideways on a phone. On some pages a wide table pushed the whole page sideways. The table now scrolls on its own and the page stays put.
• The phone app and more lists never send everything at once. If a page size or number of days in a request was not a number, some lists, including contacts, messages and conversations in the MotherBot phone app, returned every record in one go. They now return a normal page.
• Exports are checked the same way everywhere. Contacts, quotations and calls exports now share one check that stops a name starting with “=” from running as a spreadsheet formula.
• Choosing a product searches your whole catalogue. In the chatbot builder, quotations, Live Chat and Quick Replies, the product list only held your first 100 products, so in a bigger catalogue the rest could not be found or picked. Typing now searches every product.
• The chatbot builder works on a phone. The list of steps and the checks now open over the canvas with a button, and a step’s settings open full screen, so the canvas is no longer squeezed to nothing.
• Unsubscribing from the MotherBot newsletter works. The “Unsubscribe” link in our newsletter went to the home page. It now unsubscribes you straight away, and Gmail and Outlook show their own unsubscribe button too.
• Security updates for email, spreadsheets and images. We updated the parts of MotherBot that send emails, read the spreadsheets you import and resize pictures to their latest safe versions. Nothing changes in how they work for you, and search in the help assistant gives the same answers as before.
• Small PDFs upload to the Knowledge Base every time. A short PDF, such as a one-page price list or opening hours, often failed with “We couldn’t read this file” or was wrongly called a scanned image, then worked on another try. Small PDFs now read correctly the first time.
• Reports for very large broadcasts download smoothly. To fill in the Response and message data columns, the broadcast report first gathered every reply in the whole broadcast before writing a single row. On a broadcast to hundreds of thousands of people that could slow the download down or stop it. It now works through the replies a batch at a time. The report itself is exactly the same.
• “Rows per page” shows a number again. On Calls, Products and some other lists, the “Rows per page” box under the table was empty. It now always shows how many rows you are looking at. Those lists now show 25 rows to start with instead of 20.

For platform administrators

• Revenue figures were 100 times too small. Super Admin’s dashboard, Analytics and the admin screens of the phone app divided every payment by 100 a second time, so ₹5,000 showed as ₹50. They now show the real amounts.
• Dashboard cards open the right list. Total Organizations, Active Subscriptions, On Trial and Past Due opened the plan editor; they now open Organizations filtered to exactly what the card counts, and the numbers match the list. Failed Payments, New Contact Queries and Partner Applications open filtered too, and the support card now counts the chats in “Needs reply”.
• Filter organizations by plan. Organizations has a new Plan filter.
• Pick any organization or partner. The organization filter and the organization field on a user only listed the first 200 organizations, and partner filters loaded every partner. You now type to search them all.
• Filters name what they filter by. An organization or partner filter that was already set when the page opened showed “Selected” until you opened the filter panel. It now shows the organization’s or partner’s name.
• Platform alert links open that organization’s users. Clicking a platform alert opened Users & Organizations on the Organizations tab with nothing filtered. It now opens the Users tab showing only the accounts of the organization the alert is about. Alerts you already received work too.
• Payments covers every payment. The page showed the newest 200, so its totals, search and filters missed the rest. It now pages through all of them, and its totals cover everything that matches.
• Long lists load a page at a time. Contact queries, partner applications and newsletter subscribers used to load everything at once. Partner application counts no longer change with the status filter.
• Newsletters send in the background. A large list used to time out the Send button. Sending now carries on by itself, shows its progress, and picks up where it stopped after a restart, without emailing anyone twice.
• Marketing WhatsApp numbers can’t be added twice. Adding or editing a number with a phone number ID that is already saved now says so clearly. Adding a new default number that failed to save used to leave no default number at all; the current default now stays until the new one is saved.
• Channels stays fast on a large platform. The Channels page is now worked out by the database instead of loading every organization into memory. Its results are unchanged.

8 October 2026 — MotherBot on your phone, and a better Calls page

Fixed

• The menu opens on a phone again. On a phone, the menu button in the top-left corner was hidden under the page title, so you could not open the menu to go to another page. You can now.
• Pages fit on a phone screen. Appointments, Broadcasts, Chatbots, Contacts, Messages, Quick Replies, Sequences and the carousel and offer template page were wider than a phone screen, so you had to scroll sideways and some buttons were cut off. Buttons that do not fit now move to the next line, and long rows of tabs scroll on their own. On Messages, the list and the open conversation now take turns on the screen, with a Back button.
• Buttons at the top of a page fit on a phone. On pages such as Products, the page’s own buttons pushed the page name and your account menu off the screen. On a phone they now sit on their own line under the page name.
• Buttons that appear when you point at something now work on touch screens. Some buttons only appear when the mouse is over them, such as Edit, Delete and Hide on Quick Replies. Phones and tablets have no mouse pointer, so these buttons never appeared there. They now always show on touch screens, and also show when you reach them with the Tab key.
• Calls search looks through every call. The search box on the Calls page only looked through the calls on the page you were viewing. It now searches all your calls, by contact name or by part of the phone number.
• Calls export includes every call. Export CSV on the Calls page stopped at 5,000 calls without telling you. It now includes every call that matches your filters and your search.
• The Account filter on Calls works for team members. A team member who can use only some of your numbers, and chose one number in the Account filter, still saw calls from all of them. They now see only the number they chose.
• Exported names can’t run as spreadsheet formulas. A customer’s WhatsApp name that starts with “=” could run as a formula when you opened the Calls export in Excel or Google Sheets. It now shows as plain text.
• Plain words when your internet drops. If your connection dropped, or MotherBot took too long to answer, some messages showed computer text such as “Failed to fetch” or “Unexpected token”. They now say what happened and what to do.
• Clear microphone messages on WhatsApp calls. When there was no microphone, or another app was using it, the call screen showed your browser’s error text. It now tells you what to do, such as plugging in a headset or closing the other app.
• Lists from the API never return everything at once. If a request asked for a page size that was not a number, some lists, including messages, contacts and calls, returned every record in one go. They now return a normal page.

Changed

• Calls and Call Analysis look like every other page. Both now have the same top bar as the rest of MotherBot, with search, light and dark mode, and your account menu. “Agent Scorecards” is now called Call Analysis everywhere, to match the menu.
• Every icon button says what it does. About 140 buttons that showed only a picture, such as a bin, a pencil or an arrow, now show a short label when you point at them, and screen readers read it out.
• Cleaner browser tab names. Many tabs said “MotherBot” twice, for example “Settings MotherBot | MotherBot”. They now read “Settings | MotherBot”, and team, admin and partner pages end in “MotherBot Staff”, “MotherBot Admin” and “MotherBot Partners”.
• The copy buttons in Live Chat show a copy icon. The buttons that copy an order, an address or a catalog number showed a paperclip, which looks like “attach a file”.

8 October 2026 — a faster Broadcasts list, and AI calls that hang up

Changed

• The Broadcasts list loads one page at a time. It used to load every broadcast you have ever sent, which got slower every month. Cards now show 50 at a time with page numbers at the bottom. Search, filters, sorting and the counts in the account and status menus still cover all your broadcasts, not just the page you are on, and Export still downloads every broadcast that matches.

Fixed

• “Retry available” and sequence badges show on the Broadcasts list. They were never shown there, and the Retry available filter in Table view matched nothing. Both work now.
• Team members see the SMS and RCS broadcasts they have access to. A team member limited to certain WhatsApp numbers didn’t see any SMS or RCS broadcasts on the Broadcasts page, even when allowed to use those channels. They now do, following the channels in their access settings.
• A link to an older broadcast opens it. Opening a link to a broadcast that isn’t on the first page said “That broadcast isn’t on this account”. It now shows the broadcast at the top of the list.
• AI calls you place end when the customer hangs up. When the customer hung up, or declined or missed the call, the AI agent stayed on the line until it timed out on its own, using AI call minutes. It now ends straight away.

8 October 2026 — security and speed on busy accounts

Fixed

• Files your customers send can’t run in your browser. A web page or SVG image sent to you as a document used to open inside MotherBot, where it could act as you. These files now download instead. Photos, videos, voice notes and PDFs open exactly as before.
• Quotation images come only from your own files. The tool that puts signatures and logos into quotation PDFs could be pointed at files outside MotherBot. It now loads only images uploaded to MotherBot.
• Your business username shows for every number. For numbers connected through Facebook sign-up, a username you reserved or changed in the WhatsApp Business app never appeared in MotherBot. It now updates within moments.
• Chatbot conversations stay in order. When a customer sends several messages quickly, the chatbot answers them one at a time. After a brief connection problem, this could switch off until MotherBot restarted, so replies could arrive out of order. It now carries on by itself.
• A slow pattern can’t hold up your messages. A chatbot, flow or workflow rule that checks a pattern, written in a way that takes extremely long to check, could hold up message handling. Each check now stops after a fraction of a second. Ordinary patterns work exactly as before.
• MotherBot recovers from a brief database outage by itself. A short outage just as MotherBot started could leave it showing errors until it was restarted. It now reconnects on its own.
• “Resend verification email” is limited to 3 a minute. Each email cancels the link before it, so pressing it repeatedly only made the earlier emails stop working.

Changed

• Pictures and documents in Live Chat load faster. Before showing an attachment, MotherBot checks that it belongs to your account. On accounts with a long message history, that check looked through every message; now it goes straight to the one it needs.
• Broadcasts and the Home page load faster. They used to download the full recipient list of every broadcast sent to an uploaded list, even though none of it is shown on screen. They no longer do. Nothing you see has changed.
• Live Chat stays quick while a big broadcast sends. MotherBot can now handle more work at once, so chats and incoming messages no longer wait behind a large broadcast.

7 October 2026 — Zoho CRM History follows what you select

Fixed

• One record open: only that number. History used to show everything you had sent, whichever contact you were looking at. It now shows only the messages sent to that record’s number — from Live Chat, broadcasts, chatbots, the API and Zoho.
• Several records selected: only those numbers. Select records in a list view and History shows the messages sent to just those people.
• Nothing selected: everything on that WhatsApp number. Opened without a record, History shows everything your team sent from Zoho on the WhatsApp number chosen in Send from.
• History respects WhatsApp Account Access. If you limit which Zoho users can use which WhatsApp numbers, the same limits now apply to History. People not on the list see no history, and others only see messages from the numbers they’re allowed to use.

New

• Choose what History shows. Under History in Zoho you can choose, separately for when records are selected and when nothing is selected: messages from all of MotherBot, only messages sent from Zoho, only each person’s own messages, or no history. History only lists messages you sent, never your customers’ replies.
• Batches and Scheduled have their own settings. For each list, choose whether it shows everyone’s sends, only each person’s own (the default, as before), or nothing. Both lists now also follow what’s selected in Zoho, like the Messages list: open a record and you see only the batches and scheduled sends that went, or will go, to that number. Batches sent before today only appear when nothing is selected.
• Only the person who scheduled a send can cancel it. That stays true even when your team can see each other’s scheduled sends.

8 October 2026 — very large broadcasts and reports

Fixed

• Very large broadcasts launch reliably. Launching a broadcast to hundreds of thousands of people loaded everyone’s full details and every message into memory at once. It now works through the audience a thousand people at a time. Who receives it, in what order and how fast are all unchanged.
• Smart send time works on big audiences. A broadcast with smart send time on, sent to more than about 125,000 people, failed with an error before sending anything. Fixed.
• A launch, resume or retry never hangs. If the sending queue stopped responding part-way, the broadcast could sit at “Running” with nothing sending, and the page kept waiting. The broadcast is now paused with a clear message, and pressing Resume sends to everyone it hadn’t reached. Nobody receives it twice.
• Resume and Retry work on broadcasts of any size. On broadcasts of around 800,000 people or more, Resume and Retry failed outright. They now work through recipients a thousand at a time.
• Broadcast report downloads start straight away. The Excel report is now sent while it is being written, instead of being built in full first, so even a report of a million recipients downloads without running the server out of memory. Its contents are exactly the same. A broadcast with more than 1,048,575 recipients continues on a second sheet (“Details 2”), because that is the most rows Excel can hold on one sheet.
• The launch screen counts your audience faster. It now counts the people a broadcast will reach instead of loading every one of them first.
• Desk reports open faster on busy accounts. The Desk dashboard’s response times, resolution times and ratings are worked out with far less memory. Every figure is the same as before.
• The Desk agent table shows only what each person may see. A team member limited to their own chats, to some channels or to some WhatsApp numbers was shown every colleague’s name and how many chats each had open. They now see only the agents and chats within their own access. Admins see the whole team, as before.
• The Terms describe Meta’s pricing as it is today. They said Meta charges per conversation. They now say Meta charges for each message it delivers and for calls your business places, in 6-second pulses.

8 October 2026 — only delivered messages count towards your costs

Fixed

• Undelivered messages are no longer counted as spent. A message was added to your monthly spend as soon as Meta accepted it, so one that later failed still counted. It is now added only when it is delivered (or read). Messages counted before today are not counted again.
• Reports show undelivered messages as not charged. In the message cost report, a message that was only sent, or that failed, now shows Not delivered — not charged and costs nothing.
• A broadcast’s cost counts delivered messages only. The broadcast page shows what it will cost if every message is delivered and what it has cost so far, counting only the messages delivered. It uses the same rates as your budget.
• Calls are shown per 6-second pulse only. No screen shows a per-minute call rate any more. Each call is rounded up to whole pulses, so a 50-second call is 9 pulses. The cost calculator on the WhatsApp pricing page now asks how many calls you make and how long each one lasts.
• Clearer wording on the pricing pages. The plans page now says your first 1,000 replies each month on each number are free and the rest are charged by Meta, and that calls are charged per 6-second pulse. The partner page no longer talks about “conversations”, which Meta stopped charging for.
• Calls logged from CallBix no longer go back to an older state. If an older update about a call arrived after a newer one, it could undo the newer details. Older updates are now ignored.

8 October 2026 — costs that match Meta's bill, and a faster Live Chat

Fixed

• Meta’s prices are shown and used to three decimals, everywhere. Every rate — per message, per reply, per call pulse — now shows at most three decimals (₹0.863 for a marketing message, ₹0.389 per call pulse), and every estimate, report, calculator and budget figure is worked out from that same three-decimal rate, so what you see is what is counted.
• WhatsApp calling charges, spelled out on the pricing page. The WhatsApp pricing page now has its own calling section — free for calls customers make, ₹0.389 per 6-second pulse for calls you make — with worked examples from 6 seconds to 5 minutes, call rows in the rate table, and calls in the cost calculator.
• Reports show each message’s cost to three decimals, so a ₹0.863 message no longer reads as ₹0.86 and subtotals add up to the rates they come from. A reply sent since 1 October 2026 that Meta never priced is now shown as Estimated at the reply rate instead of Free; replies sent before then were free and still show so. Messages sent from the WhatsApp Business app on a coexistence number cost nothing and show as Free.
• A message is never counted twice in your budget. When Meta sent the same delivery update twice — which it does whenever our server is slow to answer — that message’s cost was added to your monthly spend again. Each message is now counted once, from Meta’s own pricing for it.
• No more marketing charges for messages Meta didn’t price. If a delivery update arrived without Meta’s pricing details, the message was counted at the marketing rate. It now waits for Meta’s pricing and uses the category Meta billed it under.
• International one-time codes are counted as authentication messages, not marketing.
• Broadcast costs use your own rates and Meta’s verdict for each message. The launch preview, the broadcast estimate and the broadcast report now use the same rates as your budget (including any you entered under Settings → Budget). The report’s actual cost counts only the messages Meta charged for, at the category Meta billed — free messages count as nothing.
• Free-form broadcasts show what they may cost. A broadcast sent as replies to customers whose 24-hour window is open used to show no cost. It now shows the reply rate, with a note that your first 1,000 replies each month on each number are free. Free-form bulk sends from the extensions and Zoho are no longer priced at the marketing rate when checked against your budget or sent for approval.
• The broadcast stats API counted read messages three times. GET /api/v1/campaigns/:id/stats added sent, delivered and read together, so a read message was charged three times in estimatedCost. It now counts each message once and adds freeCount for messages Meta didn’t charge.
• The budget screen says exactly what a hard stop stops. Broadcasts, drips, bulk sends, store and integration messages, templates sent by workflows, and SMS, RCS and email stop. Replies to customers — Live Chat, chatbots, the AI agent and workflow chat messages — keep sending, so nobody is cut off mid-conversation. The screen used to say chatbots and automations stop, which they didn’t.
• Workflows stop sending templates when your budget’s hard stop is reached. A workflow’s template step used to keep sending — marketing templates included — after the budget was spent. It now stops, and the run history says why.
• Live Chat no longer loads every conversation. Searching, or filtering by label, channel, Mine, Unread, Resolved and the other quick filters, made the browser load your contacts 100 at a time until it had all of them — slow, and very slow with a large address book. These are now answered by the server, one page at a time, and search waits until you stop typing. Search also finds chats by email address and WhatsApp username.
• Deleting a WhatsApp number no longer hangs. Removing a number cleaned up its contacts’ messages and history one contact at a time, so a number with many contacts could take minutes to delete. It now does the same cleanup in batches — about 30 times faster on 3,000 contacts, and the gap grows with more.
• Live Chat and chat threads open faster on large accounts. The inbox, the “Mine” filter, a chat thread on the phone, and the check made on every incoming message now read only what they show, instead of reading and sorting everything first.
• Words no longer run together in a few places. Some sentences on the WhatsApp pricing page, the WhatsApp Rates screen, the changelog and the broadcast docs showed two words joined with no space (“1,000replies”). Fixed.
• No more missing-font errors. Pages asked for bold versions of the quotation fonts that didn’t exist and showed “failed to load” errors in the browser console. Every weight now comes from the one font file that already contains them all.
• The mobile app’s Live Chat stays quick however far you scroll. It used to reload every page you had scrolled through every 10 seconds and on each new message. It now refreshes just the newest chats. Searches in the app, and in the Contacts directory on the web, wait until you stop typing instead of searching on every letter.

8 October 2026 — WhatsApp calls are charged per 6-second pulse

Fixed

• Call costs now use the per-pulse rate. MotherBot treated the call rate as a price per minute, so calls were counted at about a tenth of what they cost. The call rate is now a price per 6-second pulse, and both the cost shown on each call and your monthly budget count every pulse. If you entered your own call rate under Settings → Budget, it is now read as a price per pulse.
• Calls ended by your team now count towards your budget. When an agent hung up in MotherBot, the call’s cost never reached your monthly budget. It does now.
• Every place that shows a call charge says how it’s counted. The Calls page, the WhatsApp Rates screen, your budget settings, the WhatsApp pricing page, the mobile app, the help centre and the pricing guide now say calls are charged per 6-second pulse. The call log export has a new Billed Pulses column, and its cost column is now called Est. Meta Cost (INR).

8 October 2026 — Meta now charges for replies after 1,000 a month

Fixed

• Our pricing pages no longer say replies are free. The WhatsApp pricing page, its calculator, the WhatsApp Rates screen in your dashboard, the plans page, Getting Started and the help centre all said replies inside the 24-hour window cost nothing. They now show the 1,000 free replies a month on each number and the rate after that. The calculator has a line for replies and takes the free 1,000 off.
• The WhatsApp Rates screen describes how Meta charges today. It still explained the old per-conversation model. It now shows per-message rates, with Meta’s exact figures (₹0.115, not rounded to ₹0.12).
• Broadcast estimates for replies. A broadcast sent as a reply to customers whose 24-hour window is open is now estimated at the reply rate, and says that it may cost nothing if you haven’t used this month’s 1,000 free replies.
• Your budget counts replies. Meta tells us which messages it charges for, and your Budget screen and reports already follow that. Replies beyond the free 1,000 now appear there, priced at the reply rate. Live Chat replies still keep working when a budget’s hard stop is reached.

8 October 2026 — moving a WhatsApp Business app number to Cloud API

Fixed

• A number you move off the WhatsApp Business app is no longer treated as an app number. If you stopped using the WhatsApp Business app on a number and connected it again the normal way, MotherBot kept labelling it Also on WhatsApp Business app — so WhatsApp calls stayed blocked on a number that can now make them. Connecting again now updates the label to match what Meta says about the number.

New

• How to move off the WhatsApp Business app. Getting Started has a new section, Stop using the WhatsApp Business app on your number. It walks through moving a number to WhatsApp Cloud API only, without losing what’s already in MotherBot.

7 October 2026 — WhatsApp calls need a WhatsApp Cloud API number

Fixed

• Every place that offers WhatsApp calls now says which numbers they work on. The Calls page, the call settings for each number, the call buttons in Live Chat, “Call on WhatsApp” buttons in templates, chatbots, broadcasts and quick replies, the AI voice agent, Zoho calling, your plan details, pricing, the mobile app and our website used to present calling as working on every number. They now say it needs a WhatsApp Cloud API number and doesn’t work on a WhatsApp Business app number.
• You’re told before you connect. The Use my WhatsApp Business app number button now says, before you start, that WhatsApp calls won’t work on that number.
• No more calls that never ring. Calling from a WhatsApp Business app number used to start and then fail with an unclear error from Meta. It now stops straight away and says why. The AI voice agent, chatbot call steps and Zoho calling do the same, and those numbers are greyed out where you pick a number to call from.
• Calls can’t be switched on where they can’t work. In a WhatsApp Business app number’s settings, Allow Voice Calls can no longer be turned on, and the Call tab explains why. If it was already on, you can still turn it off.

7 October 2026 — new guides, and the right plan on every integration page

New

• Five new step-by-step guides on the blog. Sending order and delivery updates from WooCommerce; asking cash-on-delivery customers to confirm on WhatsApp before you ship (Shopify and WooCommerce); turning WhatsApp chats into Trello cards; sending Shiprocket shipping updates; and three ways to schedule WhatsApp messages, including birthday and renewal reminders. Each one says which plan it needs and what Meta charges.
• Ten new answers on the FAQs page. WooCommerce, Shopify, cash-on-delivery confirmation, cart reminders, Trello, Shiprocket tracking, scheduling a message, birthday reminders, whether the WhatsApp Business app is free, and what a WhatsApp Business account costs. The help assistant in your dashboard answers from them too.

Fixed

• Clearer wording about who bills you. A few blog articles said MotherBot passes Meta’s message charges on “at cost”. Meta bills those charges straight to your WhatsApp Business Account — they never pass through us, and we add nothing. The articles now say so. The note at the end of each article no longer says everything in it works on the free plan; connecting other apps needs a paid plan.
• The “thank you” after a cash-on-delivery tap now shows in your chats. When a Shopify or WooCommerce customer tapped Confirm order or Cancel order, the reply we sent them didn’t appear in Live Chat or Sent History, and it was sent even to customers you had blocked. It now appears in the conversation like every other message, and blocked customers are not messaged — their order is still tagged as before.
• Blog articles only claim what we can back up. The WhatsApp automation guide promised “zero” risk of your number being banned — no provider can promise that, and spam gets any number restricted — and quoted figures with no source. Those lines are rewritten. An example case study that was not about a real customer has been removed.
• The Trello page describes what Trello really does. It now lists the six Trello chatbot steps — create, find, update and move a card, add a comment, add a checklist — and no longer says the chat transcript is attached to the card, which it isn’t.

6 October 2026 — a clearer Settings page

Improved

• Settings is easier to find your way around. Each item in the Settings menu now has a short line saying what’s in it, and the section you’re on is clearly highlighted. On a phone, the menu is a row you swipe sideways instead of a long list above the page. Each section’s heading has its icon beside it. This applies to the Settings pages for business owners, team members and partners. On your business’s Settings page, the Save button also stays at the bottom of the screen, so you don’t have to scroll back down to save.
• A new Security page. Settings → Security now opens with a security checkup that shows, at a glance, whether your password is set, whether two-step login is on and how many devices are signed in — each with a button that takes you straight to the fix. Every phone and browser signed in to your account is listed right on the page, with a Sign out button for each and Sign out all others to sign out everything except the device you’re using. Two-step login (also called two-factor authentication) explains the three steps before you turn it on, and once it’s on shows when you turned it on and how many backup codes you have left.
• Every Save button in Settings now stays on screen. Some sections kept Save at the very end of a long page and some didn’t. Now every section — including Notifications, Opt-in / Opt-out, Cart Follow-up, Conversations, Appointments, Budget, Approvals, single sign-on, the summary digest and your keyboard shortcuts — has the same Save bar at the bottom of the screen while you’re looking at it. If something needs fixing before you can save, the bar says what. The bar never covers the field you’re typing in, and stays clear of the help button in the corner.

Fixed

• Notifications settings no longer flash a wrong warning. Opening Notifications could briefly say “This connection isn’t secure” before showing the real state of your browser. It now says “Checking this browser…” for that moment instead.

5 October 2026 — keep your WhatsApp Business app, and partners managing a customer's account

New

• Use the number you already have on the WhatsApp Business app. When you connect WhatsApp, there’s now a separate button: Use my WhatsApp Business app number. Meta sends a message to the app: tap Connect, choose whether to share your chat history, and copy the code into the Facebook window. The same number then works in MotherBot while you keep using the app on your phone. Your app’s contacts and recent chats come across within minutes. You need the WhatsApp Business app (not regular WhatsApp), version 2.24.17 or newer, and you must open it at least once every 14 days to stay connected. Numbers connected this way are labelled Also on WhatsApp Business app on the WhatsApp Accounts screen.
• Moving from PickyAssist? We can bring your templates across. Our team can now read every template on your PickyAssist account and submit them to Meta on your MotherBot number in one go — including image and PDF headers, link, call and quick-reply buttons, example values and one-time-code templates. Each one is checked before it’s sent, so a template Meta would refuse is fixed first rather than losing its name. Ask support to move your templates when you switch.
• Contacts from your WhatsApp Business app. People in the app’s contact list are added to Contacts, with their names, and contacts you add or edit in the app later follow automatically. A name you already gave someone in MotherBot is kept. Removing someone from the app doesn’t delete them here. These contacts aren’t counted as agreeing to marketing messages, and you can find them in segments as Source: WhatsApp Business app contacts.

Fixed

• Partners can connect a WhatsApp number for a customer. Connecting a number while managing a customer’s account finished every step at Meta and then failed with “Module access not granted”. It now works when the customer has given the partner access to Integrations.
• Partner access now covers the screens it names. Many screens had moved since partner access was set up, so a partner was refused in Live Chat, Templates, Integrations and others even with access granted. Each area a customer turns on under Partner Access now works in full, and “Exit management” works from every page.
• A clearer message when access is missing. Instead of “Module access not granted”, a partner sees which kind of access to ask the customer for.
• Quick-reply buttons can sit alongside link and call buttons. A template with, say, a Call us button followed by two quick replies was refused before it reached Meta, though Meta allows it as long as the quick replies are kept together. It’s now accepted when templates are copied or submitted through MotherBot.
• A number disconnected in Meta now shows as Disconnected. If a number was removed from MotherBot in Meta — disconnected in the WhatsApp Business app, the app not opened for 14 days, MotherBot removed from your WhatsApp Business Account, the number deleted or moved elsewhere, or MotherBot’s access expiring — the WhatsApp Accounts screen kept showing it as Connected. It now shows Disconnected within minutes of Meta telling us, or within 30 minutes at most, says why in plain words, and has a Reconnect button. Account admins get an alert when it happens. When Meta reports the number connected again, it goes back to Connected by itself.
• Meta’s warnings about a specific number now reach it. Meta’s notices about a single number — flagged, restricted, disconnected — were matched against the number as it’s displayed, with spaces, so most of them were never applied. They now are.
• Getting a text-message code after choosing “Use my WhatsApp Business app number” no longer leaves the number unable to send. If Meta sends the code by text message, it has connected the number the ordinary way rather than through the WhatsApp Business app. MotherBot now checks with Meta which kind of connection it really is, finishes setting the number up to match, and tells you which one you got.
• The WhatsApp Business app option didn’t appear when connecting. Meta hides that option when another feature is requested at the same time, which MotherBot always did. It now has its own button. Connecting that way also no longer tries to re-register a number that’s already registered to your app, and asks Meta for the app’s contacts and past chats, which were never requested before.
• One-time-code templates sent through the API no longer fail when the code is a number. If your system sent the code as a number (22427) instead of text ("22427"), the Copy code button was left out and Meta refused the message with “Button at index 0 of type Url requires a parameter”. Both now work. Send the code as text if it can start with a zero — as a number, 012345 becomes 12345.
• Quotation settings lists your WhatsApp templates again. The template list under Quotations settings was always empty because it asked for templates in the wrong place.

4 October 2026 — moving from another provider, and clearer pricing

New

• Copy templates from another WhatsApp Business Account. Moving from another provider and your number ended up on a new account? On the Templates page, click Copy from Another Account. Pick the old account, and MotherBot lists every template on it, ticks the ones Meta allows to be copied and says why the rest can’t be. Copies keep the same name, language and wording, appear on your Templates page straight away, and the old account keeps its own. Both accounts must belong to the same Meta business.
• CallBix: your team’s phone calls, on the customer’s record. Connect CallBix under Integrations → Calling and every call your team makes, receives or misses on their own SIM numbers appears on the matching contact, with the outcome, notes, follow-up and agent. Ask someone to call a customer from the new CallBix tab in Live Chat (web and mobile app, shortcut x b), from four new chatbot blocks, or from the new CallBix workflow step. Workflows can also start on a logged call, a missed call, a saved outcome, a new recording or a scheduled follow-up — for example, WhatsApp a customer the moment their call is missed. CallBix is a separate subscription, billed by CallBix, and is included in MotherBot from the Growth plan. How to set it up.
• Your existing templates arrive as soon as you connect. When you connect a WhatsApp number, the approved templates already on its WhatsApp Business Account are brought in within a minute. You no longer have to press Sync.

Fixed

• A number with a PIN from your previous provider no longer gets stuck on “Pending”. If your old provider set a two-step verification PIN, connecting with Facebook used to fail without saying so. The number now shows Not finished connecting with the reason and an Enter PIN button. Enter the old PIN, or turn two-step verification off in WhatsApp Manager and choose a new one. If you’re setting up for the first time, MotherBot asks for the PIN straight away.
• Reconnecting a number no longer shows it twice. Connecting with Facebook again used to add a second copy of the number to the list until you refreshed. Every number on the account is now shown, once.

Changed

• Pricing now says plainly what other companies bill you for. The Pricing page, WhatsApp pricing page, FAQs, comparison pages and docs now state that three costs are never part of a MotherBot plan, and each company bills you directly: Meta for WhatsApp messages, your AI provider (OpenAI, Google Gemini, Anthropic and others) for AI usage on your own API key, and each connected app (Shopify, Zoho, Razorpay, SMS providers and the rest) for its own fees. Nothing about what you pay has changed.
• Meta’s charges are described correctly. Some pages said Meta’s charges were “passed through at cost”. Meta bills the payment method on your WhatsApp Business Account directly, and MotherBot adds no markup. A few answers also still described Meta’s old per-conversation pricing, which Meta replaced with per-message pricing in July 2025.
• Clearer about what the free plan includes. We removed lines saying every plan includes every feature. AI features and integrations come with paid plans, and the comparison on the Pricing page shows exactly what each plan includes.
• Adding an AI key now tells you who pays for it. When you connect an AI provider, MotherBot says that the provider bills you directly for every use of that key.
• MagicBricks is no longer in chatbots or Live Chat. The seven MagicBricks chatbot blocks, the MagicBricks chatbot template and the MagicBricks panel in Live Chat (web and mobile app) have been removed. Everything else stays: leads still arrive in real time, the buyer auto-reply and team alerts still go out, the “lead received” workflow trigger still fires, and you can still update a lead’s status under Integrations → MagicBricks. No chatbot was using these blocks.
• Integration pages say how you really connect. Every integration page said “One-click sign-in · No API keys”, including pixbix and Explorium, which you connect by pasting an API key. Those pages now say so.
• Property portal pages now describe what they do. The 99acres, Housing.com and NoBroker pages advertised chatbot blocks that never existed. They now list what each one actually does: real-time lead capture, an instant WhatsApp reply, a team alert and a workflow trigger.

28 September 2026 — WhatsApp calls from inside Zoho CRM

New

• Call a customer on WhatsApp without leaving Zoho. Open a contact, lead, deal or any record you send WhatsApp messages from, and there is now a Call tab next to Send and History. Press Call on WhatsApp and a small MotherBot window opens. Your browser asks to use the microphone once, and the call runs in that window with a timer, mute and hang up. When the call ends you can call again from the same window.
• You decide who can call, and from which number. Go to Integrations → Zoho CRM → Extension → Calls. Pick the WhatsApp numbers that can be used for calls. Then either let everyone who uses the extension call, or list the people who can and tick the numbers each of them may call from. A number only appears once calls are switched on for it in its WhatsApp account settings.
• A daily limit for the whole team. Calls are charged per 6-second pulse, so you can cap how many calls your team places from Zoho each day. The limit resets at midnight in your business’s time zone. 0 means no limit.
• Every call is written back to Zoho. When a call ends, a call record goes onto the exact record it was made from, with how long it lasted and who made it. You can switch this off in the same Calls section. Calls also appear on your Calls page and in the customer’s chat, like any other WhatsApp call.
• Your team sees why a call can’t be made, before they press anything. The Call tab says in plain words when a customer can’t be called and what to do about it. For example: they haven’t messaged you in the last 24 hours, they’re blocked, or today’s limit is reached.

Worth knowing

• WhatsApp’s calling rules still apply. You can only call someone who has messaged that WhatsApp number in the last 24 hours, and who allows calls from businesses in their WhatsApp privacy settings. To reach someone who hasn’t messaged recently, send them a template message asking for permission to call first.
• Keep the call window open until the call ends. Closing it hangs up the call. If your browser blocks the window, the Call tab shows a link to open it instead. You can also allow pop-ups for Zoho CRM.
• Changes apply straight away. If you switch calling off, remove someone, or take a number away from them, a call window they already have open stops starting new calls.
• Incoming calls are not in Zoho yet. They still ring on your Calls page and in the MotherBot phone app, exactly as before.

Fixed

• The 24-hour calling check now looks at the right customer. When a call was placed using only a phone number, a message from any customer on that WhatsApp number in the last day could let the call through. It now checks that the person being called is the one who messaged.
• History works in the Zoho widget even when sending is switched off. If an administrator had switched off sending to single contacts, the History tab in Zoho stopped opening too. It opens again, and so does the new Call tab.

24 September 2026 — links are allowed in template message text

Changed

• You can now put a link in the message text of a marketing template. Creating a marketing template with a web address anywhere in the message body used to be refused outright — the web builder greyed out Submit and the phone app listed it as an error, both saying links had to go in a button instead. That restriction is gone. Write the link where it reads best: in a sentence, on its own line, or on a button as before.
• Nothing else about templates changed. Buttons still work exactly as they did, and a link button still has to start with https:// or http:// and use a domain registered in your Meta Business Manager — that one is Meta’s rule and it still applies.

22 September 2026 — you can switch number protection off

New

• One switch to stop us holding your messages back. Go to Settings → Broadcast → Number Protection. Turned off, we no longer stop your sending at a daily limit, no longer start a brand new number slowly, no longer hold you to a safe sending speed, no longer pause a broadcast that is going badly, and no longer refuse to launch one. A broadcast to your whole list of several thousand goes out in full, at the speed you chose.
• Off means off everywhere. There is one switch, not one per place you send from. It covers this website, the phone app, the API, the Chrome extension, the spreadsheet add-on, Zoho, WordPress, IndiaMART and the property portals, the chat widget, your chatbots, your automations and every other connected tool — including anything you build yourself against our API.
• Turn it off from wherever you work. The switch is on the settings screen here, on the phone app, and over the API at PUT /api/v1/number-health/guard. GET /api/v1/number-health now also tells you whether protection is on, so a bulk sender of your own can pace itself accordingly.

Worth knowing before you use it

• WhatsApp’s own daily limit does not go away. Every number has a limit WhatsApp itself enforces, and it will simply refuse anything past it. Those refusals count against your number and can lower its quality rating — which means a smaller daily limit, and if it keeps happening, WhatsApp blocking the number. Our limit existed to keep you the safe side of theirs; with it off, nothing does.
• We keep watching either way. Your Number Health page, your quality rating, the seven-day figures and your email alerts all carry on exactly as before. If WhatsApp starts holding your messages back mid-broadcast we will still tell you — we just won’t stop the broadcast for you. The page shows a clear banner whenever protection is off, so nobody on your team reads a daily limit there and assumes it is being applied.
• Your billing limits, monthly spending limit, blocked contacts and anyone who replied STOP are not affected. Those are your money and your customers’ choices, and no setting on the broadcast screen touches them.
• Only the account owner can change it, and we record who turned it off and when.

22 September 2026 — extra access granted to your account now works everywhere

Fixed

• Extra allowances added to your account were ignored in several places. When support raises something for you on top of your plan — more chatbots, more webhooks, more WhatsApp Flows, an app your plan doesn’t normally include, or a feature like the Sales Pipeline — the whole product now honours it. Before, only creating the thing did. You could add a webhook and never switch it on, draft a Flow and never publish it, build a chatbot and be told at the switch that your plan doesn’t include it, and connect an app that then sat on “not connected” forever. The same applied on the phone app, which reads the same allowances. Nothing about your plan has changed — the extras you were already given simply work now.
• A plan change could switch off things you had been given. Changing plan — including upgrading — ran a tidy-up that only looked at the plan, so chatbots, published Flows, webhooks, staff accounts and connected apps that support had granted you on top of it were deactivated, unpublished or disconnected. They are now left alone, and the “what you will lose” summary you see before changing plan counts them correctly too.
• Support Desk: the “All” tab now shows all conversations. It was showing only the live ones — the same rows as “Waiting” and “Awaiting customer” — so resolved and snoozed conversations were missing and the tab could come back smaller than the tabs beside it. It now shows every conversation whatever its status. Export CSV from the “Snoozed” tab used to hand back the whole desk; it now exports what is on screen.
• Two clear buttons in search boxes. The Support Desk search box, and search on the Features, Blog and Integrations pages, drew two crosses once you typed — the browser’s own and ours. There is now one.

22 September 2026 — one-time-code templates on the phone

Fixed

• The phone app looked like it wanted a button label for one-time-code templates. Creating a one-time-code (authentication) template in the phone app showed a “Button label” heading, which read as something you still had to fill in. WhatsApp writes that label itself — “Copy code” or “Autofill”, translated into the template’s language — and it refuses any template that sends a label of its own. Nothing you typed was ever sent, and it still isn’t; the label now appears as a locked line under your delivery choice, so you can see exactly what the button will say and that there is nothing to type.

21 September 2026 — one value for everyone in an imported file

New

• Fill in a field for every contact in an import, without a column for it. When you import contacts from a spreadsheet, the mapping screen now has “Same value for every contact”. Pick a field, type the value once, and it is saved on every contact in that file — the city the list was collected in, a tag like “webinar-2026”, the language to message them in, or one of your own custom fields. You no longer have to paste the same value down a thousand rows in Excel before uploading, or import first and bulk-edit afterwards.
• Tags you set this way are added, never swapped. If your file already has a tags column, the tag you type is added alongside — nothing your file says is lost, and the same tag written twice is only saved once.
• A field comes from your file or from you, never both. Once a field has a value typed for everyone, it disappears from the column list on that screen, and a field already taken from a column can’t be given a typed value — so there is never a question of which one won. Tags are the exception, because those combine. The phone number can never be set this way: everyone needs their own.

20 September 2026 — settings that now do what they say

New

• Shiprocket now sends your customers delivery updates on WhatsApp. The “Send delivery updates” switch was on by default but no update was ever sent. From today, every order you send through Shiprocket — from the dashboard or from a chatbot — is followed until it arrives, and your customer gets one message when it is on its way, one when it is out for delivery, and one when it is delivered. A parcel sent back to you, cancelled or lost gets no message. You can edit all three messages, and use the customer’s name, order number, tracking link, courier and tracking number in them.
• Choose a template for delivery updates. Most parcels arrive days after the order, and WhatsApp only allows a typed message within 24 hours of the customer writing to you. Pick an approved template under Integrations → Shiprocket → Settings and it is used whenever a typed message is not allowed. Each order shows which updates were sent, and why any were not.
• Slack: new message alerts now work. The “New message notifications” switch and its channel were saved but nothing was ever posted. You now get a short alert in that channel when a customer messages you — one per customer per half hour, so a long chat does not flood the channel.
• MagicBricks can tell your other systems when you change a lead’s status. The “Send lead status updates” switch now works: changing a status in MotherBot sends a magicbricks.lead_status_changed event to your webhooks.

Fixed

• Zoom “Require password” was ignored. Meetings were created without a passcode however it was set. They now get one, and the link your customer receives already includes it. Meetings made by a chatbot also now use your waiting room, recording, length, timezone and message settings — before, only meetings made from Live Chat did.
• Zoom “Auto-send meeting link” now applies to chatbots that don’t set it themselves, and they use your saved link message.
• Zendesk default assignee was never used, and the default group and priority only worked in one place. Every ticket — from a workflow, a chatbot or a new contact — now goes to your chosen person, group and priority unless that step picks its own.
• HubSpot deals ignored your default pipeline and stage. Deals landed in HubSpot’s own default pipeline. They now use the ones you chose, unless the step names others.
• LeadSquared leads arrived with nobody assigned. Your “Default lead owner” is now set on every lead we create or update, so someone is told to work it.
• Canva ignored your default file type. Every export was a PNG. Your chosen PNG, JPG or PDF is now used unless a chatbot step picks its own.
• Trello: the label colour, default list and “Log board activity” switch now work. Cards we create now get your chosen label colour, a workflow step with no list uses your default list instead of failing, and switching board activity off now stops it being added to your activity feed.
• Blocked contacts’ messages were still posted to Slack. Blocking now stops that too, like everywhere else.
• Clearer MagicBricks and Shiprocket errors. When MagicBricks or Shiprocket is down or refuses a change, you are now told so in plain words, instead of a general error.
• Saving Shiprocket settings no longer resets what you didn’t change, and the parcel size, weight and message fields now have sensible limits.

Changed

• Live Chat shows team members what they can and cannot do with connected apps. Someone without “Use Integrations” still sees each app’s details for the customer, but the create and send buttons are switched off, with a short note saying which permission to ask for — on the web and in the phone app — instead of each button failing when pressed.
• “Sync tags” removed from HubSpot and LeadSquared. It never did anything — tags never reached either CRM. HubSpot has no tags field of its own and we are not allowed to create one in your account, so there was nowhere safe to write them. To send tags, choose “Tags” for one of your fields under Field mapping; the screen now says so where the switch used to be.

19 September 2026 — Reports, template copies, scheduled Zoho sends, and calls in your CRM

New

• A new Reports page under Insights. Ten reports, each downloadable as a PDF or a CSV, for any period (today, yesterday, the last 7 or 30 days, this month, last month or dates you pick), filtered by channel, WhatsApp number and where the message came from.
• Sent messages, with what each one cost. Every message you sent, with the recipient, source, template, status, delivery and read times, failure reason and cost. Each cost says whether Meta confirmed it, whether it was estimated from your rates, or whether it was free.
• Auto-retries in the sent messages report. Each retry is marked “Retry 1”, “Retry 2” and so on, and shows the ID of the original message. Originals that were retried are flagged. The totals show retries and original sends separately, with their costs.
• Auto-retry performance. Shows how many messages were retried, how many retries reached the customer when the original hadn’t, why retries stopped early (for example, the contact opted out), and what retrying cost you per message recovered.
• Budget & spend statement. Your month’s spend against your budget: how much is used and how much is left, the forecast for month-end, the split between confirmed and estimated spend, the split by channel, category and source, the alerts that fired, spend by day against an even pace, and your monthly history. Only account admins can open it.
• More reports. Cost breakdown (by template, broadcast, source, channel, number and Meta category, with cost per delivered and per read), broadcast performance (reply rate, cost per read, auto-retries and attributed revenue), template performance, delivery failures (grouped by Meta error code, with what each code means and what to do about it), channel & number summary, agent performance for Live Chat, and contact growth & opt-outs.
• Get any report by email automatically. In Reports → Scheduled emails, have any report sent daily, weekly or monthly, at a time and in a timezone you choose, to up to 20 people, with the PDF, the CSV or both attached. Each email covers the period that has just ended: yesterday, the last 7 days, or last month. You can turn off emails for periods with nothing to report, send one now, and see each email’s delivery history. Only account admins can set these up.
• All report emails in Settings → Reports. Settings → Reports now holds everything in one place: the summary digest (renamed from “Scheduled Reports”, and unchanged otherwise), every detailed report email, and quick links to open or download any report. You can create, edit, pause, send now or delete a report email from either Settings or Reports; both show the same list.
• Team members see only what they’re allowed to see. Staff with Analytics access can open and download reports, limited to their numbers, channels and (if restricted) their own contacts. They can’t set up email schedules.
• Duplicate a template. Every template card now has a Duplicate button. It opens a new template already filled in with the original’s category, language, header, body, sample values, footer and buttons, under a free name such as diwali_offer_copy. Change what you need and submit; Meta reviews the copy as a new template, and the original isn’t changed. It works for approved, pending, rejected and draft templates. Carousel and limited-time-offer templates can’t be duplicated yet.
• Schedule sends from Zoho CRM. In the Zoho CRM extension and widget, choose “Schedule” next to the send button to send to one record, a selection, or a whole module at a time you pick. The send is checked when you schedule it, so a problem (for example, a template that isn’t approved) shows up straight away. Limits, the template’s approval and the customer’s 24-hour reply window are checked again when it goes out. For “send to all”, the records are pulled from Zoho at that moment. See and cancel your scheduled sends under History → Scheduled.
• WhatsApp calls are logged in your CRM. If “Log conversations” is on for Zoho CRM, Salesforce, HubSpot or LeadSquared, every WhatsApp call is now logged on the contact or lead, alongside its messages. Each log shows whether the call was incoming or outgoing and whether it was answered, missed, unanswered, declined or failed. It also includes the duration, the time, your WhatsApp number, the team member who took or placed it, and a link to the recording and transcript in MotherBot. Zoho, Salesforce and HubSpot get a real call record, which appears in their own call lists and call reports. LeadSquared gets an activity. Each call is logged once.
• Every Zoho field as a message variable. When you map {{1}}, {{2}}… the Zoho CRM extension and widget now list every field on the lead, contact or other module, including your custom fields. You can also use the record owner’s name, email, phone, mobile and role (“Lead Owner Phone”), and your own name, email and phone as the sender. Multi-select fields read as a list, yes/no fields as Yes or No, and lookup fields by name. You don’t need to reconnect Zoho.
• Property portals can now tell your team about a new lead. In 99acres, Housing.com, NoBroker and MagicBricks, there is a new box for your team’s own WhatsApp numbers — up to 20 people. When a lead arrives, each of them gets your team message on WhatsApp. Every lead now also records what happened: whether the reply and the team alert were sent, skipped or failed, and why in plain words.
• Property portals can now reach a brand-new lead, using a template. WhatsApp only allows a typed message to somebody who has written to you in the last 24 hours — which a new portal lead has not — so your reply could never actually be delivered to them. In each portal’s Settings tab you can now choose one of your Meta-approved templates for exactly that case, and say what fills each blank in it, picking from the lead’s name, phone, email, property, budget, area, city and type. You see a live preview with an example lead before you save. Your typed message is still used whenever the customer has messaged you recently, so nothing changes for people already in conversation with you. The same applies to your team alert, for teammates who haven’t messaged your number lately.
• Set your timezone from the mobile app. Account → Organisation now has a Timezone setting, with every timezone in the world and a search box — type a city (“Lagos”), a region (“Europe”) or an offset (“+05:30”). This is the timezone every date and time in MotherBot is shown in, and the one your scheduled broadcasts and your business hours run on. Until now it could only be set on the website, so an account set up from a phone was stuck on India time.
• See who a broadcast will go to, before you send it. A broadcast that hasn’t been sent yet used to show an empty recipient list — the list was only built at the moment it started, so the one thing you’d open that screen to check couldn’t be checked. Drafts and scheduled broadcasts now list every recipient, marked queued, worked out exactly the way the send itself will work it out: only contacts who are opted in and not blocked, one row per person, and (for a typed message rather than a template) only people who have messaged you in the last 24 hours. You can search it and scroll the whole list however large it is. Because a saved audience is re-checked when the broadcast actually starts, the list can still change between now and then, and the page says so. Broadcasts whose recipients come from a connected Google Sheet, Zoho CRM or Google Contacts still build their list when they start.
• Search your conversations in the Support Desk. There is now a search box above the conversation list: type a customer’s name or their number and the list narrows to them. Part of a name is enough (“prak” finds “Prakash Rao”), capital letters don’t matter, and a number can be typed however you like — with or without the country code, spaces, brackets or dashes. Search works on whichever tab you are on and alongside your channel filter, and searches all your conversations rather than only the ones on screen. Export CSV gives you just the ones you searched for.
• Your business details are now on the mobile app too. Account → Organisation now also has Business category and Organisation type, the two details that were only on the website. Everything the website’s Settings → Organization page collects can now be seen and changed from your phone.

Fixed

• The away message was going out at all hours. If you had “Away message” switched on but your business hours switched off, it replied to every customer around the clock — including people you were actively chatting to. It now only goes out while you are closed, which is what it was always meant to do. If your business hours are off, it will not send at all, and Settings now says so next to the switch.
• “How many times to ask again” for chatbot questions did nothing. Whatever you picked — 1, 2, 3 or 5 — every question always re-asked 3 times. Your choice is now used as the default for every question, and a question with its own setting still wins.
• The chatbot fallback message was never sent. Settings promised it would go out “when the chatbot encounters an error”, and nothing ever sent it — the customer just got silence when a chat flow broke. They are now told, at most once every ten minutes, and you can see the message in the conversation. Leave the box empty if you would rather send nothing.
• Shiprocket ignored your saved parcel defaults. Your usual weight, size, payment method and pickup location were saved but not used when creating an order — it always used 10×10×10 cm, 0.5 kg and Prepaid. Your own defaults are now used, and anything you type for a particular order still wins.
• A long sample image link no longer stretches the template form sideways. When you duplicate a template, its sample image comes from Meta as a very long link with no spaces in it. That link was printed in full in the upload box, which pushed the page wider than the screen and left you scrolling sideways to reach the fields on the right. The box now shows a short file name (hover to see the full link), and the same fix is applied to the chatbot builder’s media boxes.
• “Tell my team about every new lead” never worked on the property portals. In 99acres, Housing.com, NoBroker and MagicBricks, this switch and its message box did nothing at all — there was nowhere to enter who should be told, and nothing was ever sent. Add your team’s numbers in the integration’s Settings tab and it now works. If you had this switched on, please check it: no alert has ever gone out.
• Replies to property portal leads are now recorded, and follow your rules. The automatic reply to a new 99acres, Housing.com, NoBroker or MagicBricks lead did not appear in the conversation or in your Sent messages, and it ignored your plan, your monthly budget, blocked contacts and your sending limits. It now goes through the same checks as every other message and is saved in the conversation, so you can see exactly what your customer was sent.
• The same portal lead is no longer answered twice. Portals resend a lead when they don’t get a clean answer from us. Each resend ran the automatic reply again, so a buyer could get the same message more than once. A lead is now answered only the first time it arrives.
• Property portal leads can now be picked in segments and broadcasts. These leads were saved under whatever words you typed in “Name to save these leads under”, which the segment builder could not offer as a choice — so you could not build a list of, say, all your 99acres leads. They are now saved under the portal’s name and appear in the segment builder; your own wording is kept on the contact as a field you can still use in messages.
• Importing portal leads no longer creates a second copy of the same person. The Import button read phone numbers differently from the live lead feed, so a lead that had already arrived was saved again as a separate contact and their chat history split in two. Both now read numbers the same way.
• Saving property portal settings no longer wipes what you didn’t change. Your messages are also limited to a sensible length, and your team list to 20 numbers, so one save cannot slow the integration down.
• The mobile app’s template library opened empty. Templates → Template library showed a sheet with its title and nothing under it, so the ready-made templates couldn’t be reached from a phone at all. The library now opens with its search, its filters and the full list.
• The mobile app’s WhatsApp Cart wouldn’t scroll. When a customer had sent more carts than fit on screen, the rest were cut off with no way to scroll to them — including the Push to Store button on every cart below the fold. The same was true of a customer’s Appointments (where “New booking” sits at the bottom of the list) and of a recurring broadcast’s Run History. All three now scroll.
• Deleting a chatbot said it failed, when it had actually worked. Removing a chatbot showed “Failed to delete chatbot” and left it sitting in the list — but it had already been deleted, and it disappeared the next time the page was reloaded. The natural response was to try again, on something that was already gone. Deleting now reports honestly and the chatbot leaves the list straight away. The clean-up that goes with it also works again: any customer who was part-way through that chatbot is released, so they are no longer shown as “with the bot” in Live Chat, and the chatbot’s uploaded images and files are removed from your storage instead of being left behind.
• Voice notes from LINE customers wouldn’t play. A voice message sent by a customer on LINE showed as 0 seconds long and did nothing when played. The recording was always there; it just never reached the player properly. LINE voice notes now play, and you can drag through them.
• Link buttons in Live Chat are now clickable. When a message with a link button had been sent by a chatbot, a workflow or the API, the button in the conversation showed as “Visit” and went nowhere, so you could see that a link had been sent to your customer but had no way to open it. The button now carries the wording you gave it and opens your link in a new tab, leaving the conversation where it was. Buttons inside carousel cards work the same way. Reply buttons sent the same way weren’t shown at all, and now are. This affects every channel — WhatsApp, Telegram and the website widget.
• A chat session timeout shorter than 5 minutes now works. Under Settings → Chatbot, setting the session timeout to 1, 2, 3 or 4 minutes behaved exactly like 5, because sessions were only checked every 5 minutes. They are now checked every minute, so the number you choose is the number you get.
• The mobile app’s billing address is now chosen from a list. Country, state and city were typed by hand on the phone and picked from a list on the website, so the same address could be stored two different ways — and the state is what decides the place of supply on your tax invoice. The app now offers the same lists the website does. Your GSTIN is also checked as you type it, and when it is valid the state follows it automatically, exactly as on the website.

Changed

• Meta’s charge is now saved with each WhatsApp message. From today, every message records Meta’s charging category and whether Meta charged for it, so reports can show that message’s cost as confirmed. Messages sent before today are priced from your rates and marked “Estimated”. Your monthly budget totals work as before.

18 September 2026 — chatbots and workflows can no longer loop for ever

New

• The chatbot builder warns you about a loop before it goes live. If a Yes/No or If/Else branch leads back to an earlier step and nothing in between waits for the customer (a Question, a “Wait for reply” message, an AI conversation), the bot would go round at full speed and send a message or call an API on every lap. The builder now names the steps in the loop and tells you how to fix it. A loop that only repeats on a timer (a Delay wired back into itself) gets its own warning.
• A looping chatbot stops itself, and tells you. If one step runs 10 times in a row without waiting for the customer, the conversation is ended and you get an alert that names the step. Before, the bot kept going for up to 150 steps, then left the customer parked on the same loop so their next message started it again. Steps inside a Loop step still run once for each item, as before.
• Timed loops have a limit. A Delay that keeps looping back now stops after 50 rounds in one conversation, with an alert, so “nudge them every hour” doesn’t keep going for weeks after the customer has stopped reading.
• Protection against bot-to-bot ping-pong. If a contact sets the same chatbot off more than 20 times in one minute (usually an auto-responder on their side answering every message your bot sends), the bot ignores them until the minute is up and tells you why.
• A looping workflow is reported, then switched off. A workflow run stopped by the step limit used to fail silently, and the next trigger started another run that looped the same way. You now get an email the first time, at most once every 30 minutes. After three looping runs in an hour, the workflow is switched off, and the reason appears on its card until you switch it back on.

Fixed

• The workflow builder now catches two loops it used to miss. One is a loop whose only Wait step is switched off, which is skipped when the workflow runs. The other is a loop with no wait that shares steps with one that has a wait. Both used to pass the check.
• Two “receive” steps no longer read the same message. A chatbot that asked for a location twice in a row accepted the customer’s first location for both, instead of waiting for a second one.
• Failed workflow steps are counted once. A failed step used to add two to the workflow’s failure count.
• Rate limits hold while our cache server is down. When the cache server couldn’t be reached, rate limits let every request through. Limits now keep working without it.

18 September 2026 — browser notifications for your team

Fixed

• Team members can now turn on browser notifications. Agents had no notification settings anywhere, so they could never allow notifications in their browser or choose which alerts they want. It is now under My Profile → Notifications: allow this browser, see which devices are signed up, pick your alerts, set quiet hours, and send yourself a test.
• An agent’s browser keeps getting notifications. Browsers renew their notification sign-up every so often. For admins MotherBot picked up the new one on its own; for agents it didn’t, so an agent’s notifications could stop for good. It is now picked up for everyone.
• Clicking a notification opens the right chat for agents. A new-message notification took an agent to their inbox with no chat open, and the test notification opened a missing page. Both now land where they should: the conversation, and the agent’s own notification settings.

18 September 2026 — your Facebook and Instagram ads can start a chatbot

New

• A chatbot that answers your ads, and only your ads. Build a flow and set it to start on Click-to-WhatsApp Ad. Anyone who taps the WhatsApp button on your Facebook or Instagram ad gets that flow — a proper greeting for the thing they were actually looking at, instead of whatever your general “hi” bot happens to say. Leave the ad list empty and it answers every ad; name particular ads and you can run a different flow per campaign.
• It works for customers who have messaged you before. This is the part “First Message” could never do. Somebody who bought from you in March and clicks your Diwali ad in September is a fresh lead you have paid for, and until now they fell through to your ordinary keyword bots, or to nothing at all.
• Your flow knows which ad they came from. New variables you can drop into any message or condition: the ad’s headline, its ID, whether it was a paid ad or an ordinary post, a link back to it, the date they clicked, and a plain yes/no for “did this person come from an ad”. So one flow can open with “You saw our Monsoon Sale — here’s what’s left” without you building four near-identical bots.
• Workflows can now pick the ad too. The Click-to-WhatsApp referral trigger has always fired, but it fired for every ad at once. You can now choose which ad from a list of the ones you have actually had clicks from — and tell a paid ad apart from a “Send message” button on an ordinary post. Tag the lead, assign a salesperson, push it to your CRM, per campaign.

Fixed

• An ad click is no longer stolen by your “hi” bot. Meta writes the first message for the customer — usually something like “Hi, I want to know the price” — which is exactly what your keyword bots are watching for. The ad flow is now checked first, so the lead you paid for gets the flow you built for it.
• The API reference listed trigger types that do not exist. Creating a chatbot over the API documented “welcome”, “button” and “default” as trigger types. None of the three were ever accepted. The reference now lists the real ones.

18 September 2026 — who's at their desk, and a proper inbox filter

New

• See who is actually online. Your Team list now shows who is at their desk right now, with “last seen 4 minutes ago” for anyone who isn’t. It works from the web and the phone app together, so someone answering chats on their phone shows as online to a colleague on a laptop. It is a live reading, not a guess: the app checks in while it’s open and stops the moment it isn’t, so a closed laptop or a phone with no signal shows as offline by itself — nobody can be left showing green because their browser crashed.
• “I’m not taking chats right now.” A switch beside your name, on every screen and in the phone app. On a break, on a call, or heads-down on one difficult case — turn it off and new conversations are shared out to the rest of the team instead of piling up unanswered on your screen. It stays off until you turn it back on, so coming back online doesn’t quietly put you in the queue. If everybody is away, conversations wait unassigned rather than being pushed at someone who said they were out.
• Live Chat can filter by what a conversation actually is. Resolved, Unresolved, Open, Waiting on the customer, Snoozed, Overdue, Unread, Mine, Unassigned and Bot — with a live count on each, on the web and in the phone app. Your team was already recording all of this on the Support Desk; the inbox you work in all day could only offer four filters, and one of them (“Open”) actually meant “nobody has picked this up”.

Fixed

• A snoozed conversation no longer pads your Open queue. Anything you deliberately parked until Monday is under Snoozed, and comes back into Open by itself the moment its time passes.
• A brand-new chat is never hidden. A conversation nobody has closed yet counts as open and unresolved, so a first-time enquiry can’t fall off the only screen your team watches.
• Icons no longer sit jammed against their labels. Every tab strip in the product, and every button on the sign-in, sign-up, password-reset and two-factor pages, had the icon touching the word next to it — 24 tab strips and 12 buttons. Fixed where it belongs, so it stays fixed everywhere at once.
• The dot beside a team member’s name means what you’d expect. It used to be green whenever the account wasn’t suspended, which reads as “online” and wasn’t. It now shows whether they are actually there; a suspended account still says Paused in words.

18 September 2026 — table booking for restaurants

New

• Take table reservations on WhatsApp. A guest says “table for four, Friday at 8” and it is booked — on a table that actually seats four, held for as long as a party of four really takes, and only if your kitchen has room at that hour. Turn on Table booking in Appointments → Settings. Reservations sit in the same calendar as every other booking, so reminders, approval, cancellations, the Live Chat panel, the phone app, webhooks and the export all work exactly as you already know them.
• Your floor, as it really is. Add your areas — indoor, terrace, rooftop, private room — and the tables in each, with how many they seat and the smallest party worth giving them to. The tightest table that fits is always the one taken, so a couple never occupies the six-seater you needed for the party of six.
• Turn times, by party size. A couple for 60 minutes, a four for 90, a party of eight for two hours. A 90-minute booking at 7:30 genuinely blocks that table until 9:00, so an 8 o’clock enquiry is correctly refused instead of being double-sold.
• Pacing, so the kitchen can cope. Cap how many guests may be seated in any quarter of an hour. Without it every table booked “for 8” walks in at 8:00 sharp. When pacing is what stops a booking, the guest is told the kitchen is full at that time and offered another — not simply told there are no tables.
• A waiting list that actually calls people back. When a date is full a guest joins the queue and is told roughly how long the wait is. As soon as a table frees up, the party at the front is offered it — and the table is held for them for a few minutes, so two guests are never sent to the same one. An offer nobody accepts expires on its own and passes to the next party.
• Deposits for big parties. Charge per guest above a party size you choose. With hold until paid on, the booking waits as unconfirmed until the money arrives, so an unpaid party of twelve never quietly holds your best table on a Saturday night.
• Pre-orders from your own menu. Ask larger parties to choose their food ahead, up to a cut-off before they arrive, and the kitchen gets a prep list instead of eight decisions at once.
• The menu in chat is your product list. There is no second menu to keep up to date. Each product gains a dining panel: course, diet (pure veg, Jain, vegan, no onion / no garlic, halal), spice level, allergens, signature dish, how many it serves, and the days and hours it is served — so a breakfast dish is never offered at dinner, and a guest who says “pure veg” only sees food they can eat. Turn In stock off and the dish is 86’d for today: it disappears from chat immediately.
• A floor plan your staff run the shift from. Tonight’s service by area and table: who is booked, who has arrived, what is free and for how long. Seat a party in one tap, move them to another table, or take a walk-in and seat them in the same action. The phone app has a Floor screen of its own, which refreshes itself while you walk the room. In Live Chat, a guest’s occasion, dietary needs, allergy note and pre-order sit beside the conversation — so “happy anniversary, and the Jain thali is noted” needs no other screen.
• A ready-made restaurant chatbot. Start from the Restaurant — Table Booking template: it asks party size, area, day, time and occasion, shows the menu, finds an existing booking, and offers the waiting list when the floor is full. Nothing in it needs a key or a URL configured. There is a Book a Table workflow step too, plus new webhooks and triggers for when a guest joins the waiting list, is offered a table, or is seated.

Improved

• A proper month calendar. The Appointments calendar had only Day and Week. There is now a full Month view, so you can see the shape of the next few weeks at a glance.
• The calendar and the list keep themselves up to date. Both refresh on their own, so a booking taken by a chatbot or a colleague appears while you are looking at the screen instead of after you reload it.
• Step-by-step guides for Zendesk, Zapier, Calendly, Excel and Google Sheets. Each of these integrations now has a full written guide — what it does, how to connect it, flows worth building, and the WhatsApp 24-hour rule that decides what you can send and when. Every integration page links to its guide, and the guides are on the blog.
• Forty new answers in the help centre — and eight that were wrong. The FAQs now cover Zapier, Excel and Google Sheets, Calendly, template rejections, quality ratings, opt-ins and STOP replies, the channels beyond WhatsApp, and what everything costs. Eight existing answers were out of date and have been corrected: WhatsApp’s charges are per message now rather than per 24-hour conversation, the 1,000 free service conversations a month no longer exist, a new number starts at 250 customers a day rather than 1,000, the green tick is a blue checkmark with published criteria, and the plan is free forever — it was described as free for 14 days.
• The support bot can find every answer again. Nine published FAQs had no search vector, and the assistant skips any FAQ without one — so those answers could never be given, however exactly a customer asked. Every FAQ is now indexed, an answer is re-indexed whenever it is edited, and a missing vector now falls back to keyword matching instead of vanishing.
• Answers for the four things that go wrong on WhatsApp. New guides on why a template was rejected (and why an approved one can still be paused), the green tick — now a blue checkmark, free, and not for sale — a quality rating that has dropped and how messaging limits really work, and the Business app versus the API, including the 256-contact broadcast rule that catches everyone out. Each one is checked against Meta’s own documentation.
• Add a customer while you are booking. The new-appointment form used to need the customer to exist already, which meant abandoning a half-filled booking to go and create them. You can now create the customer from inside the form and carry on — on the web and in the phone app.

Fixed

• Only published WhatsApp Flows are offered. Every place you can send a Flow — Live Chat, chatbots, workflows, broadcasts, and the phone app — listed drafts alongside published ones. Choosing a draft looked fine and then sent nothing: a Flow that is not published cannot open, and WhatsApp Flows fail silently, so the customer simply received a message that did nothing. Drafts no longer appear in those lists.
• Ready-made chatbot templates that quietly did nothing. Fields across fourteen templates were saved under names the chatbot engine does not read, so parts of them had never worked: every Dynamic List menu (Today’s Menu, the product catalogue, course lists, fee lists, event lists, branch pickers) sent its list with no introduction text and no custom button label, and the item the customer tapped was stored in the wrong place — so the next message showed them {{menu_item}} instead of the dish they picked. The FAQ template never read its Google Sheet. The AI templates never saved the AI’s answer, so the step that decides whether to fetch a human had nothing to read.
• The Gmail and Google Calendar templates now actually run. Both named a step that does not exist, so the bot walked straight past it: the Gmail template sent no email and the Calendar template created no event, with nothing to show for it in either place. Creating an event also asks what time it finishes rather than how long it lasts, which is what Google Calendar needs.
• The builder no longer warns about variables that are fine. Opening a booking bot showed a wall of warnings claiming its confirmation message used the booking reference “before this step has had a chance to fill it in” — backwards, since the confirmation is sent because the booking succeeded. The variable holding whatever a customer picked from a live list was also not recognised at all, so it was missing from the { } menu and reported as never filled in. Every template we ship now opens with a clean panel, which is the point of the panel.
• Three dead ends in the all-in-one appointment bot. Looking up a booking, cancelling one, and listing your history each had no “it didn’t work” path, so a customer whose cancellation could not go through (usually because it was too close to the appointment) got no reply at all and was left waiting. Each now answers: a first-time customer is shown the menu normally, a cancellation that cannot be done automatically says so and passes the chat to your team, and a customer with no history is told so and offered a booking.
• The WhatsApp pricing guide described the old billing model. Our public WhatsApp pricing page still explained Meta’s per-conversation charges and a monthly allowance of 1,000 free service conversations — both retired. Meta charges per delivered template message since 1 July 2025, and replies to a customer inside the 24-hour window are free, as are utility templates sent while it is open. The page, its rate table and the cost calculator now work that way, so the estimate you get matches the bill Meta actually sends.

17 September 2026 — one name for each thing, in plainer words

Changed

• The sales pipeline is called “Sales Pipeline” everywhere. It was “Pipeline” in the menu, “Sales Pipeline” on the page, “Deals” in Live Chat and “Deals & Pipeline” in webhooks, Zapier and the API reference — four names for one screen. Everything now says Sales Pipeline, and one card on the board is a deal. The chatbot steps are now Sales Pipeline: Create deal, Find deal, Move stage and Update deal.
• The two website features have names you can tell apart. Chat Widget and Website Chat did different jobs under near-identical names. The button that sends visitors to WhatsApp is now WhatsApp Button; the chat box whose replies land in your inbox stays Website Chat.
• Menu names say what is inside. Grow is now Links & Coupons. WA Pricing is WhatsApp Rates. Comment to DM is Comment Replies. Consent is Consent & Compliance, matching the page it opens. Staff is Team, which is what the phone app already called it.
• The app and the browser agree. Where the phone app and the web used different words for the same screen — Call Logs vs Calls, Staff vs Team, Pipeline vs Sales Pipeline — both now use the same one.
• Screen descriptions are written for the person running the business. “Saved, rule-based audiences” is now “Groups of customers that update themselves”; “Ground the AI Reply chatbot step in your own content” is now “Give the AI your own documents, so it answers from your information instead of guessing”; “Blast template messages” is now “Send one message to many customers at once”. Owners and team members see the same description of the same screen.

17 September 2026 — Appointments, rebuilt

New

• An Appointments screen of its own. Under Customers → Appointments: today’s list, a day or week calendar, and every booking with its full history. Book for a customer yourself, move one, confirm, mark completed or no-show, and export what you’re looking at. Bookings taken by a chatbot, by your team, in the phone app and through the API all land in the same calendar.
• Services. Give each thing you offer its own length, gap afterwards, price, seats and location — a 20-minute consultation, a 90-minute treatment, a class of 20. Customers pick one in chat. If you don’t add any, every booking is one appointment of your default length, exactly as before.
• Staff, rooms and other resources. A booking can be with a doctor, a stylist, a trainer, a room, a table or a bay — each with its own calendar, hours and time off, so two of them can both take 10:00 and a customer can choose who they see (or let you pick whoever is free).
• Reminders. Up to five per booking — a day before, an hour before — sent on the channel the customer booked on. Reminders are re-timed automatically when a booking moves. Outside WhatsApp’s 24-hour window they need an approved template, which you choose in Settings; without one the booking records that the reminder couldn’t be sent, and why, instead of failing silently.
• Customers can manage their own bookings in chat. New chatbot steps move a booking, cancel it, confirm they’ll attend, look up their next one, or list their history — and you decide how close to the appointment they may still change it, and how many times.
• Appointments inside Live Chat. An agent answering “can I come Thursday instead?” can see, book, move and cancel that customer’s appointments from the chat, without leaving the conversation. The phone app has the same panel, plus its own Appointments screen.
• Closed days, special hours and approval. Mark holidays, open different hours on a one-off date, cap how many bookings a day you’ll take, require your approval before a booking is confirmed (the slot is still held while it waits), and close out past bookings automatically as completed or no-show.
• A full REST API and webhooks. Book, move, cancel, read availability, and list services and staff from your own software. Send an Idempotency-Key and a retry can never book twice. New webhooks and workflow triggers fire when a booking is made, confirmed, moved, cancelled, completed, missed, or reminded.

Fixed

• Double bookings. Free times were worked out by matching the clock exactly, so a 60-minute booking at 10:00 left 10:30 open and both could be sold. Two chatbots kept separate counts and could each sell the same seat. Two customers tapping the last slot at the same moment both got it. Availability is now worked out from real overlapping time, including your gaps, on one calendar per business — and the seat is re-checked at the moment of saving, so only one of them can win.
• “Bookings per slot” now saves. The setting existed and the booking code read it, but saving Settings silently dropped it — so an OPD set to take five patients per slot kept taking one.
• A chatbot can no longer book a time you’re closed. Whatever date and time a customer typed was booked: a Sunday, 3am, or a date that had already passed. Every booking is now checked against your hours, closed days, notice period and booking window.
• WhatsApp Flows no longer offer slots that are taken. The slot list in a Flow was never excluding existing bookings at all, so a form could hand out a time somebody already had.
• The all-in-one appointment chatbot template works. Its “reschedule”, “cancel” and “my history” options relied on steps that were never built, so it always answered “you don’t have an appointment” and could only ever book. It now finds, moves, cancels and lists bookings — and rescheduling keeps the customer’s existing reference instead of issuing a new one.
• Your confirmation message is used. The message written in Settings was saved and never sent; chatbots always sent their own wording.
• Times follow your timezone. Reminders and the calendar are worked out in your organisation’s own timezone rather than India’s.
• Booking references are easier to read out. Eight characters, with no 0/O or 1/I to confuse over the phone.

Changed

• Appointment length comes from the service or your settings. The per-step length on the chatbot’s Book Appointment step is no longer used, so one booking can’t be a different length from the slot it occupies.
• Your chatbots share one calendar. Each chatbot used to keep its own count of what was booked. A customer’s booking is now found and managed by any of your bots, and capacity is counted once for the business.

17 September 2026 — every plan limit can now be raised for a single account

Fixed

• Custom limits cover everything your plan meters. If our team agreed to give your account more than your plan includes, some limits couldn’t be raised: Workflows, Workflow Runs / Month, Drip Sequences, Knowledge Bases, WhatsApp Groups, Quotations / Month and Quotation Designs. All of them can be raised now, and a raised limit takes effect straight away.
• Chatbot steps can be unlocked one at a time. Our team can now unlock a single chatbot step for your account: the deal steps, the quotation steps, Add Note, Number Health Check and Ad Conversion. Before, only four steps could be unlocked this way. You don’t have to upgrade your whole plan.

17 September 2026 — one email, one login

Security

• A team invite can no longer reuse someone else’s inbox. Each email address could belong to only one account, but other spellings of the same inbox were accepted. For example, johndoe@gmail.com for an existing john.doe@gmail.com, or owner+team@company.com for owner@company.com. Inviting a team member with such an address created a second login, and its temporary password was sent to the existing person’s inbox. Every place that creates an account or changes its email now refuses another spelling of an address already in use, by any kind of user in any workspace. That covers team invites (web and app), sign-up, Google and SAML sign-in, partner-created customers, and Super Admin’s organisation, user, partner and admin screens. Gmail ignores dots and treats googlemail.com as gmail.com, so both count; a +tag is ignored for every provider.
• Emails are stored trimmed. Some forms kept leading or trailing spaces, so " owner@company.com" counted as a different address.
• Duplicates are blocked by the database too. A second request arriving at the same moment is refused rather than creating a duplicate.
• Partner applications. Approving an application whose email already belongs to a customer, team member or platform admin account is now refused with a clear reason, instead of being marked approved without creating a partner.
• Google sign-in. Signing in with Google using a dotted spelling of an address that already has an account shows a message asking you to use that account’s exact email, instead of creating a new workspace.

17 September 2026 — usage bars for unlimited limits

Improved

• Unlimited limits have a bar too. On Billing, limits marked Unlimited now show a light striped bar, so every row lines up and the page no longer looks unfinished. The stripes mean there’s no ceiling; they aren’t a fill level. Super Admin’s organisation details use the same bar and now say “Unlimited” instead of “∞”.
• Small usage is visible. Any usage above zero now shows at least a sliver, so 4,672 of 10,00,000 monthly messages no longer looks like zero.

17 September 2026 — WhatsApp Flows with several screens, end to end

Fixed

• Changing one screen’s ID no longer changes another screen. After you switched screens, the Screen ID box could still show the previous screen’s ID. Clicking out of it then gave that ID to the screen you were on, and a later rename changed both screens. The box now always shows the open screen’s ID and renames only that screen. Press Enter to apply, or Escape to undo your typing. Flows that already have two screens with the same ID are repaired when opened: the second screen is renamed after its title (for example DELIVERY_DETAILS), and the button that pointed at it opens it again.
• Earlier screens’ answers now arrive with the finished form. In a flow without a server connection, the final button sent back only the last screen’s answers, so a product chosen on screen one never reached you. The final button now also sends every answer from the screens before it. Photos and files still arrive only from the screen they were uploaded on, as WhatsApp requires.
• “No data model is defined in the next screen” is fixed. When a button passes answers to the next screen, that screen now declares them automatically, as WhatsApp requires.
• Flows connected to your server move through screens in order. When no rule chooses where to go, submitting a screen now opens the next screen in the list. Before, it ended the whole flow after the first screen. A conditional “Go to” rule that doesn’t match no longer sends the customer to its screen anyway. The Logic tab shows where the customer goes by default.
• Reorder screens. New arrows next to Delete move a screen earlier or later. The first screen is where the flow opens.
• Deleting a screen is safer. Its data settings and rules are deleted with it. Buttons, navigation rows and rules on other screens that opened it are kept, and the builder asks you to choose a new screen for each, instead of leaving them pointing at a screen that no longer exists.
• Navigation list rows count as links between screens. A screen opened only from a navigation row was reported as “cannot be reached”, and a flow connected to your server could reject that step.
• “Ask your server” error screens work. The screen chosen for when the call fails now follows renames. WhatsApp is also told the flow can go there; before, sending the customer there could fail without any message.
• Rules that point at a missing screen are flagged. This includes a “Go to a screen” rule with no screen chosen, and a rule that sends the customer to its own screen.
• “Required property ‘helper-text’ is missing” is fixed. WhatsApp needs helper text on a text field that has a format pattern. The field’s error message is now used as its helper text when you haven’t written one.

17 September 2026 — test a workflow as a real customer

Fixed

• Testing a workflow no longer stops at “Send a chat message”. Test always ran without a customer. Any step that acts on the customer the workflow runs for stopped with “This step writes to the customer the run is about, and this run doesn’t have one.” That included sending a message, tagging and adding a note, even on triggers like “A message was received” that always have a customer when live.
• Pick a test customer. Test now opens a window where you choose a customer from your contacts. When a step needs one, the window says which step, and the test won’t start without a customer. Nothing is sent to that customer and nothing about them changes. Your pick is remembered for the next test of the same workflow in the same browser.
• Trigger values are filled in during a test. A test now uses sample data for the trigger, with the test customer’s own ID, name and number, so {{trigger.…}} values have something in them. Choose Edit what the trigger carried to try your own values, such as a different message text.

17 September 2026 — multi-screen WhatsApp Flows save again

Fixed

• A second screen no longer breaks the flow. New screens were named SCREEN_2, SCREEN_3 and so on, and WhatsApp refused them: “Property ‘id’ should only consist of alphabets and underscores”. New screens are now named SCREEN_TWO, SCREEN_THREE, etc. When you rename a screen, numbers become words (PICK_SLOT_2 becomes PICK_SLOT_TWO) and any other character becomes an underscore.
• “Success” stays on final screens only. A new screen was added as the final screen, so turning Final screen off to add another after it left its Counts as a success setting behind. WhatsApp then refused the flow: “Property ‘success’ can only be specified on a terminal screen”. Turning Final screen off now clears the setting too.
• Existing flows are repaired automatically. When you open or publish a flow with a numbered screen id, the screen is renamed. Its buttons, navigation rows, If and Switch branches, references to its answers, data rules and logic rules are all updated to match. Leftover success settings are removed. The editor shows what was renamed; save to keep it. A chatbot step set to open that exact screen will open the flow’s first screen until you pick the screen again.
• Renaming a screen updates everything that points to it. Before, buttons inside a Switch case and navigation-list rows kept the old name and stopped working.

16 September 2026 — pictures on form options, and which files an upload accepts

New

• A picture on each option. Checkboxes, radio buttons and dropdowns can show a picture beside each choice — a product, a room, a plan. Upload it per option in the builder; it’s resized for you and shown in the preview. WhatsApp allows this on those three components from Flow JSON 5.0.
• More per option. Each option also takes a description, small print, a colour, and a Selectable switch to show a choice greyed out, such as “Sold out”. Alt text can be added for pictures so screen readers describe them.
• A picture on each navigation row. Navigation list rows take a leading image (up to 100 KB each, WhatsApp’s limit) with its own description.
• Document uploads: tick the file types. Allowed file types is now a list to tick, grouped into Documents, Images, Video and Archives, instead of typing type names by hand. Video is supported: MP4 and MPEG. WhatsApp doesn’t accept QuickTime (.mov) or WebM for uploads, though an iPhone converts .mov to MP4 when attaching, so recording a video works.

Fixed

• Option pictures now count towards the screen’s picture limit. WhatsApp allows about 1 MB of pictures per screen. Option pictures were not being counted, so a screen could be refused at publish with nothing in the builder warning first.

16 September 2026 — clearer pixbix errors in workflows

Fixed

• A variable typed without its double braces is caught. Typing trigger.files.photo.url instead of {{trigger.files.photo.url}} used to send those exact words, and a pixbix design would fail with only “Some field values are not valid.” The workflow builder now flags it before the workflow can run and shows the correct form.
• “Insert” goes where you’re typing. In Fill in the fields and other name/value lists, inserting a variable puts it in the row you’re editing, at the cursor, braces included. It used to be added to the end of the last row.
• pixbix failures say which field and why. Before rendering, the pixbix step checks your design’s fields. A required field left empty, or an image field that isn’t given a web link, now stops the step with the field’s name and what it received, before any credits are used. Anything else pixbix refuses is shown with its reason for each field.
• Photos from forms are ready for other services. Phone photos can be 10 MB or more, or in HEIC format. {{trigger.files.photo.url}} now gives an upright JPEG at most 2560 px on its longest side (usually around 1 MB). {{trigger.files.photo.originalUrl}} gives the file exactly as it was uploaded.

16 September 2026 — WhatsApp Flows: every component, fully editable

New

• Show a server value in any text. A heading, subheading, body, caption, rich text, label or description can now show a data field. Click Show a value from data instead under the text, then pick an existing field or type a new name. The field is added to the screen with your current text as its example, so the preview still reads naturally. The value then comes from the Data tab or from an “Ask your server” rule.
• If, Switch and form groups can hold components. Use Add inside on a container to fill an If’s “then” and “otherwise” branches, a Switch’s cases or a form group. You can add Switch cases by the value they match, and reorder or remove anything inside. Only components WhatsApp allows in each container are offered.
• Navigation lists have a proper row editor. Each row has a title, description, small print, end label (such as a price), one badge per list, up to three tags, and its own screen to open.

Fixed

• If components with a condition couldn’t be published. A normal condition such as ${form.age} > 18 was flagged as “mixes text with a variable”. Conditions, and the Visible and Enabled settings, are no longer checked as text.
• Navigation list rows were in a shape WhatsApp rejects. Existing rows are converted when the flow is opened or published.
• Date pickers cut error messages at 30 characters. WhatsApp allows 80.

16 September 2026 — use photos and documents from a form in a workflow

New

• Uploaded photos and documents become real files. When a customer submits a WhatsApp form with a photo or document upload, the file is saved to your account right away and gets a permanent link. Before, a workflow only received WhatsApp’s internal reference, which nothing could open and which expires.
• Put a customer’s photo straight into a pixbix design. In a workflow started by A form was submitted, use {{trigger.files.photo.url}} (with your upload field’s name) in a pixbix image field, a media message or anywhere a link is needed. .urls lists every file, .fileName gives the original name, and .count says how many were uploaded.
• The variable list shows your form’s own fields. Once you choose which form starts the workflow, the variable list shows that form’s answers by name, with upload fields offered as file links.

Fixed

• Flows with a blank example on a data field couldn’t be published. WhatsApp rejected them with “Required property ‘__example__’ is missing”, because a blank example was dropped before the flow was sent. Blank examples are now sent as they are.
• Tokens typed into a custom header are now encrypted. An API key pasted into a header such as Authorization or X-API-Key is now encrypted and hidden in the builder, just like the Login fields.

16 September 2026 — WhatsApp Flows open again

Fixed

• Flows showed “Something went wrong. Try again later” when opened. This affected flows without a server connection, sent from a chatbot, Live Chat or a workflow. WhatsApp accepted the message, but the form failed as soon as the customer opened it. Two things were wrong. The message didn’t say which screen to open first. It also sent every contact field and chatbot variable as data for that screen, which WhatsApp rejects when the screen doesn’t declare those fields. Flows now open at the chosen screen (or the first one), with only the data that screen declares. Flow messages already sent will still show the error; send them again.

16 September 2026 — WhatsApp Flows: call your API and show its answer

New

• Variables work in every part of an API call. The Ask your server rule and Your own API data source take variables in the address, query parameters, headers, login and body. Every box has a Variable button listing what you can use: answers on this screen and earlier screens, the screen’s data, values from other rules, saved API answers, contact fields and details of the form itself. Each comes with a description, and clicking one inserts it where your cursor is. A How to use variables guide shows examples you can copy, such as {{order.items.0.name}} and fallbacks like {{coupon|NONE}}.
• Show your server’s answer on the screen. In Use the answer, pick a field from the API response and choose where it goes. A value goes into a screen data field that a Text component shows with ${data.order_status}. A list can fill a dropdown, radio buttons, checkboxes or chips; you say which keys hold each option’s id and label. The editor can create the screen data field for you. Clicking a data field in a text box inserts it the way WhatsApp expects, including when you mix it with your own text.
• Save an answer for later rules. Save the response under a name, such as order. Later rules and conditions on this screen and every screen after it can then use {{order.status}}, {{order_status}} (the HTTP code) and {{order_ok}}.
• Decide what happens when the call fails. Carry on, show the customer an error message (which can include variables), or send them to another screen.
• Test a request before publishing. Enter sample values for its variables and send it. You see the exact request that went out (logins hidden) and the response. Click any field in the response to show it on the screen.
• More request options. Query parameters, custom headers, form, multipart and raw bodies, how long to wait, one retry, which status codes count as success, and following redirects.

Fixed

• Answers with quotes broke API calls. A customer answer containing a quote or a line break made the JSON body invalid, so the call failed. Values are now escaped inside quotes. Written without quotes, numbers stay numbers and lists become lists. Values placed in an address are URL-encoded.
• API tokens and passwords in Flows are now encrypted. The builder said they were stored encrypted, but they were saved as plain text and shown to anyone who could open the flow. They’re now encrypted when saved, never sent back to the builder, and hidden in test results. Existing ones are encrypted the next time the flow is saved.
• Checkboxes limited to one choice were rejected by WhatsApp. Setting Max selected to 1 on checkboxes made WhatsApp reject the flow. The builder now catches this before publishing and offers Switch to radio buttons (the right component for a single choice) or Remove the limit. It also catches a minimum above the number of options, and pre-selected values that aren’t among the options.

16 September 2026 — photo and document uploads in WhatsApp Flows

Fixed

• Flows with a photo upload were rejected by WhatsApp. Adding a Photo upload and switching on Required made WhatsApp refuse the flow with “Property ‘required’ is not allowed in ‘PhotoPicker’”. Photo and document uploads don’t have that setting; they’re made mandatory with a minimum count. The builder now shows Min photos / Min files instead: set it to 1 or more to require an upload. A flow already saved with Required switched on is converted to a minimum of 1 automatically.
• Upload mistakes are caught before publishing. These used to fail only when WhatsApp checked the flow, or while a customer was filling it in. The builder now flags them first:
  • a minimum higher than the maximum
  • more than 30 files, or a per-file size over 25 MB
  • a document type WhatsApp doesn’t accept
  • uploads passed to the next screen
  • uploads combined with other text
  • a completed flow that could carry more than the 10 files WhatsApp delivers

16 September 2026 — agreed pricing, one-time charges and partner statements

New

• Pricing agreed with you appears on your Billing page. If we’ve agreed a custom price or monthly add-ons with you, Billing shows a Your agreed pricing section: each part of the price and the total you pay. That price is also what the plan card and checkout charge. If you already have a subscription, the new price applies from your next renewal, never partway through a period you’ve paid for.
• One-time charges are billed with your renewal. Agreed one-off items, such as setup or training, are listed under Added to your next renewal. They’re charged together with your next subscription payment and appear on that payment’s invoice.
• Partners earn on every payment from their clients. Commission used to be earned only on a client’s first payment. It’s now also earned on every renewal and on one-time charges billed with it. A client can have its own agreed commission rate, which is used for that client instead of the partner’s standard rate.
• A statement PDF for every payout. Partners can download a statement for each payout from Commission History. It shows the commission, GST, TDS deducted, net amount paid, bank reference and invoice number. The tax invoice you sent us for a payout can be attached to it.

Changed

• Commission is calculated before GST. Commission on a client’s payment used to include the 18% GST in that payment. GST is tax, not revenue, so commission is now a share of the amount before GST. For the same rate, each commission is slightly lower than before.

Fixed

• Renewal reminders were sent to free plans. An account on the free plan could receive “your plan renews soon” and “your plan has expired” emails, even though a free plan never renews or expires. Reminders now go only to paid plans. They also stop for an account that has chosen to move to the free plan at the end of its current period.
• Partner earnings could show long decimals. Pending and paid earnings could show as ₹1,349.6999999. They are now always rounded to the paisa.

16 September 2026 — partners can manage their customers again

Fixed

• “Manage” logged partners out instead of opening the customer’s account. A partner who clicked Manage on a customer was sent back to the sign-in page within a moment. The regular account check that runs in the background treated the partner as signed in to their own portal, not the customer’s dashboard. Manage now opens the customer’s dashboard and stays there until you choose Exit Management. If you were caught by this, sign in once more and Manage will work.

15 September 2026 — partner payouts with GST, TDS and proof

New

• Partners can add their GST and tax details. In Partner Settings you can now enter whether you’re GST-registered, your GSTIN, legal name, PAN and registered address. The GSTIN is checked as you type, so a typo is caught before you save.
• GST-registered partners are paid GST on top of commission. Each payout adds 18% GST, shown as CGST + SGST or as IGST depending on your state. Every payout records the number of the tax invoice you raised for it.
• TDS is deducted and shown on every payout. Once your commission for the financial year crosses the Section 194H threshold, TDS is deducted from the commission (never from the GST). If no PAN is on record, the higher rate applies, so add your PAN to avoid it.
• Commission can be paid straight to your bank or UPI. Payouts can now be sent online by IMPS, NEFT, RTGS or UPI. A payout shows Processing until the bank confirms it, then Paid with the bank reference (UTR). If the bank rejects or returns it, the commission becomes unpaid again and is paid in a later payout.
• Payments made outside the app come with proof. A bank transfer, UPI payment, cheque or cash payment is recorded with its date, reference and a receipt or screenshot.
• A full payout statement in your portal. Commission History now lists every payout: commission, GST, TDS, net amount, bank reference, your invoice number and proof of payment. The payout email includes the same breakdown.

Fixed

• A commission can no longer be paid twice. Marking commissions as paid used to be a single click with no record of the money actually sent. If two payouts were made at the same moment, both could include the same commission. Each commission can now belong to only one payout.

15 September 2026 — moving a business between partners

Changed

• A business can be moved to a different partner, or taken off partners altogether. Any business can be put under any partner, not only those that signed up through that partner’s link. When a business moves, its previous partner loses access straight away, including any session they had open inside the account. Commissions from then on go to the new partner; commissions already earned stay with the old one.

Fixed

• A business moved to a new partner stayed visible to the old one. Moving a business added it to the new partner but never took it away from the old one, so both partners could open its data and sign in to manage it. It is now removed from every other partner at the same moment.

15 September 2026 — WhatsApp number transfers no longer get stuck on “already in progress”

Fixed

• A transfer request you had just sent didn’t show up. After you sent a request, the Account transfers list kept showing what it loaded when you opened the window, so the request looked like it hadn’t gone through. Trying again was refused with “A transfer for this account is already in progress”. The list now updates as soon as you send or cancel a request.
• “Already in progress” now says which request is in the way. The transfer window now shows the waiting request as soon as it opens: who it went to, when you sent it and when it expires. A Cancel that request button sits right there, so you can clear it and send a new one without hunting for it.
• A transfer interrupted mid-move could lock the number forever. If an accepted transfer was cut off before it finished, nothing moved but the number stayed marked as “being transferred”, so no new transfer could ever start. After 30 minutes a stuck transfer is now marked Failed (no data was moved) and the number is free to transfer again.
• The “Review” link in transfer emails opened the wrong page. It went to Integrations, which no longer shows WhatsApp numbers, so the receiving admin couldn’t find the request. It now opens Channels with the transfer list in view, and links in emails you have already received are forwarded there too.

10 September 2026 — ratings from a workflow, and Viber taps

New

• A workflow can ask for a satisfaction rating. A customer rating could start a workflow and nothing could ask for one, so “when a conversation is resolved, ask them to rate it” had no way to do the asking. The new Ask for a rating step sends the question and records their reply against that conversation.
• Viber keyboard taps now start workflows. Viber sends a button tap as an ordinary text message, so a tap and somebody typing the same words looked identical. The payload attached to the button is now read, so a tap is recognised as one.

Fixed

• Closing a conversation from a workflow never asked for a rating. If you had satisfaction ratings switched on, they went out when a person closed a conversation and never when a workflow did — the setting looked like it was working and quietly produced no ratings from automations at all. Resolving from a workflow now asks, and you can turn that off per step for a conversation closed for tidiness rather than answered. A rating that cannot be sent no longer makes the step report a failure: the conversation really was resolved.

10 September 2026 — quotations in workflows, and LINE button taps stop vanishing

New

• A workflow can now send a quotation. Twelve different quotation events could start a workflow — created, sent, viewed, accepted, rejected, expired and the rest — and not one step could act on a quotation. So “when a deal reaches Proposal, send them the quotation” could not be built. The new Send a quotation step sends an existing one on WhatsApp, and hands back the link the customer opens so a later step can use it.

Fixed

• Quotation triggers offered no variables at all. Every other trigger showed you what it carries; the twelve quotation ones showed nothing, so unless you already knew that the total was called trigger.quotation.grandTotal you could not use it. They now list the number, status, totals, dates, terms, the customer and the public link, like every other trigger.
• LINE button taps were being thrown away. When a customer tapped a button on a LINE message, the whole event was discarded before anything ran — no message in Live Chat, no unread badge, no trigger, nothing. The customer answered and the business never found out. Those taps now arrive like any other reply and can start a workflow.

10 September 2026 — button taps start workflows on Telegram, Messenger and Instagram too

Fixed

• Telegram inline-keyboard taps now set workflows off. Tapping a button under a Telegram message raised nothing the reply trigger could see. Telegram also tells us exactly which message the buttons belonged to, so the reply is matched to it precisely rather than guessed from timing.
• Messenger and Instagram button taps too. A tap on a call-to-action, an Ice Breaker or a button we sent arrives as a “postback” on these channels, and none of them reached the trigger. Meta gives no reference to the original message here, so the match is worked out from the most recent unanswered message — the workflow can tell the difference, as the reply says whether the match was exact or inferred.
• “Message received” carries the tap on these channels too. If you already have a workflow on that trigger, it now sees which button was pressed instead of just that something arrived.

10 September 2026 — the workflow builder now shows you what data you have

New

• “What this step can use” — a plain-language list on every step. Open it and you see everything available at that point in the workflow: the customer’s details, what set the workflow off, and what earlier steps produced. Each row shows what it is called, an example of what will actually be in it, and the code to paste. The example is the important part — seeing Diwali offer beside a row explains it better than any name can.
• It only lists what will really have a value. Steps that run after this one, and steps on a branch this one never reaches, are left out — picking one of those was never going to work, and it fails silently rather than telling you. If something you expected is missing, connect that step ahead of this one and it appears.
• Pick a button from a list instead of typing its ID. The “which button” filter now suggests the quick-reply buttons from your own approved templates, and tells you which template each one is on. You can still type your own, for buttons on interactive messages that are not part of a template.

Fixed

• The button filter asked for something that does not exist. It asked for “the button’s ID, not the words on it”. For a quick-reply button on a template there is no ID — WhatsApp sends back the words on the button, and they are the only handle there is. The filter now matches either the ID or the wording, and ignores capitalisation and stray spaces, so it works whichever kind of message the reply came from.
• A filter containing only a space matched nothing at all. An empty filter has always meant “any”, but a filter holding a space or a stray tab was treated as a real value that nothing could ever equal — so the workflow was switched on, correct, and silently never ran. You cannot see the difference between the two in a text box. Blank now means “any” however it got that way.

10 September 2026 — a button tap can now start a workflow

New

• A trigger for replies: Customer replied to a message. It fires when someone taps a quick-reply button, chooses a row from a list message, submits a form, or answers a broadcast or template. Previously the only trigger that covered any of this was “message received”, which told you a message had arrived and nothing else — not which button was pressed, and not what it was an answer to.
• It tells you what they were answering. The reply carries the broadcast, the template and the sequence the original message came from, so a workflow can behave differently for Tuesday’s offer than for last month’s. It works even when the reply is a tap on a message we sent days ago.
• Narrow it with dropdowns, not IDs. Choose the broadcast from a list of your broadcasts, and choose how they replied — tapped a button, chose from a list, typed something, submitted a form. Filtering happens before the workflow starts, so a business running four broadcasts is not paying for four runs on every reply.
• Match on the button’s ID, not its wording. You can narrow to one particular button. It matches the button’s ID rather than the words on it, so rewording a button later does not quietly break the workflow.
• “Message received” now says which button too. If you already have a workflow on that trigger, the button’s ID and wording are now in what it receives.

Fixed

• The variables a step offers are the ones that will actually have a value. The insert-a-variable list showed results from every step in the workflow, including steps that run after the one you were setting up, and steps on a branch it never meets. Picking one of those was never going to work: it fills in as blank when the workflow runs, with no error anywhere — so a message goes out with an empty space where the tracking number should have been. The list now shows only steps that genuinely run before this one, and updates as you rewire the workflow.

10 September 2026 — segments are re-checked, and re-counted, the moment you use them

Fixed

• Workflows can see segment members again. The three paths above asked the right question and threw the answer away. Every one of them now resolves the segment properly, and a segment whose rules have stopped working says so by name instead of quietly matching nobody.
• CRM-backed segments are re-read before you send. A rule built on a Zoho, HubSpot, Salesforce or LeadSquared field matched against a copy of that data which refreshed once an hour. So a broadcast could go out against a Lead Status you had already changed hours earlier: the rule was current and the data behind it was not. Now the CRM is re-read immediately before a broadcast, a recurring broadcast, a scheduled workflow, or a segment you add to a sequence by hand reaches anyone.
• The count on the Segments page follows every use. Each time a segment is used to send, its size is re-counted from the same query that picked the recipients and written back. The number you see is the send that just happened, not whatever a background sweep last managed.
• A broken segment stops the send instead of widening it. If a rule no longer makes sense — a custom field was deleted, a linked campaign is gone — the send is refused and names the segment. It can never fall back to “everyone”, which is the expensive direction to get wrong.

10 September 2026 — WhatsApp carts appear as they arrive, and push to WooCommerce by SKU

Fixed

• A cart now appears the moment it is sent. The WhatsApp Cart panel loaded once, when you opened the conversation, and never refreshed — so the cart bubble arrived in the chat while the panel next to it stayed empty, and the only way to see the cart was to switch conversations and come back. It now updates live, in the conversation you are already looking at.
• Push to Store now matches your products by SKU. A cart line was only ever sent to your store as a numeric product ID. If your catalogue is keyed on SKUs — which is how every CSV feed and most catalogue plugins build one — WooCommerce got a line naming no product at all and refused the whole order. Both stores now match on SKU first and product ID second, including product variations.
• A rejected push names the SKU. Instead of repeating WooCommerce’s “Product ID or SKU is required”, it now tells you which SKU your store did not recognise, so you know which product to look at. The cart stays where it is and can be pushed again once it is fixed.
• Your store prices the order. Matched lines are sent as a reference to the real product, so tax, coupons and stock behave exactly as they do for any other order. The total the customer saw in WhatsApp is written into the order note, so if your catalogue price has drifted you can see both numbers side by side rather than neither.

10 September 2026 — cart reminders stopped sending, and told you nothing about why

Fixed

• A new cart from the same customer now replaces the old one. Every cart used to start its own set of reminders, so a shopper who corrected their cart — ordinary behaviour — was chased about the one they had already replaced, by two ladders at once. The earlier cart’s reminders now stop the moment the new cart arrives, and say so.
• The daily cap now leaves room for more than one cart. The default is 10. If you set a cap lower than the number of reminders you have switched on, the settings screen now refuses it and says which reminder could never send — rather than saving a ladder that silently stops halfway, on every cart, forever.
• You are told why a reminder did not go out, in words. “Daily cap reached (9/9 messages in the last 24h)” instead of daily_cap. This applies to every refusal — opted out, blocked, no number connected, monthly limit reached — wherever a store or catalogue automation reports one.

10 September 2026 — cart reminders now follow the timings you just saved

Fixed

• Saving your reminder timings now moves the carts already waiting. Shorten a delay and every cart still being chased is re-timed to it on the spot — anything that is now overdue goes out within the minute. Lengthen one and the reminder waits, instead of firing at the old, earlier time.
• Switching Cart Follow-up off stops the carts mid-ladder. Previously each one carried on until its next reminder came due before noticing. The cart’s follow-up line in Live Chat now says it stopped, and why, as soon as you save.
• A reminder your new timings push past the 24-hour window is ended honestly. A catalogue reminder is a normal reply, which WhatsApp only allows within 24 hours of the customer’s own message — so one scheduled beyond that can never send. Instead of sitting there marked as scheduled forever, it now stops and tells you that is what happened.

10 September 2026 — a message that fails now gets retried, from wherever you sent it

Fixed

• A rejected message is now a message you can see. Sent History shows it with WhatsApp’s own reason and code, whether it came from the Chrome extension, the Sheets or Excel add-on, the Zoho widgets, the WordPress plugin, Live Chat, a chatbot, a broadcast, a sequence, a coupon, a quotation, a store automation, Zapier, Calendly, HubSpot, Salesforce or the API. Your message.failed webhook now fires for these too.
• Auto Retry now sees them, so “Failed” works as it reads. This is the fix behind the report: with Failed ticked, a template WhatsApp rejected on the way out is now retried on your schedule, up to your attempt limit, from every one of those places.
• HubSpot and Salesforce messages are now recorded at all. A WhatsApp message triggered from either used to leave no trace anywhere in MotherBot — not in Sent History, not on your webhooks, and never eligible for a retry. Both now log the send and the failure.
• A large send from an extension or the API is no longer filed as a broadcast. Above 250 recipients these are handled by the same engine that runs broadcasts, and they were being labelled as one. If you had set Auto Retry to “Individual sends” only, none of them were retried; if you had set it to “Broadcast messages” only, all of them were. They now carry the tool they were sent from.
• Retries no longer repeat a rejection WhatsApp will repeat. Some refusals are about the message itself — the number cannot receive WhatsApp, the template is paused, the values do not match the template. Retrying those cost you the message and cost your number a little quality rating, three times over, to arrive exactly where it started. The chain now stops on the first one and tells you why.

Changed

• Retries respect your plan and your budget. A retry is a billable message, and the one send that runs while nobody is watching was the only one not checking. It now stops at your monthly message limit and at a monthly spend budget set to block — and resumes on its own when either resets, as long as the message is still inside its retry window.
• A failed send is never counted as a sent one. It does not move the contact’s last-message time, does not add to their sent count, and does not consume your monthly message allowance.

10 September 2026 — your quotation design is now exactly what the PDF is

Fixed

• Everything you set is now on the PDF. Watermark, background image, corner style, header style, table style, page size, your accent and your secondary colour. The secondary colour had never been used anywhere at all, even on screen — the eight ready-made looks each set one and it was quietly ignored.
• Fonts are now real, and the same everywhere. The four typefaces ship with the product instead of relying on fonts installed on whoever’s computer opened it, so a quotation looks identical on your Mac, on your customer’s phone and in the PDF. The rupee sign, and every other currency symbol, now renders properly in all four — and where a typeface genuinely has no rupee sign at all (the monospace one does not), the document borrows that single character rather than printing something else in its place.
• Long quotations paginate properly. The column headings repeat at the top of every page, a line item is never split across a page break, and the totals, payment details and signature blocks stay whole. Every page carries your business name, the quotation number, and “Page 2 of 5”.
• Line items can be moved down, not just up. Reordering only worked in one direction, behind an icon that looked like a drag handle — so moving a line down meant moving every other line up past it. There is now an up and a down control, and a button to duplicate a line rather than retyping six fields to change one.
• The builder no longer closes one section when you open another. Checking the customer’s address while pricing a line used to collapse the items list and lose your place.

New

• Emailing a quotation now attaches the PDF. The email carried a link and nothing else, so a customer who wanted a copy to file or forward to their accounts team had to open the link and download it themselves. The document is now attached as well. The link is still the live version — it is what they accept from.
• A setup checklist on the Quotations screen. Quotations worked from the moment they were switched on, which meant a first quotation could go out with no bank details, no terms and no logo, and nothing said so. The list now shows what is still missing and why a customer would care. It never blocks anything, it can be dismissed, and it disappears once the essentials are in.
• Printing from your browser now produces the same document. Ctrl+P on a quotation gives properly formatted pages rather than a screenshot of the screen.
• Amounts in words are no longer italic. A small change, made so the line reads identically on screen and on paper.

10 September 2026 — every segment filter now explains itself

Fixed

• Some CRM filters still were not refreshed. Only rules on a CRM field triggered a re-read. Rules on CRM last synced, CRM, CRM record and CRM record type did not — so “find contacts whose CRM data has gone stale”, a filter whose entire purpose is to catch old data, was itself answered from old data. All of them now refresh.
• The explanation was a tooltip. Hovering is not something you can do on a phone, and it was easy to miss on a desktop. Every filter that is not simply live now carries a proper panel you can read without hunting for it.

New

• Each filter says where its data actually lives. Pick a CRM field and it names the exact system and record type behind it — “Zoho CRM · Leads” — rather than “your CRM”. If you have two CRMs connected and the same field mapped on both, you can finally tell the two entries apart.
• And how it stays current, in plain terms. Whether it is held here or in someone else’s system, when it last changed, and what to do if it looks stale. Where a refresh is not possible the panel says so and says why, instead of offering a button that does nothing.
• Enrichment filters now say they cost credits to update. Company size, industry, seniority and the rest come from an enrichment you paid for, and they never change on their own. That is now stated on the filter, along with the fact that re-enriching is a per-contact decision — MotherBot will not spend your credits behind a segment preview.
• The count shows when your CRM was last read. An actual date and time, not just “just now” — so a count that refreshed nothing still answers “how old is what I am looking at?”.
• The same explanations are in the mobile app. One set of wording, written once on the server, so the two never drift apart.

9 September 2026 — CRM segments now count against your CRM as it is right now

Fixed

• A segment with a CRM rule now re-reads your CRM before counting. Open or edit a segment that filters on something like Zoho’s Lead Status and the values are fetched again first, so the count reflects what your CRM holds now rather than what it held this morning.
• The count now tells you where it came from. Underneath the number it says whether your CRM was just read, and how many contacts were read — so a figure you are about to build a broadcast on is one you can trust. There is a Refresh from CRM link to force a fresh read, and the refresh button on the Segments list does the same.
• Contacts your rule can never reach are now named. Fields are kept per record type, so mapping Lead Status on Leads left every contact linked to your CRM’s Contacts record type holding none of it — the segment was valid, the field was mapped, and the count was quietly low with nothing explaining it. The builder now says exactly how many contacts are affected and which record type they are in.
• The field list is searchable. The picker can now run to a couple of hundred entries once your CRM fields, broadcasts and coupons are in it, so it has a search box — matching the field’s name and its underlying key, so looking up Lead_Status or cf1 finds it too. The mobile app already had this.
• Every filter now says when its data updates. Pick a field and the builder tells you what kind of data sits behind it — always current, read from your CRM, from the last enrichment, or recalculated daily. A tag and a Zoho picklist look identical in a dropdown and are not the same thing, and the count now says which kinds it was built from before you act on it.
• Map a field across all your record types at once. The Segment fields screen now lists the other record types your contacts are actually linked to, with how many are in each, and offers to keep the same fields on those too. Only fields that exist on a record type are copied; anything else is reported rather than silently dropped.

9 September 2026 — segments: pick your values instead of typing them

Fixed

• CRM fields now offer the CRM’s own values. Filtering on something like Zoho’s Lead Status meant typing the value in, and it is matched exactly — so “contacted” against Zoho’s “Contacted” found nobody and said nothing. Those choices are now read from your CRM and offered as a dropdown, for Zoho, Salesforce, HubSpot and LeadSquared alike, and for every mapped field rather than only the ones set up on the Segments tab. If your CRM adds a value tomorrow you can still type it.
• Telegram, LINE and Viber contacts could not be segmented at all. The channel list offered seven of the ten channels the platform supports. Contacts on the other three were visible in Live Chat and then unreachable in any audience, count or broadcast. All ten are now listed.
• Three ways a contact can be added were missing. Contacts that arrived from Calendly, IndiaMART or a workflow could not be filtered on. The list also showed raw values like wordpress; every choice is now named properly.
• “Country is India” missed contacts stored as “IN”. Country has been filled in by imports, forms, webhooks and the API over the years, and they did not agree. Picking a country now matches every way it has been written down, so one rule finds the whole audience instead of part of it.
• “Is any of” could only ever hold one value in the mobile app. Choosing several tags or several channels at once was offered and then quietly impossible.
• A mistyped value is now refused when you save. For lists that cannot change — channel, how they were added, language, consent — a value that is not on the list is rejected with the valid choices shown, instead of being saved as a rule that can never match.

New

• Your own tags and cities are offered as choices. Both were free text against values only the database knew the spelling of, so a tag typed with different capitalisation matched nobody. You can still type one you have not started using yet.
• Your custom fields are in the list by name. Filtering on the field you call “GST number” meant knowing it is stored as cf1 and typing that. Named fields now appear in the picker like any other.
• Business data from enrichment. Where a contact has been enriched you can now segment on job title, seniority, company, industry, company size and revenue — so “decision makers at mid-sized fintech companies” is an audience you can build.
• Timing and window rules. Filter on the hour of day somebody usually replies in, when your chatbot last spoke to them, and when the 72-hour free reply window from an ad click runs out.
• More ways to find people. First and last name, the country worked out from their phone number, other channels the same person is reachable on, the ad headline they came from, and which Zoho record type they are linked to.

9 September 2026 — a workflow can no longer set itself off in a loop

Fixed

• “When a message is delivered” + “send a message” was an endless loop. The reply you sent got its own delivery receipt back from WhatsApp a minute later, which set the same workflow off again, which sent another message, and so on with nothing to stop it. The same applied to the sent, read and failed triggers. This is now blocked: a workflow is never set off by the receipt for a message it sent itself.
• Two workflows bouncing off each other are stopped too. Each one could honestly say it was not the workflow that sent the message, so they would have kept going indefinitely. A send-and-receipt chain is now counted across the whole round trip and ends after five hops.
• The builder says so while you are building it. A workflow that starts on a message status and sends a message now shows a note explaining that its own replies will not set it off again — so a workflow that correctly does nothing does not look broken.
• Workflow sends are labelled in Sent History. They were recorded as if an agent had typed them in Live Chat, so there was no way to tell what an automation had sent. They now show as Workflow.

9 September 2026 — workflow triggers were not starting anything

Fixed

• Every “when this happens” trigger was silently refused. An internal check misread every switched-on workflow as switched off, so the run was declined the instant it was created. Nothing was reported — no error, no failed run, nothing in the run history — because from the system’s side the workflow had simply chosen not to run. All of the roughly sixty product events were affected, and so was every trigger from a connected app such as Shopify, WooCommerce, Zendesk or Trello.
• What was not affected. Workflows you run by hand, workflows on a schedule, and workflows started by a web address or the API all worked correctly throughout — they take a different path. If your automations seemed to work sometimes, that is why.
• A workflow that matches but does not start now says so. Ordinary reasons stay quiet — “this customer is already in this workflow”, a monthly limit — but anything unexpected is now recorded, so a silence like this one cannot happen again unnoticed.

9 September 2026 — fewer boxes to type ids into

Improved

• Coupons, workflows, chatbots and knowledge bases are chosen from a list. Each of these was a text box wanting an id. A typo saved without complaint and then failed when the workflow ran — or worse, matched something else. “Answer from a knowledge base” had never been able to offer anything at all.
• AI models are picked from a list, grouped by provider. Previously a free-text box: a model name that had been retired saved cleanly and failed against the provider mid-run.
• pixbix designs are chosen by picture. The design field showed your published designs with their thumbnails instead of asking for an id copied from the pixbix dashboard, and the one you pick is previewed so you can see you have the right one. Only designs you can actually render are offered — a design from the shared library has to be copied into your own workspace first, and one that is not renderable used to list happily and then fail.
• Picking a design fills in its fields for you. You no longer have to know a design’s field names by heart. Choosing one adds each of its fields ready for you to fill in — and this matters more than it sounds: a mistyped field name was never rejected, so pixbix rendered the design with that field left blank and you got a real, correct-looking image with the customer’s name missing. Anything you have already filled in is kept.

9 September 2026 — workflows: send to any number, from any of your numbers

New

• Every send step now asks who to send it to. The customer the workflow is about is still the default and still what you want almost every time. But you can now type a phone number, build one from the trigger — {{trigger.customer.phone}} — look somebody up by phone, email or ID, write to the agent the conversation is assigned to, or always write to one person on your team. Numbers you have never messaged before are added to your address book automatically so the message has a thread to live in; you can switch that off per step.
• Choose which of your WhatsApp numbers it goes out from. “Send from” is now a dropdown of your connected numbers instead of a box wanting an id you had to find somewhere else and paste. Leave it on Automatic and it keeps using the number the customer already talks to. If your access covers only some of your numbers, you are only offered those.
• Reach a typed number on any channel. When you type a number in, you pick the channel it belongs to — WhatsApp, SMS, RCS, Telegram, Instagram and the rest — and the message joins that person’s thread there.
• Automations that message somebody with no customer attached. Because a step can now carry its own recipient, “every morning at nine, text the ops number yesterday’s total” is something you can build. Before, a workflow started by a schedule or by your own software was refused any step that sends a message.
• Advanced settings on every step. A new collapsed Advanced section: run this step only when your rules hold (and quietly move on when they don’t), try again if it fails, give a slow app longer to answer, and a note to yourself about why the step is there.
• Retries, for the times somebody else is briefly down. Choose up to five extra attempts and how long to wait — doubling each time, or the same gap. The workflow waits between tries rather than holding on to anything, so a retry still happens after a restart, and the run history shows each attempt and how many there were.

Fixed

• Workflows that started but never did anything. A workflow run is created the moment its trigger fires and then handed to the machine that carries out the steps. If that handover was missed — a brief blip between the two — nothing ever picked the run up again, and nothing anywhere reported a problem. The run sat in the history with a start time and no steps, forever. Depending on when the blip happened this could affect one run or every run, which is why it could look like none of your triggers were working at all. Runs that have been sitting unstarted are now found and carried out within a couple of minutes, and if the handover still cannot be made they are run directly instead.
• A workflow can no longer be stopped by one step being slow. Steps that call another app get a time limit you can raise, rather than one fixed limit for everything.

8 September 2026 — transferring a number no longer fails on a shared name

Fixed

• A transfer failed if both businesses had used the same name or id. Two shops that had each made a trackable link called “Shop counter poster” were enough to stop the whole handover, and the transfer showed only Failed. The same thing could happen with a sequence, a workflow, a catalogue id, an order reference or a day of analytics. Every kind of record is now checked before anything moves, so a clash is resolved instead of ending the transfer.
• Nothing is deleted to make room. Where the clash is a name you chose, the arriving one is renamed — a link or sequence called “Welcome” arrives as “Welcome (2)”, and if that is taken too, the next free number. Where it is an id that cannot be renamed — a catalogue id, an order, a day’s figures — the record stays with the business sending the number, and the receiving account keeps its own.
• The transfer now tells you what it resolved. A completed transfer lists it by collection: how many contacts were merged into ones you already had, what was renamed, and what stayed behind. Previously only contacts, products and sequences were reported.
• Double bookings were not actually being blocked. The rule that stops the same customer being booked into the same slot with the same chatbot twice had never been active, because of how it was set up. It is now.
• New-account alerts now record whether they were sent. The notification that tells our team a new account has been created could fail without leaving any trace, so nobody knew to look. Both sign-up methods — email and Google — now share one notification that writes down its outcome either way. Nothing changes for your account.

7 September 2026 — connect an AI assistant to your account

New

• One URL, your existing API key. Nothing to download and nothing to keep updated. Add https://motherbot.io/api/mcp as a connector in your assistant, paste an API key, and it can see your contacts, conversations, templates, analytics, orders, coupons, deals and number health. Setup guides for each app — Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, JetBrains and ChatGPT.
• It can build automations for you. Describe what you want — “when someone messages us for the first time outside business hours, reply that we’ll get back to them in the morning and tag them as an after-hours lead” — and the assistant builds the chatbot or workflow. It reads the real list of triggers, steps and node types first, so what it builds is something MotherBot can actually run rather than a plausible-looking guess.
• Your API key decides what it can touch. An assistant is only offered the tools your key’s permissions allow, and any other call is refused. A read-only key gives you an assistant that can answer anything and change nothing — a good place to start.
• Two new key permissions. Workflows and Chatbots, each split into read and build, so you can let an assistant design automations without giving it your contact list.
• Workflows and chatbots on the REST API. The same abilities are available to your own code: list, read, create, edit and activate both, plus two endpoints that describe every trigger, step and node type available on your plan. See the API reference.

Fixed

• Some assistants refused to load the tool list. Clients on the newest MCP revision validate every response against the specification, and ours was missing the two caching fields it requires — so the connection failed with a type error instead of listing any tools. Both are now sent. The tool list is marked private, because it is filtered by your API key’s permissions and must never be cached and served to somebody else’s key.
• Editing a workflow or chatbot ignored the WhatsApp number. Both accepted a number when you created them and silently dropped it when you changed it, so moving an automation to a different number did nothing. It now applies.

7 September 2026 — a monthly spend budget, and sign-off before a big send

New

• A monthly budget for third-party charges. Under Settings → Budget, set what you are willing to spend in a calendar month with Meta and your SMS, RCS and email providers. The screen shows what you have spent so far, what you are on course to spend by month end, and where it went — by channel, and by what sent it, so a broadcast is separated from a chatbot and from the Chrome extension. It counts WhatsApp messages by Meta’s own category, WhatsApp call minutes, SMS per segment (a 200-character Hindi message is three segments, not one), RCS and email. It does not include your MotherBot subscription — that is Billing.
• Alerts you choose, to people you choose. Add as many thresholds as you like. An actual alert emails when you have spent that much; a forecast alert emails when your current daily rate is heading there by month end — the one that arrives early enough to do something about. Each threshold can have its own recipients on top of a list that gets everything, so finance can be told at 100% and you at 50%. Raising your budget mid-month re-arms the alerts at the new figure rather than silencing them.
• Optionally, stop sending. Choose what happens at the top: nothing, send big broadcasts for approval instead, or stop. You can set the stop above 100% if you want alerts at your real budget and a hard line only once you are over it.
• Your own prices. What Meta charges depends on your country, and what your SMS gateway charges depends on your contract. Enter your real rates on the same screen and every estimate in the product — including the cost shown before you launch a broadcast — uses them. Leave a field blank to use the platform rate, which is shown next to it.
• Approval before a bulk send. Under Settings → Approvals, hold any send going to more than a number of people you set, or costing more than an amount you set, until an approver says yes. Nothing is sent while it waits. It covers every way a send can start: the dashboard, the mobile app, the API, the Chrome extension, the Google Sheets and Excel add-ins, the Zoho CRM widget and the WordPress plugin.
• A queue, on both web and phone. A new Approvals screen lists what is waiting, who asked, how many people it reaches, what it will cost, which template it uses, a few of the recipients and why it was held. Approve or reject with a note. Approvers are emailed and get a push notification — an approval that waits for somebody to reach a desk is one that misses its send window. Whoever asked is emailed the answer.
• Approving is instant, whatever the size. Pressing Approve records the decision and returns straight away — it never waits for the send. The release then runs in the background, a few thousand recipients at a time, so a hundred-thousand-person broadcast behaves exactly like a five-hundred-person one from where you are standing. If it is interrupted part way it resumes from where it stopped rather than starting again, and nobody is messaged twice.
• A permission for it. Approve Broadcasts & Bulk Sends is a new staff permission, and it is deliberately not implied by being able to manage broadcasts — the person who starts a send is who the queue exists to review. Until you grant it, you are the only approver.

Fixed

• SMS broadcasts are now priced by segment. Cost estimates counted one message as one charge. Gateways bill per 160-character segment, and per 70 once a single emoji, curly quote or non-Latin character appears — so a long message in Hindi was being under-costed by two thirds.
• A broadcast could count one person as both delivered and failed. A report could read Total 1, Sent 0, Delivered 1, Failed 1, with the same recipient showing as delivered in the message log and “Failed” in red beside them. WhatsApp sometimes sends a failure notice and a delivery receipt for the same message seconds apart, and MotherBot was adding to a counter for each one it received instead of moving the recipient between them. A delivery receipt now takes a recipient back out of Failed, a failure notice arriving after a confirmed delivery is ignored — the handset already has the message — and the stale error text is cleared. Every figure on a broadcast report now adds up to the audience it was sent to.
• A late failure notice could mark a delivered message as failed in the chat. The same out-of-order receipts could leave a message the customer had already received sitting in the conversation and in Sent History with a red error against it. Message status now only ever moves forward.
• Phone Health was measuring your numbers against a figure several times larger than your real traffic. WhatsApp re-sends delivery receipts — whenever we are slow to acknowledge one, and routinely besides — and every re-send was being counted as another message. One number reported 105 delivery verdicts in a week it had 21, and days on which it sent nothing at all showed eight deliveries. Every percentage on the Phone Health page was divided by that inflated total: the delivery rate, the opt-out rate, the “Meta is withholding X% of your messages” warning and the health score itself. Because the inflation lands on whichever receipt WhatsApp happens to repeat, the figures could be too low as easily as too high — the withheld-messages warning was reading well under the truth. A message is now counted once, when it reaches a state, so these are real percentages of what you actually sent.

7 September 2026 — link shortening with Bitly, and a channel search that finds channels

New

• Bitly, with automatic link detection. Connect your Bitly account under Integrations, switch on Detect and shorten links automatically, and the web addresses in your messages are replaced with your own short links as they go out. It covers Live Chat replies, broadcasts, drips, chatbot flows, workflows, scheduled messages and sends through the API — on WhatsApp, SMS, RCS, email, Telegram, LINE, Viber, Messenger, Instagram and website chat. Media captions and button links are included, not just the message body. On SMS this is money: a text is billed in 160-character segments and a long link can be half of one.
• You decide where it applies. Each surface and each channel has its own switch, so you can shorten broadcast links and leave Live Chat alone, or shorten on SMS and not on WhatsApp. There are rules for the rest: a minimum length (so a link shorter than the bit.ly replacing it is left as written), a cap on how many links one message may use, a list of websites to shorten and a list never to touch, and optional UTM tags added to the destination before shortening — with {{source}} filling in the surface that sent it, so broadcasts and chatbots report separately from one setting.
• The same link is never shortened twice. A broadcast to forty thousand people carries one link, so it costs one link on your Bitly plan — not forty thousand — and all of its clicks are counted together instead of split across forty thousand identical entries. The Links tab shows what has been shortened, how many messages carried each one, and their click counts pulled back from Bitly.
• Your branded domain, if you have one. Pick the Bitly group and short domain to mint on. Only domains that group actually owns are offered.
• Shorten a link by hand. There is a Try it box on the integration, and the same action is available from the mobile app, whether or not automatic shortening is switched on.

Fixed

• Searching the platform channel list now searches the channels. The search box on the platform-wide channel view only ever looked at the customer’s name, slug and billing email — so typing a phone number, a WABA id, a bot handle, a Page name, a sender id or a gateway name matched nothing and the screen answered “no connections” for a number that was plainly connected. That is the one lookup the screen exists for. It now searches the connection’s own details as well, phone numbers match however they are typed (+91 98123 45678 finds 919812345678), and searching a customer still lists every one of their connections — including the quiet one you were probably looking for. The counts above the table now describe what you searched for rather than the whole platform.

5 September 2026 — pixbix renders that stop getting lost, and a platform-wide channel view

Fixed

• “It failed here, and it is finished in my pixbix dashboard.” When pixbix was busy it would accept the job and hand back a ticket instead of the file — and MotherBot treated that ticket as a failure, for a picture or video that finished seconds later and was charged for either way. It now waits for the job and gives you the file. This affected images, videos and page captures alike, in Live Chat, chatbots and the mobile app.
• A slow render is no longer charged for twice. If a render took long enough that the connection timed out, MotherBot used to start the whole thing again — sometimes three times, each one billed to your pixbix credits, and you were still shown an error at the end. It now goes back for the render that is already running instead of paying for another one.
• A video render that outlives the wait can be picked back up. A long encode used to leave you with nothing but an error, even though the video was on its way. The job now stays on screen with a Check again button, on the web and in the mobile app, so you collect the file you have already paid for rather than rendering it a second time.
• You are told what actually went wrong. A failed render used to say only “the video render failed”. It now shows pixbix’s own reason — and if MotherBot loses contact with the render while it is working, it says that, instead of leaving a progress bar sitting at 0% for four minutes.
• Saved capture presets work in Live Chat again. Picking one of your saved pixbix presets and pressing Render answered “Enter a URL first” and never took the picture — even though a preset carrying its own web address is the whole point of saving one. It now captures the preset’s page. Two things behind it are fixed as well: the preset picker no longer stays hidden until you switch between Web page and Template and back, and the panel no longer quietly overrules the recipe you picked. A preset saved as “full page, PDF, on a phone” used to come back as a desktop PNG of the first screen; the format, device and full-page controls now show what the preset will actually do, and changing one is a deliberate override.
• A saved preset now outranks your pixbix defaults everywhere, not just in Live Chat. The same thing happened in chatbot capture steps, workflow capture steps and the mobile app: your workspace defaults under Integrations → pixbix, and the step’s own untouched format and device boxes, were quietly written over the top of the preset you had named. Naming a preset is now taken as the instruction — anything you set alongside it still wins, so picking PDF next to a preset still gives you a PDF. If a capture in a chatbot or workflow has been coming out in the wrong size or format since you started using presets, this is why, and it needs no change from you.
• Video posters are back. The still frame pixbix produces for every video was being dropped, so a chat that cannot autoplay had nothing to show. It now travels with the video.
• Deleting an organization now removes everything. A handful of records tied to individual team members rather than to the business itself were being left behind. They are removed with everything else, and the check that keeps this honest now also catches the reverse mistake — a new kind of record that quietly never gets cleaned up.
• Deleted broadcasts no longer leave broken links behind. Messages and part-finished forms kept pointing at a broadcast that had been deleted. The message history is unchanged and still names the broadcast it came from; only the dead link is cleared. The same was true of IndiaMART enquiries pointing at a deleted customer.

New

• pixbix in Workflows. A workflow can now render one of your pixbix designs — image or video — or photograph a web page, and hand the result to any step that follows: send it to the customer, post it to Slack, put it in an API call. Both actions are under pixbix in the step picker, and only appear once pixbix is connected and included in your plan.

Workflows

• Big trigger data no longer arrives empty. When something started a workflow with a lot of data attached — a large order, a detailed record from your own software — every {{trigger…}} value came out blank, and the workflow carried on and sent the message with the gaps in it. Nothing looked wrong in the run history. The important fields are now kept, the bulky ones are dropped, and the run history names exactly which ones were dropped.
• Automations stop while an account is unpaid — properly. A workflow could not start on an account with a billing problem, but one already part-way through a wait carried on when the wait ended, and kept messaging customers. Those runs are now paused instead, and resume on their own once the account is settled — they are not thrown away.
• A tightened check on where a workflow can send a web request. Steps that call a web address are blocked from reaching private and internal addresses. That check could previously be sidestepped by a website that redirected the call elsewhere; it no longer can be.
• AI steps now count towards your AI usage. Anything a workflow’s AI step spent was missing from Settings → AI usage, so the figure there was lower than what you were actually using. It is counted from now on — expect the number to look higher than before, because it is now complete.
• AI steps check your plan when they run, not only when you build them. The builder already hid AI steps from plans that do not include them, but a workflow built while you had AI carried on using it afterwards. It now stops with a clear message instead, so the step tells you why rather than quietly costing you.
• Long-abandoned runs are cleared in steady batches. Housekeeping that closes runs which waited far too long could try to do the whole backlog at once and slow everything else down. It now works through them a batch at a time.
• One more kind of API key is now hidden in run history. If a Call-a-web-address step authenticates by putting a key in the web address itself, that key was written into the run history in full — where your team, an export or a support thread could see it. It is masked now, like the other three kinds always were. If you used that option, treat the key as exposed and rotate it.

Website

• “How it works” now shows you, instead of telling you. The page opens with a real WhatsApp conversation playing itself out — a customer asks about stock, the AI answers, they pick a slot, they pay, the order is created — captioned two or three words at a time so it makes sense to somebody who has never used a chatbot. The sixty-second trace underneath walks itself through all eleven steps, one line at a time, and you can tap any step to hold it. The three setup steps and the ten channels are drawn now rather than described. About two thirds of the reading was removed.
• The Integrations page leads with what it actually does. Instead of a paragraph explaining that data moves both ways, the page shows it: orders, contacts, payments and replies crossing a wire between your tools and MotherBot, in both directions, saying which is which as it goes. Underneath, every one of the 34 integrations drifts past as its real logo. The search and category filters are unchanged.
• Both pages animate on a phone now, not just on a desktop. The moving parts on these two pages are built so a phone plays them too, rather than showing a still picture of a diagram — and everything still stops for anyone whose device is set to reduce motion.
• The twelve feature walkthroughs are in plain English now. Every one of them was written for somebody who already knew the product — a chatbot step used to read “add nodes and connect them visually to define conversation flow”. It now reads “each block is one thing the bot says or does”. The drawn dashboard leads the page and plays itself, one short step at a time, and it now shrinks to fit a phone instead of being cut off at the edge.
• Each integration page shows what actually crosses, in both directions. It used to open with a paragraph and an arrow labelled “two-way sync”, which does not tell you what comes back. Every page now names the real things — order updates, deal stage, payment confirmed, coupon codes — travelling each way, and the setup steps and examples show one at a time instead of all at once.
• Every feature and integration page now shows a real conversation. A saree brand taking a ₹2,400 order at midnight, a clinic booking a slot on a Sunday, a Shopify cart recovered in twenty minutes with a coupon that genuinely worked at checkout — each one plays out as a chat, with a running list beside it of what MotherBot did at every step and what it was worth. Alongside it: the same working week shown twice, before and after; four numbers that change; six industries with the actual job each one uses it for; and answers to the questions people really ask, which also appear in Google.
• Fixed: the comparison pages had three animation faults. With “reduce motion” switched on — which includes every phone — the channel rings painted as complete circles before you scrolled to them, so it briefly looked as though both platforms had every channel. Filtering the comparison list by region replayed the entry animation for cards that had not moved. And the counters were being rebuilt on load, which restarted every animation on the page. All three are gone, and the pages are clean with motion on or off.

4 September 2026 — WhatsApp Groups

New

• Create a group and invite customers to it. Messaging → Groups. Give it a name and a description, choose whether anyone with the link joins straight away or waits for you to approve them, and share the invite link. If you already have groups on your number from somewhere else, Import existing groups pulls them in.
• One thread for the whole group. Send text, photos, videos, documents and approved templates to everyone at once, and read every reply in the same place, attributed to whoever wrote it. New messages appear as they arrive without a refresh. Pin a message so it sits at the top for everyone — WhatsApp allows three pinned at a time.
• Invite customers from your contact list. Pick people, pick an approved invite template, and WhatsApp sends each of them a card with the group and a join link. You get a line-by-line result — who was invited and who was not, and why. Anyone who has asked not to be contacted is skipped, and you are told.
• Decide who gets in, and who leaves. On an approval-required group you see who is waiting and approve or reject each one. You can remove somebody at any time, and reset the invite link if it has gone somewhere you did not intend — that stops the old link working immediately, for everybody who has it.
• Partners can be granted Groups separately. If a partner manages your account, WhatsApp Groups is its own grant under Partner Access — turning on Messages does not hand them your groups.
• Three separate permissions. Reading a group, posting to it, and running it are granted separately, because they are different jobs. Posting to a group is not covered by the Live Chat send permission — an agent can be allowed to answer private customer chats without being able to broadcast to a group, and the other way round.
• You are told who asked not to be messaged. If somebody in a group has blocked you or opted out of your marketing, the group screen says so before you post. WhatsApp gives no way to leave one person out of a group message, so MotherBot shows you rather than quietly deciding for you — remove them from the group if you want to honour it.

Worth knowing

• You cannot add somebody to a group — they have to join. That is WhatsApp’s design, not a missing feature here: every member arrives through an invite link they tapped. It is also why inviting asks you for a template — the invite is a message, and WhatsApp only allows an approved one.
• Eight people, and ten thousand groups. Those are WhatsApp’s limits, not ours — a group holds eight customers besides you, and a number can have ten thousand groups. Your plan may allow fewer groups than that; Billing → Usage shows where you are.
• Groups are billed like any other message. Each group message counts once against your monthly message allowance, and WhatsApp charges for it the same way.
• Some things do not work in a group. WhatsApp does not allow buttons and list messages, authentication templates, catalogue and payment messages, disappearing or view-once messages, or calls in a group. MotherBot tells you which one you tried rather than passing WhatsApp’s error straight through.
• Chatbots and drip sequences do not run in groups, on purpose. A bot written for a private conversation would answer all eight people at once, and someone typing “stop” in a group chat has not asked to be removed from your marketing. Group messages are also kept out of Sent History and the one-to-one inbox, which are about individual customers.
• Group messages do not count as a reply to a broadcast. A remark in a group was never addressed to your campaign, so it does not close the loop on one or end a drip sequence.

4 September 2026 — Video from a template, and “…is typing” on every channel that has it

New

• Typing indicator, on every channel that has one. While an agent is writing a reply — or a chatbot is composing one — the customer sees “…is typing”. Works on WhatsApp, Messenger, Instagram, Telegram and LINE, on the web and in the mobile app, and it is on by default. Settings → Live Chat → Message Behaviour turns it off. SMS, RCS and Viber provide no way to show it; your website widget has its own switch in Web Chat settings.
• Render a video from a pixbix template. Fill a motion design with a contact’s name, order or offer and send the finished video into the thread. A new pixbix: Render Video chatbot node waits for the encode and branches on the result, and Live Chat and the mobile app both show the render progressing rather than a spinner. Choose MP4, WebM, MOV or GIF, SD to 4K, at 24, 30 or 60fps.
• Saved capture presets. A capture of a real site is rarely one URL — it is a selector, a cookie banner to dismiss, three things to hide. Save that recipe in pixbix once and name it from a chatbot node, from Live Chat, from the app, or set it as your default. When the site changes you fix the preset there, not every flow that captures it.
• Read values off a page while you photograph it. A capture can now pull the headline, the price or the tracking status out of the same page load, so a bot can send the screenshot and quote what it says — with no second fetch that might see a different page.
• Copy a pixbix library design into your workspace. Library templates were browsable and not renderable, with nothing on this side to fix that. The template list now shows which ones are ready to use and offers a Copy button for the rest.
• Cost before you commit. Video credits scale with length and resolution, so the panel prices a render before it runs, and a refusal for credits now tells you how many were needed and how many you have.
• Clear a stale capture. If a page keeps coming back the way it looked yesterday, Integrations → pixbix → Capture now clears the reuse cache.

Changed

• pixbix looks like pixbix. Their logo, colours and lowercase name are used as their brand guidelines require, across the dashboard, the mobile app and the integrations pages.
• More output formats. Captures and image templates can produce WebP as well as PNG, JPG and PDF. WhatsApp will not show a WebP or a GIF as a picture — both go as a file to download — and the pickers now say so before you send one rather than after.

Worth knowing

• Read receipts on a second WhatsApp number never worked. A “mark as read” only exists on the number that received the message, and MotherBot was sending every one against your default number — so on an account with more than one number, conversations on the others silently never turned blue. Fixed for read receipts and for the new typing indicator, both of which now use the number the conversation is actually on.
• On WhatsApp, typing and read receipts are the same request. Meta provides no separate typing call — the indicator travels with the “mark as read” message, so showing one also turns the customer’s message blue. Rather than quietly undo a choice you made on purpose, MotherBot skips the indicator on WhatsApp when you have read receipts switched off. Every other channel is unaffected.

3 September 2026 — SMS and RCS, everywhere WhatsApp already was

New

• Broadcasts and sequences run on SMS and RCS. Choose the channel on the broadcast or the sequence itself. Everything else works as it always has, including the A/B split and the report. RCS sends rich cards and buttons through the gateways that carry them and steps down to plain text on the ones that do not, so a single broadcast still reaches the whole list.
• Fourteen gateways, or your own. MSG91, Twilio, Gupshup, Karix, Vonage, Plivo, Infobip, Sinch, Bird (MessageBird), Kaleyra, Route Mobile, Textlocal, Fast2SMS and Google RBM each connect with their own credentials, and a Custom HTTP option covers a gateway that is not on the list. The Indian gateways collect the DLT entity and template ids the regulator requires.
• One place to connect a channel. Channels is now the single connect screen for all ten — WhatsApp, Telegram, LINE, Viber, Instagram, Messenger, SMS, RCS, email and web chat — rather than a different screen per channel with different words on it.
• Chase a WhatsApp catalogue cart. A shopper who builds a cart in your own WhatsApp catalogue and taps Send opens a 24-hour window and then, very often, goes quiet. MotherBot can now follow that cart up inside the window as ordinary replies — no storefront to connect and no approved template to wait for, so it works on day one. The nudges stop the moment they reply, order or opt out, and hold over your quiet hours.
• Conversation outcomes. Snooze a conversation until a time you choose and it leaves the queue until then — or until the customer writes, which wakes it at once. Closing notes can be off, optional or required, with your own categories. Conversations nobody closes can close themselves after a number of hours you set.
• Comparison pages. motherbot.io/compare sets MotherBot against ten platforms on the points buyers actually ask about, feature by feature.

Fixed

• A STOP confirmation was swallowed on SMS, RCS and email. The opt-out was recorded first and the confirmation sent second — so the reply telling the customer they had been unsubscribed was blocked by the unsubscribe it was confirming. They heard nothing back, which reads as the opt-out having failed. The confirmation is now exempt from that gate, and only the confirmation.
• SMS and RCS ticks never moved. Most gateways offer one callback field, not two, so delivery receipts arrive at the same address as incoming messages — and that address was not reading them. A sent SMS stayed “Sent” forever. Delivery and failure are now read from that one address, so the report and the message ticks reflect what the network actually did.

30 August 2026 — Flows that read live data

New

• The Flow builder’s Data tab offers choices, not text boxes. Pick the spreadsheet, then its tab, then its column; the Calendly event type; the Trello board and then its list; the Zendesk group; or your own contact fields, segments, pipelines and products. Each list loads when you open that dropdown, and only apps your organisation has actually connected appear.
• Call any HTTP API from a workflow. A workflow step can send a request to a system of your own with the headers, body and authentication it needs, and use the response further down the workflow. Requests to private network addresses are refused.
• HubSpot deals on a Flow screen. A customer’s deals are found by walking HubSpot’s own link from the contact we matched, so “your quotes” means theirs — not every deal whose name happens to share a word with their own.
• CRM field mapping and sync. Map your contact fields to the CRM’s once, and the workflows on both sides read the same mapping.

Changed

• A Flow or chatbot is checked before it goes live. A screen that leads nowhere, a required field with no answer to give it, or a reference to something deleted is named at save, instead of failing silently in front of a customer.

29 August 2026 — Onboarding, the template library, Flows and Workflows

New

• Workflows. Build an automation from a trigger and a chain of steps, test it against a sample, run it by hand, activate it, and read every past run with the reason each one stopped. Duplicate a working one rather than rebuilding it.
• WhatsApp Flows, rebuilt. Create, preview, publish, duplicate and deprecate a Flow from inside MotherBot, start from a ready-made Flow template, and read every submission on the Flow’s own Responses page — with each response tied back to the contact who sent it.
• A template library worth browsing. Around 300 ready-to-submit message templates across 22 industries — retail, healthcare, education, logistics, travel, finance, real estate, food, events, NGOs and more — searchable in a full-height workspace on the web and on the phone. Pick one and it opens in the template editor, filled in.
• Guided onboarding. A short wizard covering your profile and your organisation, with the email address and mobile number verified by one-time code, so the account is complete before the first message goes out. It picks up where you left it.
• State pickers. Country, state and city are three linked lists rather than free text, on the web and on the phone.

28 August 2026 — Billing rebuilt, number transfer, Live Chat per number

New

• Billing answers the two questions you open it with. How long you have, and whether you are running out. The renewal date and the quotas closest to their limit are now the top of the page, instead of one of four identical tiles and an eighteen-bar list in fixed order that put the one at 96% below five reading zero.
• Pause a scheduled broadcast and resume it. Pausing a broadcast that had not started yet and resuming it reported “completed” without sending to anyone. It now sends to the audience it was created for.
• Filter Live Chat by WhatsApp number. A business running several numbers can work one inbox at a time, and the thread, the history you scroll back into and the messages arriving live all follow the number on screen. An empty thread names the number and says the history may sit on another one.

Changed

• The notification bell is gone from the dashboard header. Behind it sat a poller that ran on every page for every signed-in user whether or not anybody opened it. Notifications still reach you by email and on the phone.
• Live Chat holds its place when you change conversation. Opening another chat moves the messages and leaves the composer, the header and the contact panel where they were.

Fixed

• Transferring a WhatsApp number between organisations now works. Contacts the destination already has are merged and their history re-pointed rather than duplicated; a product or a sequence whose name is already taken is handled instead of colliding; both organisations are re-checked at the moment the transfer is accepted, not only when it was requested; a transfer can no longer complete in the middle of a broadcast; and the result says what it had to reconcile rather than only “Completed”.
• Message previews stopped being pushed to everyone. A live update carried up to 100 characters of message text to every member of the organisation, including members restricted to their own conversations. It no longer does.
• The WhatsApp-number filter no longer hides other channels. Filtering the inbox by a WhatsApp number was hiding Telegram, Instagram and every other conversation that has no WhatsApp number to match.
• Call screens stopped polling without a limit. One inbound call to a large team had every ringing device asking for its status every two and a half seconds, unbounded. Those four endpoints are now rate limited like every other one.
• An unlimited quota no longer draws a full bar. On an unlimited plan every usage row read as though it were at its limit. An unlimited row now draws no track and reads the count followed by “Unlimited”.

27 August 2026 — Broadcast audiences, scheduling, and forms with room to work

New

• See exactly who a broadcast goes to. The audience is a list you can read and search, not just a count — and you can pull a recipient out of the queue before it sends, or find them again afterwards.
• Reply to a message, and react to one. Quoting a message and reacting to it now work on every channel whose provider supports them, and are refused at the point of sending on the ones that do not, rather than appearing to work.
• Contacts and templates get their own pages. Creating or editing a contact, and building a template, are full pages rather than a panel squeezed above the list — one form each, so the two can no longer drift apart.
• Your own login history. Team members can see where their account is signed in and end any session, themselves.
• Pipeline boards from the web. Creating and deleting a board worked in the app and not in the browser. Now both.
• Retry a failed Knowledge Base document, from the web and from the phone, with a message that says what actually went wrong.

Changed

• One password rule, on every door that sets one. Sign-up, reset, change and invite acceptance all enforce the same rule — eight characters with a capital and a number — shown as a live checklist as you type.
• Every timezone, searchable, and the same list in the browser and in the app, under the modern names rather than the legacy ones.
• You can see which workspace you are in, and what you are in it — name and role, in the sidebar and in the account menu.

Fixed

• Nothing schedules into the past. A broadcast, a sequence or a live-chat message set for a moment already gone is refused at every surface that can set one, including the app’s time wheels, which had no floor at all.
• Scheduling reads your organisation’s clock on every device. A time picked in the app or in live chat was pinned against the phone’s or the server’s zone, so “9 am” meant a different moment depending on where it was typed.
• Updating a contact through the API applies what you sent. The one door that could write a name with anything at all in it validated nothing, and switching consent through the API never reached the consent record.
• A contact’s name may contain a bracket. Searching for one no longer breaks the search.
• A paused team member is told they are paused when they try to sign in, rather than meeting an error that explains nothing.
• Blog posts render properly. Tables were publishing as a run of paragraphs and links as their raw markup.

26 August 2026 — Knowledge Base accuracy, one clock, international contacts

Fixed

• The AI was throwing away right answers. A single fixed relevance cut meant a short question scored lower than a long one against the same paragraph, so “what is the return policy” was answered and “refund” went blank — and short questions are what customers type. The cut is now judged against the best match found, so the bot answers both and still says nothing to a question your content does not cover.
• A Google Drive link was indexed as its sign-in page. Importing a Drive URL stored the “Loading… Sign in” shell and marked it ready — and because that text carries the file’s name, it outranked the real document. Drive links are refused at import now, with a message telling you to upload the file instead.
• Knowledge Base PDFs failed to upload at all, with an error naming a file that had nothing to do with yours.
• Long documents were cut without saying so, and a failed document had no name, so eight of them read “Untitled” with no way to tell which upload each had been. Both now say what happened.
• Non-Indian numbers were rejected outright. Creating a contact through the API with any country code but +91 failed, and the CSV importer skipped those rows and reported them back to you as bad data. Numbers are now read against the country their own code names.
• Custom fields sent by an integration were stored where nothing reads them. Posting the field’s human name — the one shown in Settings — now writes into that field, instead of a key no screen displays.
• Template usage always read zero. Nothing had ever counted a send against its template, so the “Used” column, the “Never used” filter and the app’s preview reported nothing on templates that had been sent hundreds of times.
• The composer stopped carrying your draft into the next chat. Text typed to one customer followed you into the next conversation and sat in the box addressed to somebody else.
• Read receipts tell the truth per channel. Each channel shows only what its provider actually reports — Telegram, for instance, has no read receipt to give, and pretending otherwise was worse than showing nothing.
• Renaming yourself or your organisation no longer needs a sign-out for the new name to appear.
• A Google account can set a password, so signing in without Google is possible afterwards.
• LINE emoji arrived as words, and voice notes were refused as an unsupported file type on Telegram and LINE. Both send and render now.
• The API reference described endpoints that did not exist. Date filters on the messages endpoint were documented and ignored — asking for last week returned your whole history — eleven working parameters were undocumented, and three documented limits were unenforced.

Changed

• Every timestamp reads against your organisation’s clock. Dates were formatted in whatever zone the viewer’s device happened to be in, so the same broadcast showed one send time to an owner in Dubai and another to their agent in Manila — and, worse, “Today”, “Yesterday” and the day headings in a conversation were computed from the device’s midnight, filing the same messages under different days for two colleagues. Everything now uses the timezone in Settings → Organization, on the web, in exports and on the phone. Invoices are stamped in IST, because the tax point belongs to the issuer.
• Connecting LINE has real instructions. Seven numbered steps naming the console, the tab and the button for each — including the two that decide whether the connection works at all: switching “Use webhook” on, and turning LINE’s own auto-replies off so your customer does not get two answers from one business.
• Billing usage rows name themselves. A limit in your plan can no longer be missing from the usage list, and the two places that list usage can no longer disagree about what a row is called.

25 August 2026 — Team access enforced everywhere, and chatbots on every channel

Fixed

• Chatbots went silent every evening. The bot router checked business hours before anything else, so on any organisation with hours set, every bot on every channel stopped answering the moment the day ended — and nothing said so. A bot now answers around the clock unless you ask it to keep your hours, and when it does keep them the message reaches a human instead of disappearing.
• The 24-hour reply window was applied to channels that do not have one. It exists on WhatsApp, Messenger and Instagram. A scheduled Telegram, SMS, email or web-chat message was being cancelled once 24 hours had passed since the customer last wrote, with an error about a WhatsApp window that channel has never had.
• Team members saw WhatsApp numbers they were not given. The web listed all of an organisation’s numbers — names, quality ratings, messaging limits — to a member scoped to two of them, and let them send from any. The app had always filtered; the web had not.
• Dashboards showed what the screens beneath them hid. Call volume, talk time, answer rates and conversation summaries were reported for the whole organisation to members restricted to certain numbers or to their own conversations.
• Message content was pushed to every member of the organisation. Live updates carried the message body, the contact’s name and their phone number to every signed-in browser, and the inbox filtered them only when deciding what to draw. It is no longer sent.
• Team members could read the plan, its price and your usage. The screens that legitimately need to know which features are on now ask that question instead of reading the whole commercial record.
• Signing out in one tab left the others usable, still receiving live customer messages, until something forced a refresh. Signing out now ends every tab at once, and a session revoked from elsewhere signs an idle phone out immediately rather than waiting for it to ask for something.
• A chat assigned to a team member appeared only after a refresh — the moment the product most needs to be live, because somebody has just been handed work.
• Deleting something now removes its files, and deleting an organisation works at all: the confirmation screen was sending nothing, so every attempt failed with an unexplained error.
• Telegram poll and quiz answers were unreachable, Telegram albums and chatbot media uploads failed, and a Telegram connection that has drifted now repairs itself.
• LINE dropped media it could not play, silently. An outbound audio file in the wrong format returned success and simply never arrived. Files LINE cannot carry are refused before sending now, with a reason.
• Calls appear in the conversation alongside the messages, and a failed call reports the actual reason rather than a code.
• Cart orders on the phone show product names. WhatsApp sends a basket as catalogue ids; the web had always resolved them to real names, prices and pictures, and the app showed the raw ids.

Changed

• Cities come from one shared list. Typing searches it and only a chosen value is saved, so “Bengaluru”, “bengaluru” and “Banglore” can no longer be three places, with a segment on one quietly excluding the others.
• Phone numbers are validated per country wherever a contact is created — by hand, by import, or through the API. A landline is accepted and flagged as unlikely to be on WhatsApp rather than refused; a supplier’s office number belongs in a CRM.
• Name and email rules, stated once. A person’s name may not contain digits and an organisation’s may — 3M and 99acres are customers — and names in Devanagari, Arabic, CJK or with accents are accepted everywhere.
• The AI model is a dropdown, filled by the provider through your own key, so a mistyped model id can no longer save cleanly and then fail hours later on a real call recording.
• Product pickers show status and stock, so an out-of-stock item is visible as one before it is put in front of a customer.
• Integration secrets are no longer offered by the browser’s autofill.

17 August 2026 — Team access, end to end

New

• Record visibility — a third access scope, next to WhatsApp numbers and channels. Switch on “Only what’s assigned to them” in Team and that member sees only their own conversations and contacts, in Live Chat, Support Desk, Contacts, Sent History, Analytics, the mobile app and the extensions. Off by default. See Team Access.
• Read-only really is read-only. A member with view access but not manage no longer sees Create, Edit, Delete, Deploy or Send controls at all — across broadcasts, templates, chatbots, flows, products, quick replies, webhooks, the knowledge base, recurring broadcasts, the web chat widget and the channels hub.
• Staff can build. The chatbot builder and the WhatsApp Flow editor now exist for team members holding the matching manage permission — previously those screens were owner-only and the buttons leading to them went nowhere.
• Delegated call analysis. Agent scorecards are governed by the Call Analysis permission, so a team lead can be given the league table without being made an account admin. The figures are limited to the numbers that member works.

Changed

• Removing someone takes effect immediately. Deleting or deactivating a team member now ends every session they hold, in the browser and on the phone, at once. Editing their permissions reaches sessions they already have within about a minute — no more signing out and back in for a change to apply.
• Sign-in explains itself. A member whose access does not include the mobile app is told so at the sign-in screen, naming the permission to ask for, instead of signing in and meeting an unexplained error.
• Templates follow number access. A member scoped to specific numbers sees only those numbers’ templates — including the ones shared across a WhatsApp Business Account, which they can legitimately send.

Fixed

• New chats now arrive live for team members. Live Chat’s realtime feed discarded any conversation that was not yet assigned — which is every new incoming chat. Agents had to refresh to see new conversations, and non-WhatsApp channels appeared not to work at all.
• The channel filter appears when it should. The inbox’s channel filter is built from the channels your organisation actually uses and the member is allowed to work, instead of only appearing once a non-WhatsApp conversation happened to be on screen.
• Exports open correctly in Excel. CSV files downloaded from the API — ad performance, consent, contacts, quotations, call and desk reports — were read by Excel in the local character set, so an em dash appeared as â€" and non-Latin names were mangled. Every export is now marked as UTF-8, and filenames with non-Latin characters no longer break the download.
• Buttons that led nowhere. Links inside shared screens pointed at the owner’s version of a page, which bounced a team member to their dashboard with no explanation — “Build from Scratch”, “Use template” and “Scorecard” among them. Team members now land on their own version of the page, or on a clear Access Restricted message if they may not open it.