A BETTER INITIAL BRIEF
Ask the questions needed to prepare a useful offer
Build a focused estimate questionnaire with supported answer types, conditional questions and a deliberate release from draft to published form.
Start the conversation with useful context
A quotation request is easier to assess when the customer has already described the relevant situation. Tsumira’s estimate wizard combines a selected catalog context with a bounded set of authored questions and contact policies. The aim is a useful first brief, not a long survey or an unconditional price promise. The company chooses which questions are genuinely necessary for reviewing the request and explaining the next step.
Choose the answer format that fits
The supported question types include short and long text, dates, single choice and multiple choice. The configuration supports up to eight questions, with bounded choice lists. Use a date for timing, a short field for a reference and a longer answer for context that cannot be reduced to an option. Contact policies distinguish required, optional and hidden supported fields, while preserving an actual contact route. Do not collect detail merely because an input is available.
- Text, date and choice answers
- Up to eight authored questions
- Explicit contact-field policies
Show follow-up questions conditionally
Questions can depend on an earlier visible answer, a selected option or a chosen offering. Visibility follows the authored question order, and hidden answers cannot activate a later chain on their own. This makes it possible to ask about a special requirement only when it applies. Check both the short path and the more detailed path before release. A condition must be supported by the actual configuration; it is not a promise of an unlimited visual workflow engine.
- Answer-based conditions
- Offering-based relevance
- Authored order and visible context
Publish a coherent questionnaire version
The studio maintains one draft and one published wizard configuration per company. Saving the draft does not replace the visitor’s live version. Review question wording, catalog choices and notices before publication. Submitted requests retain the relevant wizard version and snapshot context, so later improvements do not silently rewrite what the customer answered. The current wizard copy supports the implemented Japanese and English content model rather than automatic translation into every site language.
- Separate draft and published configuration
- Version context on submissions
- Review of wording and notices
A concrete workflow
Define the brief
Choose the customer decisions that are necessary for initial assessment.
Author the questions
Use suitable types and supported conditions with clear contact policies.
Review the paths
Test normal and conditional routes, catalog context and expectation notices.
Publish the version
Release the reviewed configuration and handle requests against their recorded context.
An illustrative working example
Example: assessing an installation request
The company asks for the desired timing and a short description. A chosen installation offering reveals a follow-up about site access, while an unrelated offering does not. The team reviews the full path and publishes the configuration. A later wording improvement becomes a new version; the earlier customer’s request still refers to the questions and offering context used when it was submitted.
Questions about this topic
Is this an unlimited survey builder?
No. The quotation wizard has a defined schema and bounded questions and options, designed for focused estimate intake.
Can a question depend on a previous answer?
Yes, through supported conditions on visible earlier answers, options or offering selections. Review the authored order.
Does saving a draft change the public form?
No. Draft saving and publication are separate operations for the company’s wizard configuration.
Will later question edits change old answers?
Requests retain version and snapshot context. New editing should not be treated as rewriting the customer’s original submission.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Docs
Workflow concept: Review question wording and response notices before publishing the complete questionnaire specification.
Google Sheets
Workflow concept: Compare supported offering choices and required brief information before authoring conditional questions.
Microsoft Teams
Workflow concept: Walk through normal and conditional question paths with the people who review incoming requests.