Changelog

A new look for Wappline

A visual refresh across the product and the public site, with a new brand mark and a green accent.

Added

• A new Wappline mark and favicon, and a new preview image when someone shares a link to Wappline.
• Redesigned home, feature, solution and guide pages, plus new sign-in and registration screens.
• Redesigned emails, error pages and legal pages that match the rest of the product.

Improved

• A refreshed interface inside the product, with consistent tables, forms, dialogs and notifications.
• Pages load faster on repeat visits: static files are cached by the browser, and fonts are served from Wappline instead of an external font service.

Security, reliability and data controls

A broad update that protects channel credentials and webhooks more strongly, makes campaigns and automations more reliable, and gives you clearer control over your data.

Added

• Every webhook endpoint keeps a delivery history with the status, timing and error of each attempt, and you can send a test event from the channel's webhook settings.
• Endpoints that keep failing are paused automatically after repeated failed deliveries, and you can resume them yourself.
• Webhook secrets can be rotated without downtime: for 24 hours after a rotation, deliveries carry a second signature made with the previous secret.
• Deleting a user account or a whole company account starts a 3-day waiting period in which you can cancel, and a reminder email arrives 24 hours before the deadline.
• Data-deletion requests from Meta are handled automatically, with a confirmation code and a public status page.
• Forms can email your company administrators when a new submission arrives.

Improved

• Campaigns are built for large audiences: sending is paced for each channel, an interrupted campaign continues where it stopped, and a failed message is retried or stopped depending on the kind of error Meta reports.
• Automations can wait for a delay or for a customer's reply and continue afterwards, and long waits no longer occupy a worker.
• The dashboard and reports are built from hourly summaries of your message counts, so long date ranges open faster.
• The conversation list shows the delivery status of the last message you sent, and reactions to messages appear in the conversation.
• Incoming media is downloaded in the background, so messages arrive without waiting for large files.
• Channels above your plan limit are frozen instead of deleted. They keep their data, are marked on the plan page and become active again when you upgrade or add channels.

Security

• Telegram channels now verify incoming updates with a secret of their own, existing channels were moved to the new address automatically, and Telegram bot tokens are stored encrypted.
• API keys that you connect for automation steps are stored encrypted in a company credential store instead of inside the automation.
• Webhook triggers of automations can be protected with a secret: when one is set, a request must carry a matching signature of its body.
• Requests from Bitrix24 are checked against the application token stored for your portal, and a request with a wrong token is rejected.
• An audit log records privileged actions such as plan changes and API token rotations.