Task Flow Mickael Rutembya · Flow Atlas

Contact Form

/contact/

Atomic steps for a visitor to submit a contact inquiry and receive an acknowledgement.

Task intent

What the user is trying to do

« Send a message through the contact form and get an acknowledgement. »

Entry points

ElementDestination
Footer link Contact/contact/
Header link Contact/contact/
Programme CTA General contact/contact/

Flow

Adjacent routes — click a node to open it.taskflow
flowchart TD A["Start: visitor clicks Contact"] --> B["Land on /contact/"] B --> C["Read form instructions"] C --> D["Fill name, email, message"] D --> E["Submit form"] E --> F["Backend validates and stores inquiry"] F --> G["Auto-acknowledgement email queued"] G --> H["Visitor sees success message"] H --> I["End: team follows up"] click B "https://mickael-umt.com/contact/" "Open Contact" click H "https://mickael-umt.com/contact/" "Open Contact" click I "https://mickael-umt.com/contact/" "Open Contact"

Step inventory

IDStepActionSystem state
S1Open contactNavigate to contact pagePage loaded, form visible
S2Read instructionsReview fields and privacy noticeNo state change
S3Fill formEnter name, email, messageClient-side validation enabled
S4SubmitPOST to backendLoading + validation
S5ConfirmationView success messageInquiry stored, email queued

Flow scenario

Scenario CF1

Prospect sends a general inquiry

Trigger

  • Visitor clicks Contact from footer
  • Wants to ask about a programme or collaboration

Experience

  1. Contact page loads with form fields and privacy notice.
  2. Visitor enters name, email, company, and message.
  3. Submits and sees confirmation message.
  4. Team receives inquiry and responds within SLA.

Trust and safety rules

  • Email is verified before outreach.
  • Message is stored with consent timestamp.
  • No sensitive data should be sent through the form.

Interaction rules

  • Required fields validated client-side and server-side.
  • Success message replaces form on completion.
  • Privacy notice linked from form footer.

Result states

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