WEBSITE INQUIRY ROUTING · Workflow idea
When a website receives submissions through different forms, prepare a dedicated team conversation for each form and format the new inquiry for review. Show the proposed destination and included contact details so an authorized teammate can confirm access before anything is posted.
01 / The starting point
A person submits a request through one of the selected website forms
“Match the submission to its form, prepare a clearly formatted team notice, and hold channel creation or posting until an authorized person approves the destination and content.”
02 / The work
Helps teams notice and organize website inquiries in their shared work area rather than relying on one person to check each form.
Keep the submitted information and source form together so the right team can understand the request.
Match the inquiry to the form it came from and show the proposed team conversation for review.
Format only the details the receiving team needs and make missing or sensitive information easy to spot.
Have a form owner confirm that the proposed destination is restricted to people allowed to see the submission.
Require a person to approve the conversation setup and exact message before the inquiry is shared with the team.
Keep the approved submission linked to its form and make the person responsible for follow-up clear.
03 / The result
A review-ready team message linked to the correct form and proposed conversation, awaiting approval before contact details are shared.
Customer support · Example outcome
A review-ready team message linked to the correct form and proposed conversation, awaiting approval before contact details are shared.
Submissions may contain personal or sensitive details. Use restricted team spaces, share only fields needed to handle the request, and require an authorized person to approve the destination and exact message before posting.
04 / Make it yours
A few choices shape the work around your team.
Select the forms in scope and identify the minimum submission details each team needs.
Decide where each form belongs and confirm that the intended team has appropriate access.
Name who checks the proposed destination, contact details, and team message before it is posted.
Check a first submission, repeat entry, and sensitive field to confirm nothing is shared with an unapproved audience.