Service Configurator Summaries: Separate What the Customer Provided From Illustrative Examples

The risk

A service configurator often shows illustrative examples to help customers decide: a sample layout, a sample colour scheme, a sample text. If the final enquiry summary mixes those with the materials the customer actually supplied, the business may later work from an example the customer never chose, or the customer may assume the business will use something they only glanced at. This article proposes a summary layout that separates them. It is an example workflow, not an observed result, and the scenario is hypothetical.

Inputs

Imagine a small studio offering custom invitation design. During configuration the customer may:

Type their own wording.
Upload their own image.
Choose an option from a menu.
View, but not select, example layouts shown for inspiration.
Tick an example as a style they like, which is a preference, not a supplied file.

Classify each item the configurator can display into one of these groups: Provided by you, Chosen by you, Liked as inspiration, and Example shown only.

Summary layout

Show four labelled sections in this order.

Provided by you: your own text and files, each with a name and a short description. Use the customer's own words, unedited.
Chosen by you: menu selections and options.
Liked as inspiration: examples the customer marked, labelled as a direction, not an instruction.
Not part of your enquiry: if shown at all, a brief note that examples seen during configuration are not included unless listed above.

Before sending, show a confirmation line asking the customer to check that the first section matches what they meant to supply.

Decision branches

If a customer provided nothing, show Provided by you with a plain statement that nothing was supplied, not an empty box.
If the customer ticked an example but also supplied their own material for the same part, show both, and ask which should lead.
If an uploaded file fails or is missing, flag it and do not list it as provided.
If an example is changed after the customer selected it, mark that the selection refers to an older version and ask them to review.

Whether to show the fourth section at all is optional; include it where examples are prominent enough to cause confusion.

Stop conditions

Do not allow sending when:

A listed file is not actually attached.
Any item appears in more than one section without a visible reason.
The Provided by you section contains anything the customer did not type or upload.
The customer has not seen the summary before sending.

Worked example

A customer types their own invitation wording, uploads one photo, chooses a size and a paper option, and ticks a floral sample layout. The summary shows: Provided by you, the wording and one photo. Chosen by you, size and paper. Liked as inspiration, the floral sample, labelled as a direction. A note states that other examples seen are not part of the enquiry. The business reads the first section as the supplied material and the third as guidance only.

Acceptance test

Create four test enquiries: wording only, upload only, example only, and all of them together. For each, check:

Nothing the customer did not supply appears under Provided by you.
A ticked example never appears as a supplied file.
A failed upload is flagged and not listed as provided.
A person reading only the summary can state which items to work from and which are inspiration.

If any check fails, adjust the sections or labels and repeat. Keep the four test enquiries for later changes.

Conclusion

A clear summary protects both sides. Separating what the customer supplied from what they chose, liked or merely saw keeps the business from working off the wrong source and keeps the customer from assuming examples are promises. Test it with simple enquiries before you rely on it.