Page role
Cross-route contact, not a vague catch-all.
Use this page when someone needs to reach the business directly or does not clearly fit the flagship, direct-help, TMAAS, or live branch pages yet.
Contact Gray Shadow Consulting
Start the right conversation instead of wandering into the wrong lane.
This page should function as a clean inquiry surface for direct help, organizational conversations, live delivery interest, and other legitimate outreach. It should not replace the more specific route pages when those are the better fit.
What this page should do
Make contact possible without flattening the whole architecture.
A good contact page should help people self-select intelligently: direct-help inquiries, organizational inquiries, and live-delivery interest should all feel legitimate here, while the flagship route remains the default path for most people.
Choose the best-fit lane
Most visitors should still use a more specific route when one exists.
This page works best when it clarifies choices instead of acting like every kind of need belongs in the same unlabeled inbox.
Higher-touch individual help
Use the direct-help lane for urgent or complex individual support
If someone already knows they need direct intervention, the direct-help route is a cleaner fit than a generic contact page.
Go to direct helpOrganizations and teams
Use TMAAS for B2B or organizational conversations
Company or team buyers should have a serious branch rather than getting mixed into consumer-oriented inquiry language.
Go to TMAASLive delivery
Use the live branch for seminars, workshops, and speaking interest
Authority and live-delivery interest should stay connected to the live page so that context and expectations remain clean.
Go to live deliveryInquiry design note
The final form and routing logic still need to be decided explicitly.
The structure is now here, but the actual contact mechanism is still intentionally unresolved. The right next step is to define whether this page should route to email, an Airtable form, a qualification form, or separate branch-specific contact flows.
Next move
Keep contact as a routing-and-inquiry surface until the final submission mechanic is chosen.
That preserves architectural clarity while leaving room to choose the right operational intake method instead of hardcoding the wrong one too early.