Task Flow Mickael Rutembya · Flow Atlas

Call Qualification

/contact/#call-qualifier

Atomic steps for a prospect to submit a structured qualification request and trigger follow-up.

Task intent

What the user is trying to do

« Submit a structured qualification request so the team can route me to the right mandate. »

Entry points

ElementDestination
Programme CTA Qualifier/contact/#call-qualifier
Home CTA Qualifier/contact/#call-qualifier
Footer Contact/contact/#call-qualifier

Flow

Adjacent routes — click a node to open it.taskflow
flowchart TD A["Start: visitor clicks Qualifier"] --> B["Land on /contact/#call-qualifier"] B --> C["Read qualification fields"] C --> D["Fill structured form"] D --> E["Submit request"] E --> F["Backend validates and stores lead"] F --> G["Team notified"] G --> H["Visitor sees confirmation"] H --> I["End: follow-up scheduled"] click B "https://mickael-umt.com/contact/#call-qualifier" "Open Contact" click H "https://mickael-umt.com/contact/#call-qualifier" "Open Contact" click I "https://mickael-umt.com/contact/#call-qualifier" "Open Contact"

Step inventory

IDStepActionSystem state
S1Open contactNavigate to qualification anchorPage loaded, form visible
S2Read fieldsReview name, company, need, timelineNo state change
S3Fill formEnter structured dataClient-side validation enabled
S4SubmitPOST to backendLoading + validation
S5ConfirmationView success messageLead stored, team notified

Flow scenario

Scenario CQ1

Qualified prospect books a discovery call

Trigger

  • Visitor clicks "Qualifier une mission" from programme page
  • Arrives at contact with call-qualifier anchor

Experience

  1. Contact page scrolls to qualification form.
  2. Visitor enters name, company, mandate type, timeline, budget range.
  3. Submits and sees confirmation message.
  4. Team receives lead and schedules call.

Trust and safety rules

  • Form data is stored as a lead with consent timestamp.
  • No contract is created at this step.
  • Email is verified before any outreach.

Interaction rules

  • Form fields are required and validated client-side before submit.
  • Anchor scroll on load for direct links.
  • Success message replaces form on completion.

Result states

StateWhat the user seesWhat happens next
Form visibleEmpty qualification formUser fills and submits
LoadingSpinner or disabled submitValidation runs
SuccessConfirmation messageLead created, team notified
ErrorField errorsUser corrects and resubmits