What's New: March 2026

Copilot: Conversation history and reasoning visibility

• Conversation history is now generally available (previously preview). Users can reopen and continue past Copilot chats via the “triple dots” menu, including across days. 

• Visible reasoning / thinking view is now supported (preview) for both fast and deep-thinking modes, letting users see how Copilot is working through complex prompts.

• Copilot makes it easy to understand observability issues. As part of the customer’s daily briefing/report, it is now possible to ask which tickets failed to sync. Here’s an example:

  

Financial Impacts Dashboard: Quantify achieved and potential savings

• Introduction of a new Financial Impacts Dashboard, replacing the older version. Breaks value into:

  • Achieved savings vs Potential savings
  • Direct savings (energy, maintenance)
  • Cost avoidance (risk, downtime, safety, compliance)
  • Continuous coverage (total insured value of deployed skills)

  Added plain-language descriptions explaining how each impact score is calculated. Designed explicitly to support sales and value conversations with customers and finance stakeholders.

  

Dashboards: Automatic unit scaling and internationalisation

• Automatic unit scaling and K/M notation across all dashboards (e.g., kWh → MWh, K/M/B values).
• Improved handling of metric vs imperial units, including better decimal precision (notably for Celsius).
• App preference added to choose temperature units for homepage weather, with plans to extend globally.

Bi-directional ticket sync: Customer-specific status and priority mapping

• Ticket statuses and priorities now sync directly from customer source systems instead of being forced into Willow-defined values. 
• Customer-specific workflows are preserved, including valid state transitions.
• Still mapped into Willow tabs for consistency, but without mutating customer data.

Activate & scenarios updates

• Scenario recommendations are now directly tied into the diagnostic checks using the knowledge graph, making them clearer and more relevant.
• Scenarios include clearer guidance (like expected ranges) to explain why something needs attention.
• Scenario prioritization has been improved with Critical / High / Medium / Low levels instead of everything being urgent. 
• Scenarios can now be marked as completed, allowing dashboards and KPIs to reflect real progress. Errors behind the scenes are easier to understand and quicker to resolve, reducing delays and friction.