Practical guide

Rehearse the client journey before moving real work

Last materially reviewed 2026-09-19

Quick answerUse fictional material to verify the whole handoff, then pilot with a willing client before migrating everyone.
What to know

Setup checklist: prepare harmless materials

Use an invented company name, a short sample brief and files that contain no client information. ManyRequests documents creating a test client separately from using an administrator’s client view. Follow the supported method for the account you are evaluating. Do not create unauthorized identities, start billable activity or upload confidential material merely to obtain a screenshot. The point is to learn the workflow while keeping the consequences small and reversible.

What to know

Walk the complete path

Have the fictional client find the service, submit a request, identify its state, respond to a clarification and review a new version. Separately, have the producer find the brief and next responsibility. Record whether the result is actually observed or merely described by the vendor. A successfully opened dashboard does not prove that a later approval, payment or permission transition behaves as your agency expects.

What to know

Add one interruption

Stop halfway through the fictional request and return through the normal supported navigation. Check whether the previous work remains recognizable and whether the next action is clear. Ask how the team should recover if a submission’s outcome is uncertain. Do not manufacture a real outage or submit a payment twice. The acceptance question is whether the supported process lets you inspect an existing result before trying again.

What to know

Choose a small pilot deliberately

If the rehearsal passes, pick a cooperative client and a bounded piece of work for a separate authorized pilot. Preserve the old records and explain which system is authoritative during the transition. A failure should send you back to the specific unmet requirement, not into a blind full migration. Keep what the rehearsal actually demonstrated distinct from what only live adoption can establish, including client preference, time savings and long-term reliability.

Continue when useful

Next: An agency portal demo scorecard that tests the hard parts

Make the demo follow one client job, including a revision and an interrupted handoff.

Open An agency portal demo scorecard that tests the hard parts →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. ManyRequests fictional client journey — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
  2. ManyRequests client experience — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
  3. ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19