The contact page should do one job well: reduce ambiguity. Each lane below is mapped to the type of request it should receive, the response window you can expect, and the best information to include in the first message.
Route your request to sales, support, or legal first. That reduces internal handoff time.
A short, complete first message is better than multiple fragmented follow-ups.
The request is reviewed, routed if needed, and answered by the responsible team.
Use this lane for pricing, enterprise rollout planning, plan selection, commercial scope, and onboarding design.
Use this lane for workspace access issues, billing questions, broken flows, configuration help, and live platform troubleshooting.
Use this lane for privacy requests, compliance review, contractual questions, business document handling, and policy matters.
Strong first messages are short, specific, and actionable. If your request is about a client workspace, billing event, or broken workflow, include the reference details once and let the team investigate from there.
Sales can help you align the plan, rollout expectations, onboarding sequence, and commercial scope before your team creates a long-term workspace.