Changelog

ReferenceUpdated 2026-08-05

Notable platform changes, newest first, grouped by month. Breaking changes are emailed to instance owners ahead of release in addition to appearing here.

2026-08

2026-07

  • Added: Documentation system launched at /docs, with full-text search across the docs index.
  • Added: Retention policies can now be set separately for voice call recordings.
  • Changed: Ping Me device fleet view now shows last-seen connectivity per device, not just per instance.
  • Fixed: WhatsApp template category was occasionally mislabelled in the console after Meta re-review.

2026-06

  • Added: Ping Me device fleet view added to the console with connectivity alerting.
  • Changed: Campaign consent filtering moved to execution time rather than at build time, so consent withdrawn after a campaign was scheduled is respected.
  • Changed: Billing portal (client.arino.one) now itemises Ping Me button-press and talk-minute charges separately.
  • Fixed: RCS sender verification status could show as pending after approval; status now refreshes on load.

2026-05

  • Added: RCS agent onboarding made available in additional EU markets.
  • Added: Audit log export extended to cover template submissions and approvals.
  • Changed: Quality rating warnings now surface in the console at yellow, not only at red.
  • Fixed: Erasure requests submitted via the API were not always reflected in the audit trail.

2026-04

  • Added: Voice/WebRTC minute usage now visible in near real time in the usage dashboard.
  • Changed: Instance connection and management fee invoicing moved to a fixed monthly date rather than anniversary billing.
  • Fixed: Live web chat widget occasionally failed to reconnect after a network drop on mobile browsers.

2026-03

  • Added: Segment builder in the CDP now supports consent-state as a filterable attribute.
  • Changed: Connected instances can now request Infobip throughput increases directly through Arino support without sharing their API keys.
  • Fixed: Message template rejection reasons from Meta were sometimes truncated in the console notice.

2026-02

  • Added: Support for additional sender registration per WABA, raising the practical cap for multi-brand accounts.
  • Fixed: Delivery receipts for RCS were occasionally delayed behind WhatsApp receipts in the same batch.

2026-01

  • Added: Instagram and Messenger channel overviews added alongside existing channel documentation.
  • Changed: Setup fee billing now distinguishes verified-Meta-Business-Manager cases from Arino-assisted verification cases on the invoice.
  • Fixed: QR opt-in codes generated before December 2025 could fail to resolve after a console update; all affected codes were regenerated automatically.

2025-12

  • Added: Consent and opt-in records now display the exact wording shown to the contact at the time of capture, not just the current template text.
  • Changed: The console now surfaces Infobip account-level rate limit warnings directly, rather than only via email.
  • Fixed: Campaign scheduling occasionally used the instance's default region time zone instead of the console user's selected time zone.

2025-11

  • Added: Voice/WebRTC call recording retention can now be configured independently per instance region to align with local rules.
  • Fixed: Ping Me device registration failed silently if the device firmware was more than two versions behind; registration now blocks with a clear firmware-update prompt.

2025-10

  • Added: Erasure request workflow now generates a downloadable evidence bundle for audit purposes on completion.
  • Changed: Template rejection notices now link directly to the relevant Meta policy category.
  • Fixed: SMS fallback for undelivered WhatsApp messages occasionally fired twice for the same contact within a single campaign run.

2025-09

  • Added: User roles reference updated with a new read-only auditor role, available on all instances.
  • Fixed: Live web chat unread-count badge occasionally failed to clear after a conversation was marked resolved.

Frequently asked

Are breaking changes announced in advance?

Yes. Any change that could affect an existing integration or workflow is emailed to instance owners ahead of release, in addition to being listed here.

Does this changelog cover unconnected instances too?

It covers changes to the Arino One template, console and Arino Core infrastructure. Unconnected instances (no active $50/month Arino Core connection) only receive template updates if the client pulls them in themselves.

How often is the changelog updated?

Roughly monthly, grouped by the month a change shipped, though minor fixes are sometimes batched into the following month's entry.

Where do I report a bug that isn't listed here?

Raise it through support; confirmed fixes are added to the next changelog entry once released.

Next step

Apply this to your own deployment

This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.