Projects: a client project can now be invoiced straight from the project screen. The Actions menu offers Invoice this project when the project has a price, and creates a draft invoice with a single Tasks line listing the project's tasks for that price.
Projects: when a project has no price, the Actions menu offers Invoice members timesheets instead, and creates a draft invoice with one line per logged timesheet entry — the team member and job title as the line title, the task as the description, the logged hours as the quantity and the member's hourly rate as the rate.
Projects: team members can now be given an hourly rate per project, from the dollar icon on each member in the Project members card. The same person can be billed at a different rate on a different project, and a member left without a rate is simply not billable.
Both invoicing actions ask for the bill date, the due date and the tax before generating, suggesting the client's default tax. The chosen tax is applied to the invoice and every generated line is taxable.
Team Messenger → Guests: a new Convert to lead button, next to the ticket button. A visitor who came in through the website chat becomes a lead in one click — the name, email address and phone number they typed into the chat are carried over, along with the country and city they wrote from.
The whole conversation is filed on the new lead as a note, so whoever picks it up reads the request in the visitor's own words instead of a summary. Internal notes your team wrote in the thread stay private and are never copied across.
The visitor becomes the lead's primary contact, and the conversation stays open in the Guests tab — they are still typing, only the record they now belong to has changed. Once converted, the same button opens the lead, so a conversation can never be converted twice.
Converting works for any guest conversation, not only the website chat: a WhatsApp or Telegram stranger is converted the same way, and their number becomes the lead's phone number.
If your workspace has a lead source named after the channel (for example "Website"), it is filled in automatically. Nothing is invented — a source that does not exist is simply left empty.
Team Messenger: a new Support tab. Every conversation your clients have with the Marvin assistant now appears there, so your support team can read them and step in — until now those chats were private between the client and the assistant, and nobody else in the workspace could see them.
Support: conversations waiting for a human float to the top of the list, and a red counter on the Support tab shows how many nobody has picked up yet.
Support: a new Waiting filter listing only the conversations that were handed over and have not been answered.
Marvin now hands a client conversation to your team by itself when it cannot answer, and whenever a client asks to speak to a person — in any of the supported languages.
A team member can take over any client conversation at any time. Marvin stops replying the moment someone does, and the "hand back to the assistant" button returns it.
Clients see one continuous conversation: replies from your team arrive in the same thread, signed with the name of the person answering.
A conversation nobody answers is escalated after a few hours — administrators are notified by email, and over Telegram when the Marvin bot is connected. The delay is configurable in Settings (default 4 hours; 0 turns it off).
Support conversations can be assigned, forwarded, closed and turned into a support ticket, exactly like the Guests inbox.
Conversations your clients had with the assistant before this release are not lost: the first time a client writes again, the whole earlier conversation appears in the Support tab with it.
Support is not only for the messenger: a client writing on WhatsApp or Telegram lands in the same tab, each row showing which channel it came from. Support now means "a conversation with a client we recognise", wherever it arrived.
A conversation moves tab by itself as soon as you know who it is. An unknown WhatsApp number sits under Guests; the moment it matches a client contact — or you link one by hand — it moves to Support. Unlinking moves it straight back, so a wrong guess costs nothing.
Replying to a client who came in over Telegram reaches them on Telegram, not only in the workspace. The thread header names every channel the client can be reached on.
The Support tab is shown only to the team members allowed to send messages to clients (Settings → Client permissions), and to administrators. If your workspace has never set that list, every team member who can see the conversation inbox sees Support too.
Team Messenger — Guests and Groups conversations now have a full composer: emojis, file attachments, and voice messages recorded straight from the browser.
Emoji reactions on any message in a conversation. Reactions the person adds on WhatsApp appear in the thread within seconds, and your team can react to each other's messages. (Sending a reaction back out to WhatsApp is not possible with the current provider, so reactions your team adds stay inside NIZU.)
Reply to a specific message. Replying to one of your own messages produces a real WhatsApp quote bubble; replying to something the customer sent shows the quoted line in italics above your reply, because WhatsApp's gateway cannot quote an incoming message. Tap a quote in the thread to jump back to the original.
Copy the text of any message with one click.
The assistant now always replies quoting the message it is answering, so its answers can never be mistaken for a reply to something else.
Every conversation shows who you are talking to: the client contact, lead or team member behind the number, with their company, role, team and source, and a link straight to their profile. Unknown numbers are matched automatically, and you can link or unlink a person by hand.
Forward a conversation to a team member from the conversation header. They are told immediately by email, on Telegram, and on WhatsApp where those are available — and you are shown which of them actually reached.
WhatsApp App — everyone in the workspace is asked once, on their next sign-in, whether they want to be reached on WhatsApp. The prompt greets them by name, explains that the workspace has installed WhatsApp notifications and support, and shows the QR code to scan to opt in. Their answer is saved either way, and the prompt can be limited to clients only in the App settings.
Photos, videos, voice notes and documents sent from WhatsApp are now downloaded in full and shown in the conversation, instead of only a small preview. Small files arrive with the message; larger ones follow within a minute, and anything that fails is retried.
The opt-in prompt now shows a confirmation code. Scanning the QR and sending it back confirms the number really belongs to that person, closes the prompt on their computer by itself, and files the number on their profile if there was none.
WhatsApp App — a new Opt-ins screen lists everyone who has been asked, with their answer, and everyone who has never been asked yet, so a newly registered person is visible before they first sign in. Administrators can put the question again to one person or to everyone who declined, and can lift a STOP for a client, team member or lead.
A WhatsApp tab on your own profile, next to Telegram's. Turn WhatsApp notifications on with the same QR code, confirmation ID and button as the first-time prompt, or turn them off again — so declining once, or replying STOP, is no longer final. It only appears on your own profile, never on a colleague's.
Confirming your number now also fills in your WhatsApp social link (wa.me) on your profile, if you had not set one yourself, and adopts your WhatsApp profile picture as your NIZU avatar when you do not already have one.
WhatsApp notifications: choose which workspace notifications are also sent over WhatsApp, the same way the Telegram Notifications App works. Each person receives them on their own number and only if they opted in, so switching an event on never messages somebody who has not agreed to it. An event that is switched off in Settings -> Notifications, or that has nobody set to receive it, is flagged on the list — it can never fire, whichever channel it is meant for.
WhatsApp notifications carry the details in the message itself, so they can be read without opening anything: a task shows its project, title, creator, points, priority, collaborators, owner, start date and deadline; a project its title and dates; a client its company and country.
The WhatsApp App is now available in all 13 workspace languages.
WhatsApp App — full in-app documentation: what it is, how to install it, how to use it day to day, best practices for keeping your number safe, which NIZU modules it connects to, and how it compares to other WhatsApp inbox tools.
One inbox for conversations from every channel. The Guests tab in Team Messenger now shows website chats, and in future WhatsApp and other channels, in a single list — each conversation marked with a small icon showing where it came from.
A new Groups tab in Team Messenger for group conversations, starting with your connected Telegram groups. It appears once you have at least one group.
Internal notes on a conversation. Notes are clearly marked, are only ever visible to your team, and never count towards a conversation's unread badge.
Conversations can be forwarded between team members, and every change of hands is recorded. Who wrote each message, and who was looking after the conversation at the time, stay correct no matter how often it is passed on.
A full-page version of the inbox, so a notification can link straight to a conversation and so the inbox is comfortable on a small screen.
Your WhatsApp numbers are now managed by the platform itself instead of by a single App. A number is linked once and every WhatsApp feature can use it.
Support for more than one WhatsApp provider at the same time. Each number remembers which service it uses, so a future number can run on a different provider without changing the numbers you already have.
Live Testing: a new dashboard widget shows every test cycle currently in progress, each with its progress bar, the number of testers on it, how long it has been running, a warning badge when cases have already failed, and a shortcut to its live race. It refreshes itself every 15 seconds.
Live Testing: four new counter widgets for the dashboard — test cycles in progress, test cycles passed, test cycles failed, and regressions detected (with the number still open beside it).
Live Testing: a new dashboard chart showing how many test cycles passed and how many failed per month over the last 12 months.
All Live Testing widgets are added from the dashboard's "Add widget" menu and are only offered to team members who have Live Testing access.
Knowledge Base & Help: every article now has a Share button — copy its link, send it by e-mail, or open it in a new tab.
Articles can be shared directly on LinkedIn, WhatsApp, Telegram and Facebook.
Telegram Notification App: a new "Send as Telegram notification" entry in the Share menu pushes the link of an article (or of any other shared item) to the workspace's Telegram chat.
Updates
Invoices: timesheet entries are now permanently marked once they have been invoiced, so the same hours can never be billed to a client a second time. Entries still running on a timer, and members without an hourly rate, are never picked up.
Invoices: deleting an invoice that was generated from timesheets releases those hours again, so the time is not lost with the invoice and can be re-invoiced.
Projects: the hourly rate and the invoicing actions are only visible to team members who are allowed to create invoices, and only on projects that belong to a client. Internal projects are unaffected.
The converted conversation is linked to the lead: the thread header shows the lead card, and the lead's page is one click away from the chat. A note in the thread records who converted it and when.
Converting to a lead is available to the team members who already work with leads — no new permission to configure. The button is shown on the Guests tab only, since a Support conversation is with a client you already know.
If the visitor's email address already belongs to another user, the lead is still created with everything else and you are told which detail could not be carried over.
The conversation inbox now serves three lists instead of two — Guests for anonymous website visitors, Groups for group chats, and Support for your identified client contacts.
Settings → AI: a switch to stop Marvin answering client conversations altogether. The conversations still reach the Support tab, so a person always answers them.
Existing WhatsApp conversations already matched to a client contact are moved into the Support tab by this update, rather than waiting to be re-linked by hand.
A WhatsApp message the platform sends to someone it already knows (a notification to a client or a team member) now opens a conversation properly identified as that person, with their client record linked.
Marvin → Telegram: you now choose who gets asked about Telegram notifications with three separate switches — Team members, Client contacts, and Guests / Leads — instead of one either/or choice. Any combination works, including asking nobody at all.
Your existing choice is carried over automatically: "Everybody" becomes Team members and Client contacts switched on.
The Guests / Leads switch is marked "Not reachable yet" — lead contacts cannot sign in to the workspace, so the prompt has no way to reach them for now. Your setting is remembered and will apply as soon as they can.
The Notification opt-ins screen now follows the same three switches, so the "Never asked" list only shows the people you are actually asking.
Marvin can now send your workspace notifications to your own Telegram chat. Everyone is asked once, with a short prompt in the app, and nothing is ever sent to someone who has not said yes.
The prompt doubles as the way in for anyone who has not connected Telegram yet: it shows a QR code to scan with your phone, plus an "Open in Telegram" button. Opening it connects your account and turns your notifications on in one step.
New screen (Marvin → Notification opt-ins) listing who was asked and what they answered, filtered by tabs: all, accepted, declined, asked, never asked, and — most usefully — the people who said yes but never connected Telegram, so nothing can reach them.
Administrators can put the question to somebody again, or to everyone who declined at once.
New screen (Marvin → Telegram notifications) to choose which notification events are also sent on Telegram. Events that are switched off, or that have nobody to notify, are flagged so a switch never looks armed when it can never fire.
Your profile's Telegram tab now carries a switch to turn workspace notifications on or off yourself, at any time.
Marvin settings now let you decide who sees the Telegram prompt — everybody, team members only, or client contacts only — and let you switch the prompt off entirely.
Notifications sent on Telegram carry an "Open" button that takes you straight to the invoice, task or project they are about.
The emoji picker is now shared between the Team Messenger composer and the omnichannel conversation panes, so both behave identically and remember the same frequently-used emojis.
A reaction, a quote or an attachment that a channel cannot deliver no longer fails the message: it is sent without that extra rather than not at all.
WhatsApp App settings gained two switches: ask existing users to opt in, and notify team members on WhatsApp when a conversation is forwarded to them.
A phone number that merely matches a contact record is now clearly labelled as unconfirmed. Only a person proving it, or a staff member linking them by hand, counts as confirmed.
WhatsApp App — the warm-up daily limit is now a setting instead of a fixed 20 messages a day.
WhatsApp App settings moved to Settings -> Apps, alongside Telegram's, so the sidebar keeps only the screens used day to day: Numbers, Contacts, Opt-ins and the Activity log.
Opt-in answers are kept in their own table rather than as one row per person in the workspace settings, which every page load had to read through. Existing answers are moved across automatically.
WhatsApp App settings no longer ask for the provider's API address. It ships with the App, and if the provider ever moves it arrives with a platform update — there is nothing for an administrator to keep correct, and no longer a field that can silently break sending.
WhatsApp App settings were redesigned: options are now grouped into titled cards — connection, sending and limits, notifications, opt-ins — with on/off switches instead of plain checkboxes, so the page can be scanned instead of read from top to bottom. It follows dark mode and works on a phone.
Website chat conversations and Telegram groups from the Marvin App have been moved into the shared inbox. All of your existing conversations, messages, notes and support-ticket links are carried over and continue to work exactly as before.
The Guests tab is now part of the platform rather than the Marvin App, so it no longer disappears if that App is turned off.
Replies written by the assistant are now recorded against it in the same way a team member's replies are, so "who replied" filters and per-person reporting include them.
Conversation lists can be filtered by where the conversation came from, alongside the existing Active / Closed / Ticketed filters.
WhatsApp Channels now reads its linked numbers from the shared list. Your existing numbers, sessions and QR links are carried over automatically and keep working — nothing needs to be scanned again.
OrderLemon broadcasts now use the same shared WhatsApp connection as WhatsApp Channels, so a token saved in one place works everywhere.
Numbers carried over from WhatsApp Channels stay marked for broadcasting only, and keep their unlimited daily sending. Nothing about how they send today changes.
Each WhatsApp number can now record who holds the phone, a daily sending limit and what it is used for. These are preparation for the upcoming WhatsApp conversations App and are optional today.
Subscriptions: the list can now be filtered by Type (App, Stripe, Metered, Mollie) and by Status (Draft, Pending, Active, Cancelled), on top of the existing currency, repeat type and next billing date filters.
Subscriptions: Mollie subscriptions now show a proper "Mollie" label in the Type column instead of an untranslated placeholder.
Live Testing: the app documentation now covers the dashboard widgets, and the new widget labels are translated into all 13 supported languages.
The Share menu used across the app (projects, tasks, clients, invoices, …) can now show social network destinations where it makes sense.
Fix
Knowledge Base: importing a Postman collection no longer stops silently. A collection folder named with a word such as "update", "delete" or "table" — for example "8. Menu update" — ended the import halfway with no message, so the preview stayed empty and no articles were created. Folder names of any wording are now accepted.
Knowledge Base: a Postman collection where several requests share the same method and address — typical of webhook collections, where every event is posted to the same URL — now creates one article per request instead of folding them all into a single one. Re-importing the same collection still updates those articles rather than duplicating them.
Conversation inbox: internal notes added to a conversation are visible again in the thread. They were being saved but never shown, so a note written for a colleague could not be read by anyone — including the person who wrote it. Notes remain staff-only and are never sent to the contact.
A client asking the assistant for help no longer disappears into a conversation nobody on the team can read or answer.
Team Messenger: the conversation list no longer stops half way down the panel when the messenger is opened. The list now fills the window from the first moment, on any screen size, and follows the window as it is resized, dragged to full screen or as the reply box grows.
Team Messenger and the Inbox showed raw labels such as inbox_guests, inbox_groups or inbox_filter_active instead of real words in Turkish, Spanish, French, German, Dutch, Italian, Portuguese, Polish, Czech, Russian, Greek and Norwegian. The whole conversation panel is now translated in every language: the Guests and Groups tabs, the Active/Closed/Ticketed filters, conversation statuses, internal notes, attachments and voice messages, forwarding to a team member, and the linked-person panel.
The Share menu (share a project, task, client, lead, invoice, order, subscription, estimate, proposal, ticket, report or article) was untranslated outside English and now shows proper text in all languages.
The client impersonation feature (open a session as a client's user to verify the client portal) showed untranslated labels, confirmations and error messages outside English.
The Knowledge Base show/hide sub categories option was untranslated outside English.
The Gamify App was only available in English, Dutch and French; every other language showed raw labels such as gamify_leaderboard across the Arcade, the leaderboard, trophies, the XP ledger, the NIZU Office world, the duels and the App settings. Gamify is now fully translated in Spanish, German, Italian, Portuguese, Polish, Czech, Russian, Greek, Norwegian and Turkish.
Notification opt-ins: the "Never asked" tab showed an error and stopped loading in workspaces with more than 200 people, and also listed everybody who had already answered.
Notification opt-ins: the "All" tab counter showed far fewer people than the list beneath it.
Marvin settings: switching the Telegram bot off did not stick — the setting could only ever be turned on.
Deprecated
The Marvin App keeps its own copy of website chats and Telegram groups for one more release so nothing is lost during the changeover. Those copies are no longer read and will be removed in a later version.
The WhatsApp Channels App keeps its own copy of your numbers for one more release so nothing is lost during the changeover. That copy is no longer read and will be removed in a later version.