April product updates

 Better control, more reliable results

This month’s updates are focused on one thing: giving you more confidence in your tests.

We’ve introduced improvements to give you more control over your data, prevent avoidable testing issues, and improve visibility and clarity within the dashboard experience.

Here’s what’s new.

📑 In this update

• Expanded admin controls for test data and results
• Alexa virtual device conflict prevention
• Improved DTMF feedback and input visibility

🛠️ Expanded admin controls

We’ve expanded admin capabilities to give teams more control over how test data is managed and interpreted.

This is especially useful during setup, iteration, and experimentation.

What’s new

Admins can now:

• Delete test executions to remove invalid or setup-related runs
• Manually update test or test run results
• Add context to any changes with notes
• See a full audit trail (who made the change and when)

Modified results are marked with a yellow asterisk in the dashboard for visibility.

These actions are only available to admins, helping maintain consistency and control of your data.

Why this matters

Testing isn’t always linear. With these updates, teams can:

• Keep dashboards clean and meaningful
• Avoid skewed metrics from failed setup runs
• Handle intentional or edge-case scenarios
• Maintain transparency across changes

Note: Deleting executions is permanent and will recalculate overall statistics.

🧠 No more conflicting Alexa tests

Alexa virtual devices behave like real users — they can only handle one interaction at a time.

Previously, running multiple tests simultaneously on the same device could result in failed or incomplete responses.

What’s new

If a virtual device is already running a test, you’ll now see a:

→ “Device in use” message

You can then wait or choose a different device.

Why this matters

This simple safeguard helps:

• Prevent conflicting executions
• Reduce false negatives
• Avoid unnecessary debugging

🔊 More realistic IVR testing with DTMF feedback

When testing IVR flows, sending DTMF inputs (using $ + number) now includes audible keypad tones.

We’ve also improved how inputs are displayed in the dashboard:

• DTMF inputs (e.g. $1) are now highlighted in blue and bold
• API variables (e.g. ${API_VARIABLE}) are highlighted in green

Why this matters

Previously, digits were sent — but without sound, it could feel like nothing was happening, and inputs could be harder to scan visually.

Now:

• Tests feel more realistic
• Inputs are easier to identify at a glance
• You gain more clarity when reviewing test steps

🤓 TL;DR

Faster insights, cleaner data, fewer testing headaches:

• Admins can manage and clean test data
• Alexa conflicts are prevented
• DTMF inputs now include audio feedback
• Inputs are easier to read with improved visual highlighting

If you're looking to improve your conversational AI quality with automated testing and monitoring —

👉 Book a demo or start testing with Bespoken AI today.