Request handling
Every request should reach the right next step.
Coaching, workbook, speaking, creative, book, store, accessibility, and member-access requests each need a clear destination so visitors get helpful follow-up without oversharing sensitive details.
Request context
Operational clarity should still feel connected to the public site.
This page keeps support expectations close to the actions visitors actually use: forms, calls, resources, account access, and external store support.
Service principle
Ask for only what is needed, then guide the visitor clearly.
The request map keeps follow-up practical: collect the right context, protect sensitive details, and send each request to the page or platform built for it.
Right context
Every request should ask for the minimum details needed for a useful response.
Consent and expectations
Workbook and email paths should make follow-up expectations clear before visitors subscribe.
Lane separation
Coaching, speaking, creative, store support, book orders, accessibility, and general messages should not collapse into one vague inbox.
Request map
Each public path has a purpose, destination, and next step.
Use these cards to understand where a request belongs before sending private details or assuming every question should become a coaching inquiry.
Workbook signup
This marketing form should not collect private coaching, clinical, legal, or crisis details.
first_nameemaillead_magnetsource_contextconsentconsent_timestamp
Before this path collects details
- Final workbook file is ready
- Sender and delivery expectations are clear
- Unsubscribe and consent handling are clear
Clarity Call booking
Booking is a fit conversation, not crisis care, clinical intake, medical advice, or legal advice.
nameemailscheduled_timetimezonebooking_statussource_context
Before this path collects details
- Calendar redirect is clear
- Preparation email is ready
- No-show and cancellation follow-up are defined
Contact intake
General contact must not become the place for detailed coaching intake, crisis disclosures, or order payment details.
intentnameemailmessage_or_contextsource_contextconsent_timestamp
Before this path collects details
- Support destinations are clear
- Retention expectations are clear
- Spam and rate protection are configured
Speaking inquiry
Speaking requests should not collect private counseling details or emergency support requests.
organizationcontact_nameemailevent_namedate_or_windowlocation
Before this path collects details
- Fee and travel expectations are clear
- Recording and media-rights language is clear
- Speaking follow-up path is assigned
Creative inquiry
Creative intake stays separate from coaching, store support, and book support.
project_typenameemaildesired_dateusagedeliverables
Before this path collects details
- Creative inquiry destination is clear
- Usage and licensing expectations are clear
- Portfolio permission process is clear
Bulk book order
Amazon retail support remains external; bulk and event requests need a separate fulfillment path.
nameemailorganizationquantityneeded_byshipping_context
Before this path collects details
- Bulk pricing expectations are clear
- Shipping and fulfillment process is clear
- Event resource bundle terms are clear
Store support
Order, payment, shipping, sizing, return, and fulfillment questions should not enter the coaching inquiry path.
order_number_optionalemailissue_typemessage
Before this path collects details
- Store support URL is verified
- Order support path is clear
- Return and shipping policy are clear
Accessibility feedback
Accessibility feedback is not an emergency channel and should not be buried in general contact.
page_urlissue_descriptiondevice_or_browserassistive_technology_optionalfollowup_email_optional
Before this path collects details
- Feedback destination is clear
- Response expectations are clear
- Accessible anti-spam control is in place
Request standards
Every request path should meet the same trust standard.
Visitors should know what they are submitting, why it matters, what happens next, and when another support path is more appropriate.
Follow-up signals
Measure usefulness without over-collecting.
Basic stages and event names can help the team improve the site while avoiding unnecessary sensitive content or treating every click as coaching readiness.
Lifecycle stages
Record status without guessing intent.
- new
- validated
- delivered
- triaged
- awaiting_response
- responded
- booked
- resolved
- archived
- escalated
Analytics events
Keep the core funnel observable.
workbook_form_startworkbook_form_submitclarity_call_calendar_viewclarity_call_booking_completecontact_form_startcontact_form_submitspeaking_form_startspeaking_form_submitcreative_property_outbound_clickshop_gateway_clickshop_support_clickthank_you_view
Before collecting sensitive details
Keep high-risk information out of general forms.
The site can guide visitors today. Private account access, uploads, payment details, crisis disclosures, and sensitive coaching notes should use the right protected process.
Workbook delivery should not ask for sensitive details
Workbook delivery should not ask for sensitive details
Support destinations should be clear before visitors share private conte
Support destinations should be clear before visitors share private context
Member access should stay invitation-based until private-resource rules
Member access should stay invitation-based until private-resource rules are reviewed
Booking and contact paths should protect against duplicate submissions
Booking and contact paths should protect against duplicate submissions
Privacy
Privacy, retention, unsubscribe, and crisis-support language should stay visible wherever personal details are requested
Use this guide
Choose the correct request path first.
Start with the contact page when you are unsure, the Clarity Call for coaching fit, the shop for order support, and member access only when private resources apply.