WISPGate Release Notes
Platform Updates & Changelog
Resource Page / Release Notes

Release Notes.

A premium release stream that shows what changed, why it matters, and what operators need to watch before rollout.

Review detailed release highlights, fixes, operational impact, upgrade notes, and rollout guidance for every WISPGate version update.

Open Release Structure Jump to Inner Release
1
Release Hub
1
Inner Release Page
5
Update Categories
0
Changelog Clutter
What this page must do

It must inform, signal maturity, and reduce upgrade anxiety.

A release page is not just a list of commits. It is a trust surface. Presenting changes clearly ensures smooth operations and secure platform upgrades.

Release archiveClean timeline of major versions and product improvements
Inner pageDeep release breakdown with impact and upgrade guidance
01. Release landing/archive 02. Detailed release page 03. Change categories 04. Upgrade & rollout notes
Release
Control
Center
Features
Fixes
Upgrade Notes
Known Issues
Security & API

Release-notes landing page

This is the archive and index for product updates. It emphasizes the latest important releases, groups notes by version, and helps customers identify what matters.

Release Hub Inner Release Changes Upgrade Notes
Page 01 / Release Archive

A product update stream that feels controlled, not chaotic.

The landing page spotlights the latest major release, shows recent release history, and categorizes changes clearly so users can scan for new features, fixes, billing changes, API updates, and operational risks.

Archive & Latest Release Layout
Latest spotlight

Feature release highlight

The top section shows the newest important release with a summary, impact statement, and direct link to full notes.

Archive timeline

Chronological browsing

Browse by version, quarter, or month without turning the page into an endless dump of minor changes.

Filter by concern

Scan by category

Features, fixes, API, security, billing, known issues, and upgrade-impact items are visually distinct.

Featured Release

WISPGate 2.4 — Billing Intelligence, dispatch workflow refinements, and API consistency improvements

This release combines improvements across billing visibility, field operations, and API behavior while introducing safer rollout notes and clarified upgrade steps for live environments.

Major Enhancements Billing Dispatch API
Apr 2026
Previous Release

WISPGate 2.3 — ONU workflow polish, alerting cleanup, customer-portal fixes

A stability-focused release with device workflow cleanup and reduced UI friction.

Mar 2026
Previous Release

WISPGate 2.2 — Multi-gateway payment sync and collections rule improvements

Expanded finance automation and stricter payment-state handling.

Feb 2026
Landing section 01

Latest release spotlight

Show the top release with summary, impact, and CTA into full notes.
Landing section 02

Recent archive list

Keep the latest releases easy to scan with category tags and dates.
Landing section 03

Filter by change type

Let users isolate billing, API, bug fixes, security, or upgrade-impact notes fast.
Page 02 / Detailed Release Page

Template example: WISPGate 2.4 release note.

This is the inner page your users open from the archive. It explains the operational value, rollout implications, and any risks or upgrade steps the customer needs to know before they touch production.

Inner Release Template / Example
Release 2.4

WISPGate 2.4 — Stronger billing visibility, cleaner dispatch operations, and more predictable API responses

This release is positioned as a control and consistency update. It introduces better billing-intelligence presentation, operational improvements in field-dispatch handling, and cleaner API response normalization to reduce integration friction.

Features
08

New features and functional enhancements worth surfacing to users.

Fixes
14

Bug fixes and stability improvements affecting production usability.

Upgrade Impact
Low–Med

Minor operational caution areas, but not a full migration-grade change.

Highlight 01

Billing intelligence widgets

Introduced clearer visibility for receivables, overdue balances, and collection-state tracking in dashboard and account views.

Highlight 02

Dispatch workflow refinements

Improved technician assignment visibility, schedule state clarity, and completion-state handoff between ops and support.

Highlight 03

API response normalization

Made selected endpoint responses more consistent to reduce custom parsing work and client-side guesswork.

F
Feature

New billing-intelligence summary layer

Added receivables, aging, and collection-state summaries to improve operator awareness of commercial risk.

U
UI / UX

Cleaner work-order state transitions

Refined labels and visibility around scheduled, in-progress, blocked, and completed dispatch tasks.

A
API

Normalized success and error envelopes for selected endpoints

Reduced inconsistency in response shape for key subscriber and billing actions.

B
Bug Fix

Fixed edge-case invoice display mismatch in account summary view

Resolved a UI inconsistency where recent invoice state did not immediately reflect backend updates in some scenarios.

S
Stability

Reduced duplicate notification behavior in selected reminder flows

Improved event handling to reduce repeated communication under specific retry conditions.

Upgrade path

1

Review scope

Check release categories that affect your deployment: billing, API, dispatch, notifications.

→
2

Validate customizations

Verify dashboards, workflow assumptions, and external integrations against changed behaviors.

→
3

Roll out safely

Apply in staging first, test critical flows, then move to production with rollback awareness.

Known issues
  • Some legacy custom dashboard tiles may require visual adjustment after enabling new billing widgets.
  • Certain older API clients may rely on inconsistent legacy response assumptions and should be regression-tested.
  • Installations with heavily customized dispatch terminology may require minor UI label review.
Rollout guidance
  • Test one billing-heavy account flow before full rollout.
  • Validate dispatch board states with support and field teams together, not in isolation.
  • Regression-test client applications consuming normalized API responses.
  • Communicate visible UI changes to internal teams before go-live.
# Example internal release summary block Release: WISPGate 2.4 Focus: Billing Intelligence / Dispatch Workflow / API Consistency Risk Level: Low to Medium Recommended Environment Path: Staging → Targeted Validation → Production Must-Test Areas: Dashboard tiles, invoice visibility, reminder flows, API clients Rollback Consideration: UI/config rollback only unless custom integrations are affected