Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.minoa.io/llms.txt

Use this file to discover all available pages before exploring further.

A business case is only as credible as the numbers inside it. The customer survey lets your champion or other stakeholders fill in those numbers themselves — so the inputs come from the customer, with their attribution attached, instead of being your best guess.

​
How a survey is created

Every business case gets a survey by default — you don’t need to set one up manually. When you finish step 2 of the business case builder (use case selection and build), Minoa automatically launches a survey for that business case using the inputs from your active scenario. By the time you reach step 3, the survey is ready to share. On step 3 of the builder, you’ll see a Send out a Survey card with a Copy Link button. That’s the link to send to your customer.
Send the survey link to your champion early — having them fill in real numbers up front makes every conversation that follows more grounded.

​
Relaunching or regenerating a survey

You can also launch (or relaunch) a survey from inside the business case at any time:
  1. Open the left side panel and click Edit Survey
  2. Under Gather And Sync Customer Inputs, click Re-open survey
This is useful when you’ve added or removed use cases since the survey was first created, or when you want to switch how inputs are grouped.

​
Bucket grouping

Inputs in the survey are organized into buckets so respondents aren’t faced with one long list. You have two options:
  • By use case (default) — one bucket per use case, plus a Baseline Inputs bucket for any global inputs shared across use cases
  • By Minoa AI — Minoa AI groups inputs into buckets that flow well for a respondent
The Automatic Grouping toggle keeps the survey in sync with the business case — when you change inputs or use cases in the BC, the survey updates to match.
With automatic grouping on, those syncs can regenerate survey buckets. Any manual bucket edits or custom groupings you applied may be overwritten — turn the toggle off if you need your layout to stay exactly as you left it.

​
What inputs are included

By default, every input from your active scenario’s use cases is included in the survey.
  • Global inputs that appear in multiple use cases show up once, in a shared Baseline Inputs bucket — your respondent only answers them once.
  • Inputs you don’t want the customer to see can be locked (see below).

​
Locking an input to exclude it from the survey

Some inputs you’d rather fill in yourself — pricing assumptions, internal targets, anything where the customer’s answer wouldn’t help. Lock those inputs to hide them from respondents. In the survey preview, click the lock icon next to any input. The tooltip reads:
This will lock the input for the customer and hide it from the survey.
Locked inputs still appear to you and other internal users; they’re just hidden from the customer-facing survey.
Common inputs to lock are internal metrics like ”% of time saved” or ”% improvement” — figures the customer typically can’t answer themselves. Leave volume, frequency, and current-state metrics unlocked for them to fill in.
Respondents don’t have to answer every question. They can fill in only the inputs they have a confident answer for and skip the rest — anything left blank simply has no response to review later.

​
Comments from respondents

Alongside their response to each input, respondents can leave a comment — useful for caveats, sources, or the assumptions behind their number. Comments stay attached to the input and travel with the response into the review step, so you see the customer’s reasoning when you decide whether to apply their value.

​
Reviewing responses

Survey responses are not automatically copied into the business case. Every response goes through a review step so you stay in control of what ends up in the final numbers.
When a respondent submits a value, a you will see the survey response appear on the use case card to the right of the input name. There are two actions you can take:
  • Accept — copies the response into the input. The value is recorded with attribution to the respondent and added to the input’s history.
  • Dismiss — hides the response without changing the input.
Once you accept or dismiss a response, the box goes away for that input. Related context lives in Use case cards and Input ownership.

​
Closing the survey

When you’re done collecting responses, open the Edit Survey copilot panel and mark the survey as Completed. The survey link stops accepting new responses. If you need to gather more later, you can relaunch the survey from the same panel.