Trust
Could you explain the answer and source data to another person without apologizing for missing context?
Customer feedback
Tell us what made Cloud Horizon useful, unclear, or hard to trust.
Every customer test should leave a product signal. This form captures scores, blockers, and the one fix that would make the workflow easier to use again.
Scorecard
Clarity
Was the next step obvious, or did the product rely on us explaining the workflow live?
Speed
Did Cloud Horizon beat your current console, export, spreadsheet, script, or FinOps workflow?
After a pilot session
Use this after a guided customer test so scores map back to the pilot scorecard.
Open formAfter Marketplace activation
Use this if Microsoft login, token resolve, activation, or workspace creation felt unclear.
Open formAfter an MCP workflow
Use this when an agent answer needs better source grounding, permissions, or follow-up actions.
Open formWhat happens to this feedback
The form is wired into the product loop. We use the lowest scores and most concrete requested fixes to decide what changes before the next customer cohort.
Stored with context
The workflow, cloud surface, scores, blocker, and requested fix are saved together so the product note is actionable.
Reviewed by severity
Trust issues and Marketplace activation blockers are handled before copy polish or lower-impact requests.
Tied to follow-up
If you allow contact, we can confirm the fix, ask for missing context, or invite you back to retest the workflow.
Feedback loop
Send product feedback
Score the workflow you tried and tell us the one fix that would make Cloud Horizon easier to use again.