TLDR: Your dashboard has been rebuilt into a welcome page that shows what is set up and what is still waiting for you. The File Manager now refuses to delete a file your chatbot still uses, so customers stop getting broken media. Pictures with a caption arrive properly too.

Here's what's new 👇

🏠 A Dashboard That Shows You Where You Are

The problem: Your dashboard opened on a row of figures and a chart. That told you very little while you were still setting things up, and nothing at all about what was left to do. New businesses landed there with no idea what the next step was.

• The dashboard is now a welcome page. ✨
• A
• A
• Your referral card, your plan usage and your important links all stay where they were, on the right.
• The old figures row and chart are no longer on this page.
• If you had bookmarked the dashboard with a tab in the link, it still opens fine. It simply lands on the welcome page.

📁 Files Your Chatbot Still Needs Cannot Be Deleted

The problem: Deleting a file in File Manager never checked whether a chatbot was still using it. The file went, the chatbot kept pointing at it, and your customer received a broken image or nothing at all. Nothing warned you, so the usual way to find out was a customer telling you. This had been quietly building up across many businesses.

• Deleting a file that a chatbot still uses is now blocked, and you are told exactly what is using it. 🔒
• It checks everywhere a file can end up: your AI behaviour, your training data, keyword replies, follow-ups, knowledge documents, and drafts you have not published yet.
• Deleting a folder follows the same rule. Anything still in use is kept, and you get told which files were kept and why.
• Select a mix of files and the ones nobody is using still delete as normal.
• Files nothing points at delete exactly as they always did.

🛠 Bug Fixes

• Pictures sent with a caption now reach your customer.
• Your help button and your links card now agree.

TLDR: Your contacts get a proper board with columns you can name and cards you can drag, now in early access. Your chatbot no longer blue ticks a customer it cannot answer. And the delivery numbers on your Blast dashboard now count what really went out, not who was on the list.

Here's what's new 👇

📋 A Contacts Board You Can Drag (Early Access)

The problem: Your contacts lived in one long list. There was no way to see who is a new enquiry, who is still deciding, and who has already bought, so tracking a customer through your sales process meant keeping it all in your head or in a separate spreadsheet.

• Contacts now sit on a board with columns, one card per person, so you can see your whole pipeline at a glance. 👀
• Drag a card to move someone forward, and it stays there after a reload.
• Name your own columns and pick their colours, up to five, plus a holding column for anyone you have not sorted yet. ✨
• Filter the board however you like and save the views you keep coming back to.
• Tap a contact to see their details right beside the board, and add new people straight into any column.
• Removing a column that still has people in it parks it instead of losing them. Put the column back and everyone returns exactly where they were, and the app tells you which of the two will happen before you save. 🔒
• Your labels keep working. If your chatbot, an import, or your own tools tag a contact, the card moves on the board too.
• This is early access and it is off by default. It comes with Business plans and trials, and we are switching it on business by business, so tell us if you would like it. 🚀

📊 Blast Numbers That Mean What They Say

The problem: The delivery figures on your Blast dashboard were worked out in four different places, in four different ways, so the same campaign could show very different results depending on which screen you were looking at. The big one: the rate counted everybody a campaign was addressed to, including drafts and scheduled campaigns that had never messaged a single person.

• There is now one way of counting, used everywhere, so every screen agrees. ✅
• The middle card on your Blast dashboard is now called "Messages delivered" instead of "Recipients reached", because that is what it was actually showing.
• Your numbers there will look different, and lower, from now on. Nothing changed about your campaigns, the old figure was simply counting people who were never sent anything.
• The caption under it spells out both halves, so you can see exactly what is being divided by what.
• The main card on your Blaster page is unchanged, it was already counting correctly.
• Deleted campaigns no longer quietly pad your live delivery figures, and a rate can no longer creep above 100%.

🛠 Bug Fixes

• Your chatbot no longer blue ticks customers it cannot answer.
• A safer check on opening hours.

TLDR: Connect Claude or ChatGPT straight to your ReplyLa inbox in early access, so an assistant can read chats and reply under limits you set. The Retry button on a failed photo, video or voice note now genuinely re-sends it. Sending a video from File Manager is fixed too.

Here's what's new 👇

🤖 Connect an AI Assistant to Your Inbox (Early Access)

The problem: Your customer conversations live in ReplyLa, and the AI assistants you already use every day cannot see any of them. Anything you wanted an assistant to help you with meant copying chats back and forth by hand.

• Connect Claude, ChatGPT or Codex to your inbox through a guided setup in Integrations, AI Agents. 🔌
• Your assistant can then read a conversation, look up and tidy contacts and labels, reply to a customer, and send an approved template, all without you leaving the assistant you are working in.
• You decide exactly what it may do. Reading only, or reading and replying. You can change that later without disconnecting and starting over. 🔒
• It stays inside one business. An assistant connected to one business can never see another one's customers.
• If a team member loses access or leaves, their connection loses that power straight away.
• One page in Settings lists every connected assistant in plain words, and one button cuts any of them off.
• This is early access. It is switched off by default and we are turning it on business by business, so tell us if you would like to try it. ✨

🔁 Retry on a Failed Photo, Video or Voice Note Now Works

The problem: When a photo, video or voice note failed to send from the Inbox, pressing Retry showed a cheerful green "queued for retry" message and then quietly did nothing at all. It has never once succeeded since the button was added, and voice notes were hit hardest.

• Retry now re-sends the original file the same way the first attempt did, so it actually goes out. ✅
• A retried voice note arrives as a proper voice note with a waveform, not a plain attachment.
• If the file really is no longer stored, you get an honest message saying so, instead of a green tick that meant nothing.

🛠 Bug Fixes

• Sending a video from File Manager works again.
• Stronger data privacy between organizations.

TLDR: Inbox search and filters now look through every conversation, not just the newest handful, and the list no longer stalls while you scroll. Starting a new conversation from a template works properly again, and the brand colour picker now accepts light shades plus Yellow.

Here's what's new 👇

🔍 Inbox Search & Filters That Look at Every Conversation

The problem: Searching your Inbox, or filtering by unread, assigned, unassigned or a label, only ever looked at the newest 20 conversations in your list. Everything older was invisible to the search box, so a lead from last week simply never came up. One merchant spent over five minutes scrolling to find a customer by hand.

• Search and filters now look through every conversation on that device, however far back it goes. 🎉
• Unread, label, assigned and 24 hour window filters all surface older matches too.
• Scrolling no longer gets stuck. The list used to reach a point where it kept spinning forever without loading anything more.
• This one has been there since the Inbox first launched, so it is worth a fresh look at any old chat you gave up on finding.

✍️ Starting a New Conversation Works Again

The problem: When you start a new conversation using a template that has blanks to fill in, the Review button on the template step could never switch on. The boxes for filling those blanks sat on the next step, which you could only reach through the button that was already switched off. The button looked perfectly normal, it just never did anything.

• Those boxes now sit right beside the template they belong to, so you fill them in and Review switches on. ✅
• The final step is now purely Review and Send.
• Templates with a link button that needs filling in can be used at last. Before this, those could never be sent to anyone.

🎨 Brand Colours: Light Shades & Yellow

The problem: The brand colour picker in Settings only worked with darker colours. Anything light left the white text on top of it unreadable, so lighter brand colours were simply not offered to you.

• ReplyLa now picks white or almost black text automatically, whichever reads clearly on the colour you chose. 🌗
• Yellow
• Nothing changes unless you pick a light colour. Your existing brand colour looks exactly as it did.
• Small fix along the way: highlighted buttons in the Inbox no longer turn grey when your mouse passes over them.

📅 Appointment Booking Is Paused for Now

The problem: The last release introduced a chatbot that can check your Google Calendar and book appointments. Google has not finished reviewing our calendar connection yet, so we have switched the feature off rather than leave it running on a temporary approval.

• The Google Calendar tool is hidden from the AI Tools list for the moment.
• Nothing else about your chatbot changes, and no calendar of yours is touched.
• It returns as an early access feature once Google's review is done, and we will announce it here.

🛠 Bug Fixes

• Follow-ups now work for customers who hide their phone number.
• Your Activities feed stops lumping private customers together.
• File picker buttons are reachable on a phone.
• A single video no longer slows everything else down.
• Blast campaign numbers no longer double-count.

TLDR: A conversation that went silent after a customer tapped a button on a fancy styled template now replies normally again, and any chat already stuck this way recovers on its own. Human takeover alerts also gain an Inbox link shortcut for customers who hide their number.

Here's what's new 👇

💬 Conversations That Went Silent Now Reply Again

The problem: Some templates are written with fancy styled letters, the bold decorative kind. When a customer tapped a quick reply button on one of those, that single conversation could stop working for good. Every message the customer sent after that came back as the same apology, forever, even though every other chat was perfectly fine. Nothing in your dashboard explained why, and there was no way to unstick it yourself.

• Those conversations reply normally again. 🎉
• Any chat that was already stuck this way recovers by itself, you do not need to do anything or contact support.
• The cause is fixed at the source, so a styled template can no longer break a chat in the first place.
• We also cleaned up the affected chat histories behind the scenes, so nothing lingers.

🔗 Clearer Shortcuts in Your Human Takeover Messages

The problem: When your chatbot hands a chat to a human, the alert it sends your team can carry shortcuts like the customer's name or a summary of the conversation. One useful shortcut existed but was never offered to you: a direct link straight to that chat in your Inbox. That mattered most for customers who hide their phone number, because there was no other way to reach them.

• Inbox link
• Intent
• If a customer hides their phone number, the phone shortcut simply stays blank instead of showing something unusable. Use the Inbox link for those.
• Customer names with unusual symbols in them are now written out correctly in the alert.

🛠 Bug Fixes

• Shortcuts no longer arrive as raw text.

TLDR: Your chatbot can now look at your Google Calendar and book, move, or cancel appointments for customers on its own. Scheduled Blast campaigns finally get a "Change schedule" and "Cancel schedule" button, and a bug that could send a scheduled Blast hours early is now fixed. If you run more than one business in ReplyLa, you can also choose which one you land in at login.

Here's what's new 👇

📅 Your Chatbot Can Now Book Appointments in Google Calendar

The problem: A customer asking "are you free tomorrow at 3?" always needed a human. Your chatbot could answer questions about your business, but it could not see your calendar, so every booking, change, and cancellation had to be handled by hand, usually hours later.

• Connect your Google account, pick a calendar, and your chatbot can check what is free and book the slot right there in the chat. 📆
• It can move a booking to a new time or cancel one, all from the same conversation, and it will never create a duplicate booking by accident.
• It understands everyday wording in any language, so "esok pukul 3" and "tomorrow at 3" both land on the right date.
• Customers only ever see their own bookings. One customer can never read or change another customer's appointment. 🔒
• When it tells a customer which times are free, it shows only the times, never anyone else's name, email, or details.
• You choose how far it goes: let it only check availability, or let it book and change appointments on its own.
• It can also email the customer a calendar invite, but only after asking them and only if they say yes. This one stays switched off until you turn it on. ✨

⏰ Scheduled Blasts: Change the Time, or Call It Off

The problem: Once a Blast campaign was scheduled, there was no way to move it or call it off. The only escape was to duplicate the campaign, set the copy up again, and delete the original. Worse, the main "Start campaign" button on a scheduled campaign sent to everyone straight away, with no warning and no way to pull it back, so a single stray click could fire your whole audience long before their time.

• "Change schedule" lets you pick a new day and time without touching anything else about the campaign. 🗓
• "Cancel schedule" puts the campaign back to draft and clears the date, so nothing fires.
• Choosing to start a scheduled campaign right now asks you to confirm first, showing the time it was set for and how many people it will reach. Keeping the schedule is the default answer, so a stray click cannot send to everyone by accident.
• Saving a draft that still carried an old schedule now clears that date, so a schedule you thought was gone cannot fire behind your back.
• If you change the audience and then reschedule, it sends to the new audience, not the old one.
• Campaigns still waiting on WhatsApp template approval can be cancelled the same way, in one click.

🏢 Land in the Right Business When You Log In

The problem: If you belong to more than one business in ReplyLa, logging in always dropped you into the same one. Every session started with a switch before you could get any work done.

• Star the business you want on your Organizations page, and every login takes you straight there. ⭐
• It works the same whether you log in with a password, with a verification code, or with a magic link.
• Your personal workspace keeps its "Default" badge and never moves, so you can always find your way home.
• If you later leave that business, ReplyLa quietly puts you somewhere sensible and tells you the choice is no longer valid, with a button to clear it.

🔌 Reconnect Your WhatsApp Number Yourself

The problem: Some merchants opened ReplyLa to find their WhatsApp number showing "account disabled, contact support", with no button to fix it, even though the number was perfectly healthy on WhatsApp's own side. The link between the number and ReplyLa had been removed, but ReplyLa treated it as if the whole account was gone for good, so there was no way out from inside the app.

• ReplyLa now tells those two situations apart. A number that is genuinely gone still points you to support, but a number that only lost its link now shows a Reconnect button you can press yourself. 🔗
• Reconnecting takes seconds and does not need anyone from our team.

🛠 Bug Fixes

• One admin can now cover several takeover categories.
• Categories with nobody assigned now use your own wording.
• Switching business from a channel page no longer leaves you stuck.
• Stronger data privacy between organizations.

TLDR: A broadcast using a template with a picture at the top could fail for every single recipient, burning your whole audience for nothing. It now checks first and stops with a clear reason instead. Your AI follow-ups also use the customer's real name instead of "there".

Here's what's new 👇

📢 Broadcasts Stop Before They Burn Your Whole Audience

The problem: If you sent a broadcast using a template with a picture, video, or document at the top, and ReplyLa could not read that file at the moment of sending, it quietly sent WhatsApp a link WhatsApp could not open. Every message failed. One real campaign went out to 100 contacts and all 100 failed. Worse, hitting "Resend to failed" did no checking at all, so it burned through the same audience a second time.

• ReplyLa now checks the file right before sending, at the exact moment the sending happens, not just when you set the campaign up. 🛡
• If the file cannot be used, the campaign stops before a single message goes out, and tells you which template is the problem.
• Nobody in your audience is used up, so you can fix the template and send to the full list.
• "Resend to failed" now runs the same check, so it can no longer repeat the same failure on the same people.

👋 AI Follow-Ups Now Use Your Customer's Real Name

The problem: When your chatbot sent a follow-up message, it greeted the customer as "there" instead of using their name. It was looking for the name in a place nothing ever fills in, so effectively every WhatsApp contact came out nameless, even when their name was sitting right there in your inbox.

• Follow-ups now use the name shown on the contact in your inbox. ✨
• If a contact has no proper name, just a phone number or an emoji, ReplyLa leaves the greeting clean rather than inventing a name or falling back to "there".
• The same naming applies when you test in the AI Playground, so what you see there matches what your customer gets.

🛠 Bug Fixes

Failed template sends now show WhatsApp's own reason. When WhatsApp rejected a broadcast template, ReplyLa showed only a generic failure while WhatsApp's actual explanation was thrown away. That explanation now appears alongside our guidance, so you can tell what really needs fixing. 🔍

Account updates from WhatsApp now reach you. Updates WhatsApp sends about your account itself, things like account reviews, template status changes, and phone number changes, were being delivered to an address that no longer existed, so they never arrived. They now land properly and your account details stay current.

Locked-in prices now include the extras you bought. If your price was locked in at an older rate and you later bought extra seats, devices, or storage, those extras were not being added to your renewal, so you were getting them free. Renewals now quote your locked base price plus whatever extras you added. Nothing is charged backwards, this applies from your next renewal onward.

We tightened security so your data stays private to your own organization. 🔒

TLDR: If you have a large template library, your approved templates could stay stuck showing "Pending" for days even though WhatsApp had already approved them. Syncing now finishes properly, statuses refresh, and a blocked sync gives you a clear reason instead of a vague error.

Here's what's new 👇

🔄 Approved Templates No Longer Stuck on "Pending"

The problem: If your WhatsApp account held 100 or more templates, refreshing your template list never finished. It kept asking WhatsApp for the same page of templates over and over until WhatsApp blocked the account for making too many requests, then threw away everything it had already collected. The result: templates WhatsApp had approved days ago kept showing as "Pending" inside ReplyLa, even though sending them worked perfectly fine.

• Template refreshes now stop as soon as there is nothing new left to collect, so your list actually updates. ✨
• Statuses catch up on their own within half an hour of this update. Nothing for you to do.
• Big libraries are safe now: the refresh is capped, so it can no longer flood WhatsApp and get your account temporarily blocked.
• If a refresh manages to fetch only part of your list, ReplyLa leaves the rest of your templates alone instead of wrongly marking them as deleted from WhatsApp. 🛡

🛠 Bug Fixes

A blocked sync now says it was blocked. When WhatsApp temporarily limits how often your account can be checked, template syncing used to show a generic "Something went wrong". It now tells you plainly that WhatsApp is limiting the account, so you know to simply wait and try again.

"Sync All" stops claiming success when a channel failed. If one of your connected numbers could not be reached during a bulk sync, ReplyLa still reported the whole run as successful. It now tells you some devices could not be reached, and for a single channel it shows WhatsApp's own reason.

TLDR: When a message you send from the Inbox fails, ReplyLa now tells you the real reason instead of a vague error. Picking an unsupported image for a WhatsApp template no longer fails in silence, and scheduled campaigns waiting on template approval now email you the reminder, not just an in-app bell.

Here's what's new 👇

📤 Failed Inbox Sends Now Tell You Why

The problem: When a message you sent from the Inbox failed to go out, the error was vague. You could see it had failed, but not why, so you were left guessing: was it the 24-hour messaging window, a bad number, or something else?

• A failed inbox send now shows the actual reason WhatsApp gave, for example that the 24-hour messaging window has closed. 🎯
• No more guessing: you can tell straight away whether you need to send a template, fix the number, or simply try again.

🖼 Template Image Errors No Longer Fail Silently

The problem: If you picked a .webp image as a template header, both Submit and Save as Draft would just fail. The spinner stopped, no error appeared, and you had no idea the image was the problem. (WhatsApp only accepts JPG or PNG for image headers.)

• ReplyLa now flags an unsupported image the moment you pick it, before you ever hit Submit. ✨
• If the server rejects an image, you get a clear message telling you exactly what went wrong, both on the field itself and as a popup.
• Already stuck on this? Re-save the image as a JPG or PNG and it will go through.

🛠 Bug Fixes

• Scheduled campaign reminders now email you, not just an in-app bell.

TLDR: You can now push your WhatsApp activity straight into your own automation tools like Zapier, Make, and n8n (early access). Times across the whole app now show in your organization's timezone, so your whole team sees the same clock. Plus, new message alerts now reach everyone on your inbox team, and you get a clear heads-up whenever a chatbot feature is paused for maintenance.

Here's what's new 👇

🔗 Send Your ReplyLa Activity to Your Other Tools (Early Access)

The problem: Everything that happened in ReplyLa, a new lead, a new message, a chat handed to a human, stayed locked inside ReplyLa. If you wanted to feed that into your own automation tools (Zapier, Make, n8n, Pabbly) or your CRM, there was simply no way to connect them.

• A new Integrations page lets you paste the web address from your automation tool, tick the events you care about, and ReplyLa sends them there automatically. ✨
• 27 events are covered in this first version: new contacts, label changes, new messages, conversation updates, AI to human handovers, broadcasts, and more.
• You can point each connection at just one WhatsApp number if you only want events from that channel.
• A Delivery Log shows you exactly what was sent and whether it arrived, so you can see it working.
• Each connection gets its own secret key, so the tool on the other end can confirm the messages genuinely came from ReplyLa.
• You can set up to 5 connections per organization.

This is available now as early access to merchants on the beta program, and it's on the way to everyone. If you'd like in early, let us know. 🎯

🌏 Times Across the App Now Show in Your Timezone

The problem: In an earlier release you could set your organization's timezone, and it fixed the date and time variables in your blast messages. But everywhere else in the app, times still followed each person's own computer clock. So two teammates sitting in different places, or anyone whose computer clock was set wrong, saw different times on the very same chat.

• Building on that timezone setting, times across the app now show in your organization's timezone. 🕒
• Inbox message times, the Today and Yesterday grouping inside a chat, contact and event details, and your token usage history all follow it now.
• Everyone on your team sees the same time for the same message, no matter where they are or how their computer clock is set.

🔔 New Message Alerts Now Reach Your Whole Inbox Team

The problem: The bell that lights up when a customer just messaged in only reached the account owner. Everyone else helping run the inbox was left out, so unless the owner happened to be watching, a fresh message could sit there unnoticed.

• Anyone on your team with inbox access now gets the new-message bell, not just the owner. 💪
• It now also covers coexistence channels, the numbers you keep using in the normal WhatsApp app alongside ReplyLa.

🚧 A Heads-Up When a Chatbot Feature Is Paused

The problem: Now and then a chatbot feature (like the AI Checker or the Off-Topic Guard) gets temporarily switched off for maintenance. When that happened you had no way of knowing, so a feature you thought was protecting your chats was quietly not running.

• The chatbot setup pages now show a clear banner whenever one of these features is paused for maintenance, so you always know why it is not running. 🚧
• The AI Playground shows the same notice, and it now matches real behaviour: a feature that is paused no longer runs when you test in the playground, just as it would not run for a live customer.

🛠 Bug Fixes

• Takeover alerts now name phone-hidden customers.
• Playground now plays audio, video, and documents properly.