A little structure. A clearer next step.

Customer-feedback decisions

Group feedback around one underlying problem and choose a next step you can explain and verify.

Free to use · No signup · Yours to keepRead the guide

Make it yours.

Start with what you know. Leave the rest open until you have evidence.

0 of 8 fields filledLoading your local draft…

Your answers stay in this browser. They are not sent to Soloop or synced between devices. Download a copy to keep it.

Preview & export

Which customer and goal does this serve?

Name the current product goal and intended segment before weighing individual requests.

Example

Reliable client handoffs for small agencies. This review concerns records used by account managers.

0 / 12,000 characters

Which independent sources support the request?

Keep message IDs, dates and account codes. Multiple messages from one account are not multiple customers.

Example

R1 and R2 from account A; R3 from account B, [dates]. Three messages, two independent accounts.

0 / 12,000 characters

What is the underlying problem?

Separate the attempted job and obstacle from the requested solution. Record the current workaround.

Example

Job: report accepted handoffs. Obstacle: missing dates in an export. Requested solution: a connector; existing workaround: manual correction.

0 / 12,000 characters

What is reported, reproduced or still unknown?

Preserve source references and contrary evidence. Do not invent frequency, revenue impact or a shared root cause.

Example

Account A's export issue reproduced. Account B's report is unverified. Whether both have the same cause is unknown.

0 / 12,000 characters

Fix, build, ask or defer?

Give the reason and scope boundary. Fix restores a promise; build adds a capability; ask resolves uncertainty; defer keeps a reopening condition.

Example

Fix: investigate missing dates first. Exclude a new connector. Defer broader reporting until the corrected export is checked.

0 / 12,000 characters

Who owns the next step and review?

Name an owner, date or triggering event and unresolved questions to answer before committing more work.

Example

Founder investigates reproduction and estimates effort. Review before committing a release; shared cause remains unconfirmed.

0 / 12,000 characters

How will you verify or reverse the decision?

Define observable checks, relevant edge cases and a finding that would change the scope or priority.

Example

Accepted handoffs export the right date; pending ones stay accurate. Split the work if account B has a different cause.

0 / 12,000 characters

Who needs an update, and when?

Distinguish investigation, plan, checked result and verified release. Do not call the customer's workflow fixed until they can verify it.

Example

Update accounts A and B after a verified release and ask them to check their exports. No connector delivery date is promised.

0 / 12,000 characters

Read the guide

Back to answers

Your working document

A clear record of your thinking, ready to take with you.