Your feedback shapes what we build during the alpha. This page explains what helps us most, what to expect from the program, and how to send feedback.
What feedback is most valuable to us during Alpha testing
Not all feedback is equal at this stage. Here's what helps us most right now:
Workflow friction: Where did the product slow you down or force a workaround? What took more clicks than it should have? What felt unintuitive the first time you tried it?
Missing basics: Are there things you do every day in your current tool that StaffingManager simply doesn't support yet? We want to know what's blocking you from using this as your primary system.
Broken behavior: Anything that behaves unexpectedly, errors out, loses data, or produces a result that doesn't make sense.
What's working well: Genuinely useful to know. If something clicked immediately or made a task faster, tell us — we want to protect what's working as we iterate.
We're less focused on visual polish, color preferences, or feature requests for things outside the current scope. Save those for later — right now, workflow and reliability matter most.
Timeline and what comes next
|
Phase |
What's happening |
|---|---|
|
Alpha (now) |
Closed testing with a select group. Core workflows only. High feedback cadence. |
|
Beta |
Broader access, more features in scope, stability improvements from alpha learnings. |
|
General availability |
Full public release with onboarding, support documentation, and pricing. |
We don't have fixed dates to share for beta and GA yet — those timelines depend on what we learn during this alpha. What we can commit to: we'll communicate changes to the program directly with you before they happen, and you'll be first in line for beta access.
How this differs from the production release
The alpha is not a finished product. Here's what that means practically:
-
Features may change or disappear. If something works one week and is gone the next, we made a deliberate change — not a mistake. We'll communicate significant changes, but not every iteration.
-
Performance isn't optimized yet. Some things may be slower than they'll be in production. We haven't tuned for scale.
-
Data may be reset. In rare cases, we may need to reset or migrate data between alpha builds. We'll warn you in advance when possible.
-
You have direct access to us. In production, support goes through a ticketing system. Right now, you can reach us directly. Use that.
Service Level expectations during alpha
Keep in mind that the alpha release is not a supported production environment, as a result:
-
Know that we will respond to critical issues as quickly as possible.
-
Use the Feedback button in StaffingManager to go to our Support portal and start any kind of service request. You will receive a system-generated response from our Jira support desk.
-
We will respond to all submissions within two days.
-
Do not run your organization's live operations on the alpha release, and keep your current tools as a backup for now.
How to submit feedback
The quickest way is the Feedback button at the top of every StaffingManager screen. Select the type of feedback from the list and enter your comments.
You can also:
-
Use the Support portal to report a bug or start any other request
-
Send us an email: support@staffingmanager.co