Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Contact Routing Page.
Required content and structure
Route visitors to sales, support, partnerships or press with only necessary fields.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: strong black typography, warm yellow panels and sharp geometric compositions; controlled contrast. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
List the actual destinations for support, sales, partnerships and press, along with the minimum information each needs. Provide an alternative contact route where one exists.
Layout and behavior
Let visitors choose the purpose first, then ask only relevant questions. Keep the selected destination visible through validation and confirmation.
Task-specific acceptance check
- Keep the destination clear and provide an alternative contact route.
- Test changing the contact purpose after entering text and a failed submission.
- Preserve useful input and avoid reporting that a message reached a team before delivery succeeds.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Contact Routing Page. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Route visitors to sales, support, partnerships or press with only necessary fields. Use the following task-specific layout guidance when translating the image into editable elements: Let visitors choose the purpose first, then ask only relevant questions. Keep the selected destination visible through validation and confirmation.
Visual direction from the example brief
strong black typography, warm yellow panels and sharp geometric compositions; controlled contrast.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Route visitors to sales, support, partnerships or press with only necessary fields. Keep the destination clear and provide an alternative contact route. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Contact Routing Page Design Prompt
Use this contact routing page design prompt to route visitors to sales, support, partnerships or press with only necessary fields.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Route the Inquiry Before Expanding the Form
A contact page reduces friction when people can identify the correct destination.
One large form with every possible field burdens simple inquiries and obscures where the message goes. Let visitors choose the purpose first, then ask only relevant questions. Keep the selected destination visible through validation and confirmation.
From the Prompt
Let visitors choose the purpose first, then ask only relevant questions.
Make It Your Own
Ask for [INQUIRY_TYPE] first. Show the minimum fields for sales, support, partnerships or press, name the destination and retain a direct alternative contact method.
Prepare the Contact Routing Page Content
Four columns present different contact purposes with different fields. Define the receiving team and required information for each route instead of sending every request to the same generic inbox.
List the actual destinations for support, sales, partnerships and press, along with the minimum information each needs. Provide an alternative contact route where one exists.
From the Prompt
Route visitors to sales, support, partnerships or press with only necessary fields.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this contact routing page. List the actual destinations for support, sales, partnerships and press, along with the minimum information each needs. Provide an alternative contact route where one exists. Identify missing inputs before replacing them with demonstration content.
Change the Inquiry Type Midway
The lower band provides an email alternative alongside general inquiries. Test successful routing and give users a way forward when the dedicated form cannot be used.
Preserve shared fields while explaining which details are no longer needed. Do not silently discard a drafted message when the visitor changes its destination. Test changing the contact purpose after entering text and a failed submission. Preserve useful input and avoid reporting that a message reached a team before delivery succeeds.
From the Prompt
Keep the destination clear and provide an alternative contact route.
Make It Your Own
Review the contact routing page against this requirement: Keep the destination clear and provide an alternative contact route. Test changing the contact purpose after entering text and a failed submission. Preserve useful input and avoid reporting that a message reached a team before delivery succeeds. Preserve approved content and revise only the parts that fail this check.
Review Your Contact Routing Page Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Test changing the contact purpose after entering text and a failed submission. Preserve useful input and avoid reporting that a message reached a team before delivery succeeds.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current contact routing page. Test changing the contact purpose after entering text and a failed submission. Preserve useful input and avoid reporting that a message reached a team before delivery succeeds. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
