Resolution Statement
As part of our analytics infrastructure upgrade and rollout, your Compliance Report is now powered by our centralised data warehouse, the same single data source that drives all of your Voyc reports and dashboards.
As part of this move, we have also resolved an issue with how unscored calls were being handled in the report. Previously, unscored calls were surfacing in a way that affected your pass and fail rates, making them appear inconsistent or incorrect. They are now clearly identified as unscored and remain visible in your report, but are excluded from pass and fail rate calculations entirely. The rates you see now reflect only calls that were actually scored, giving you a more accurate and trustworthy picture of your compliance position.
No action is required on your side. If anything still does not look right, please reach out to Technical Success and we will look into it with you.
Resolution Statement
As part of our ongoing analytics infrastructure upgrade, your Alerts dashboard is now powered by our centralised data warehouse, the same single data source that drives all of your Voyc reports and dashboards.
This upgrade resolves the inconsistencies that some customers experienced on the Alerts dashboard, where certain metrics were not reflecting the correct figures. With all dashboards now drawing from one consistent, governed data source, the figures you see on your Alerts dashboard will be accurate and aligned with the rest of your reporting.
No action is required on your side. If anything still does not look right, please reach out to Technical Success and we will look into it with you.
Testing has confirmed that rescoring affected conversations correctly applies the configured routing attributes, and new calls are no longer impacted by this issue.
If you would like affected conversations to be rescored, please contact support@voyc.ai and provide the relevant date range along with your rescore request. Our team will be happy to assist.
Thank you for your patience while we worked to resolve this issue.
The issue was resolved as of 9/6, and alerts for 5 - 7 June on affected calls were re-ran successfully.