Can Darcy explain what changed between service versions?

Yes. Darcy can turn saved service-version differences into a readable explanation of what changed and what your team should review before release.

Ask it to compare two saved versions, explain a page's recent changes or identify changes since the version recorded as deployed to QA or Production.

Make release review easier

• Understand the journey impact. Identify changes to questions, wording, conditional routes and review steps.
• Check operational behaviour. Focus on validation, calculations, actions, notifications or generated documents.
• Compare with an environment. See how the current saved Builder service differs from the recorded deployed snapshot.
• Plan focused testing. Use the explanation to identify affected routes and integration outcomes.

For example, ask “Compare the current saved service with Production and highlight changes to questions, routing and notifications”. Include a date, author or environment if a version label is ambiguous.

Keep the comparison in context

The comparison is read-only: it does not edit, restore or deploy the service. It compares saved states, so unsaved conversation edits are outside that review. Recorded deployment information identifies published snapshots; it is not a live service-health check.

Use Change management if you decide to restore a version, then test the resulting service. Missing historical definitions or an incomplete comparison should be resolved before treating an explanation as a complete review.

See Explain differences between service versions and Service change management.