What’s new in WBSender

Highlights

• Only accounts without an active subscription, after 7 idle days
• Accounts with an active subscription are never affected
• First run 18:00 UTC on 22 October: 12 linked numbers, about 515 MB
• Coming back later means scanning the QR code once

Highlights

• Busiest linked number: 3,036 MB down to 892 MB
• A number that would not finish loading now connects in 18.7 to 25.2 seconds
• Photos, videos, audio and documents are no longer downloaded on our server
• Connected numbers are cleaned every 6 hours without a restart
• Login data untouched, no QR scan needed

Highlights

• No content check on every typing pause in the single-response editor
• Reply editors readable in dark mode
• Contacts in the sidebar opens All Contacts and Tags

Highlights

• New Tags page under Contacts
• Rename a tag without breaking filters, campaigns or automations
• Merge two tags into one
• Deleted tags can be restored with their contacts
• Renaming a WhatsApp label tag no longer creates a duplicate on the next sync

Highlights

• Four unused browser downloads removed, 1,235 MB in total
• Disk in use went from 23.9 GB to 22.7 GB
• None of them had been opened in the last 30 days
• No restart, and the number that was online stayed online
• WhatsApp login data was not touched

Highlights

• Nine days up since the planned restart, with no memory problems
• The nightly database backup completed on each of the last three nights we checked
• Disk use is down to 24 GB from 57 GB at the start of the month
• Pending system updates applied, no restart needed
• Browser cache cleared for numbers that were offline, with no number logged out

Highlights

• Five leftover test databases removed, each backed up first
• The server now holds one application database, the live one
• Your data was not touched: the live database had the same 144,200 contacts before and after
• The database log folder went from 790 MB to under 5 MB
• The record of who signed in to the database was kept before the old log was removed

Highlights

• The application has its own database login, limited to WBSender's own data
• That login cannot read the list of database users, create accounts or touch any other database
• The administrator password was changed, and the old one stopped working immediately
• An administrator account unused since June 2025 was removed
• Tested before the switch, including the nightly backup

Highlights

• A page of contacts now reads 20 records instead of all 144,200
• The same contact query went from 73 ms to 8 ms on an idle server, and the slowest ones in the log had taken over 3 seconds
• Activity logs went from 253 ms to 1 ms
• Looking a contact up by phone number is answered straight from the index
• Added live, with no downtime and no change to your data

Highlights

• Pending operating system updates applied, no restart needed
• The browser behind WhatsApp sessions kept on its tested version on purpose
• No linked number was disconnected and nothing had to be rescanned

Highlights

• The API is now reachable only over HTTPS, not through its internal ports
• Entry points that nothing was using have been closed
• The database now only accepts connections from our team's network
• Checked first that the dashboard and connected services only use the secure address, so nothing broke

Highlights

• The database log is rotated every day instead of growing in one file
• Older days are compressed and anything past 14 days is removed
• The 31 GB log that had built up was compressed to 786 MB, about 2.5 percent of its size
• About 30 GB freed: disk use went from 55 GB (29 percent) to 25 GB (13 percent)
• Done with no restart and no interruption to sending or the dashboard

Highlights

• An email alert goes to our team when a nightly backup fails after every retry
• A skipped backup raises the same alert, so a setting removed by mistake cannot go unnoticed
• A temporary problem that the hourly retry fixes does not cause a false alarm
• The alert says what went wrong and how to take a snapshot by hand

Highlights

• A full snapshot of the database is taken every night at 03:00 Bangladesh time
• Snapshots are encrypted and stored off the server, in private cloud storage
• 30 days of history are kept, and the 7 most recent are never removed
• Every snapshot is checked after upload, so a broken copy is never counted as a good backup
• The first snapshot was taken on 5 October and checked against the original

Highlights

• The content check no longer calls an AI model that has been retired
• Browser cache for each linked number is capped at 100 MB

Highlights

• Operating system, OpenSSL, Linux kernel and MongoDB security updates installed
• A full database backup was taken and checked against the live data before the update
• The service now starts by itself after a server restart
• 2.2 GB of old browser cache cleared without logging any number out
• Server login is key only, and repeated failed login attempts are blocked automatically
• Application logs now rotate by themselves instead of growing forever

Highlights

• A date range picker on the delivery report, with presets and a two month calendar
• Presets for the last 7 days, 14 days, last month, 3 months, 12 months, month to date and all time
• Pick any custom start and end date, with a live preview of the range as you move across the calendar
• The delivered and failed totals now count only the range you picked
• Short ranges plot day by day, longer ranges plot month by month, in your own timezone

Highlights

• The two switched-off reply routes now carry the same fix as everything else
• Every place the product attaches a file was audited — twelve in all, none left exposed
• Campaign, single-send and group attachments confirmed working after this morning's fix
• No action needed and no re-scan required; this changes nothing you can see today

Highlights

• Images, albums, voice notes, videos and documents send again
• An auto-reply with a picture no longer arrives as bare text
• Campaign, single-send and group attachments are covered by the same fix
• Already-linked numbers picked the fix up without re-scanning a QR code
• Delivery and seen ticks update again for media that WhatsApp acknowledged late

Highlights

• A reply rule can send an ordered sequence of steps instead of one fixed message, mixing text, images, an album, a video, a voice note and a document
• Existing single-response rules are unaffected — the new fields are additive, nothing about how they send has changed
• The response builder and the rule detail page were redesigned around a shared, color-coded timeline layout, fully responsive
• Fixed a typing freeze in the rich-text editor used across auto-reply, templates and message composition, triggered by having more than one editor on a page at once
• Switching a rule between single and multi-step mode now clears the mode you're leaving instead of leaving its old data behind unseen