Purpose
Beta and Preview Programs allow selected agencies to test new functionality before it is released broadly across the platform. These programs help identify workflow improvements, usability concerns, operational impacts, and enhancement opportunities using real-world agency scenarios.
If you would like to be part of a future Beta preview, please reachout to our Support Team.
When Should You Provide Feedback?
Feedback should be submitted:
After using the feature in a real workflow
When something feels confusing or inefficient
When a workflow requires unnecessary clicks or workarounds
When expected functionality is missing
When the feature improves efficiency or visibility
When you encounter unexpected behavior or system inconsistencies
Recommended Timing
Provide feedback:
During active use of the feature
Shortly after completing a workflow
Before the end of the beta period
Early feedback allows improvements to be evaluated before global release.
Before You Begin
Prerequisites
Before submitting feedback:
Confirm your agency has access to the beta or preview feature
Ensure users testing the feature have appropriate permissions
Use the feature within normal day-to-day workflows whenever possible
Gather examples, screenshots, or scenarios that illustrate your experience
How to Submit Effective Feedback
The most helpful feedback explains:
What you were trying to accomplish
What happened
What you expected instead
The operational impact on your agency
Instructions
Step 1: Use the Feature in a Real Workflow
Use the feature during normal operations whenever possible.
Examples may include:
Scheduling caregivers
Managing client visits
Reviewing billing workflows
Handling EVV-related tasks
Reviewing compliance workflows
Updating client or caregiver information
Avoid testing only with “perfect” scenarios. Real-world workflows often uncover the most valuable insights.
Step 2: Evaluate the Workflow Experience
As you use the feature, consider the following questions:
Workflow Questions
Did the feature fit naturally into your workflow?
Were there unnecessary clicks or extra steps?
Did users know what to do next?
Did the feature save time or reduce manual work?
Were any actions confusing or difficult to locate?
User Experience Questions
Was the screen easy to understand?
Was important information easy to find?
Were buttons, labels, or alerts clear?
Did anything feel cluttered or overwhelming?
Operational Questions
Did the feature improve visibility or efficiency?
Did you encounter any billing, scheduling, or compliance concerns?
Would you trust this feature during busy operational periods?
Step 3: Document Issues or Suggestions
When providing feedback, include as much detail as possible.
Helpful details include:
The user role involved
The workflow being completed
Specific screens or actions involved
Any error messages received
Screenshots or screen recordings
Recommended Feedback Format
What We Were Trying to Do
Describe the task or workflow.
What Happened
Describe the system behavior.
What We Expected
Describe the expected result.
Operational Impact
Explain how this affects scheduling, billing, compliance, caregivers, or office staff.
Suggested Improvement (Optional)
Provide recommendations if applicable.
Best Practice Recommendations
Recommended Practices
Use Multiple Roles During Testing
Whenever possible, involve:
Schedulers
Coordinators
Billing staff
Administrators
Clinical staff
Different users may experience workflows differently.
Test Real Scenarios
Use realistic schedules, clients, caregivers, and authorizations whenever possible.
Submit Feedback Early
Early feedback provides more opportunity for adjustments before release.
Include Positive Feedback
Knowing what works well is just as valuable as identifying issues.
Examples:
Time savings
Reduced manual work
Better visibility
Easier communication
Improved accuracy
Common Feedback Scenarios
Scenario: Workflow Requires Too Many Steps
Example Feedback
“Schedulers needed to open three separate screens to complete a task that normally takes one step.”
Why This Helps
This identifies workflow inefficiency and usability concerns.
Scenario: Important Information Is Difficult to Find
Example Feedback
“Authorization balances were not visible while scheduling visits.”
Why This Helps
This identifies visibility and operational workflow gaps.
Scenario: Unexpected System Behavior
Example Feedback
“The visit appeared approved, but payroll hours did not update correctly.”
Why This Helps
This helps identify reliability or downstream workflow issues.
Scenario: Feature Adds Significant Value
Example Feedback
“The feature reduced scheduling time and made open shifts easier to identify.”
Why This Helps
Positive operational impact helps prioritize feature development.
Troubleshooting
I’m Not Sure Whether Something Is a Bug or Feedback
Submit it anyway.
Beta programs are intended to identify:
Bugs
Workflow concerns
Missing functionality
UI/UX improvements
Operational risks
Enhancement opportunities
I Cannot Access the Feature
Possible causes:
User permissions are missing
Beta access has not been enabled for your agency
The feature is limited to specific roles or offices
Contact your agency administrator or Support team for assistance.
The Feature Behaves Differently Than Expected
When reporting the issue, include:
Steps performed
Expected behavior
Actual behavior
Screenshots or recordings if available