Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Customer Support Inbox.
Required content and structure
Combine conversation list, thread, customer context and assignment controls.
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: light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Define conversations, assignment, customer context, draft behavior and handoff states. Supply threads with incoming, outgoing and unsent messages.
Layout and behavior
Keep the list useful for triage and the thread readable in chronological order. Show draft and assignment states close to the conversation they affect.
Task-specific acceptance check
- Keep message order, draft state and handoff status clear.
- Switch conversations with a draft, reassign a thread and handle a failed send.
- A local draft should never look like a delivered message, and handoff should not lose context.
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 Customer Support Inbox. 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: Combine conversation list, thread, customer context and assignment controls. Use the following task-specific layout guidance when translating the image into editable elements: Keep the list useful for triage and the thread readable in chronological order. Show draft and assignment states close to the conversation they affect.
Visual direction from the example brief
light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy.
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: Combine conversation list, thread, customer context and assignment controls. Keep message order, draft state and handoff status clear. 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 Customer Support Inbox Design Prompt
Use this customer support inbox design prompt to combine conversation list, thread, customer context and assignment controls.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Protect the Conversation Context
A support inbox needs fast movement between conversations without sacrificing the reply being written.
Assignment and draft state should remain legible when the list changes. Keep the list useful for triage and the thread readable in chronological order. Show draft and assignment states close to the conversation they affect.
From the Prompt
Keep the list useful for triage and the thread readable in chronological order.
Make It Your Own
Use a conversation list, chronological thread and customer-context panel. Preserve [DRAFT] per conversation and display [ASSIGNEE] and [HANDOFF_STATE] near the reply action.
Prepare the Customer Support Inbox Content
The center thread separates customer messages from a highlighted internal note. Preserve sender, timestamp and visibility for each entry when preparing the conversation data.
Define conversations, assignment, customer context, draft behavior and handoff states. Supply threads with incoming, outgoing and unsent messages.
From the Prompt
Combine conversation list, thread, customer context and assignment controls.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this customer support inbox. Define conversations, assignment, customer context, draft behavior and handoff states. Supply threads with incoming, outgoing and unsent messages. Identify missing inputs before replacing them with demonstration content.
Test a Handoff Mid-Draft
The composer offers Reply and Internal Note modes with a Send action. Test visibility, draft preservation and delivery failures before reporting a message as sent.
Change the assignee while a reply is unfinished. The interface should make the handoff visible and retain the draft without implying that it was sent. Switch conversations with a draft, reassign a thread and handle a failed send. A local draft should never look like a delivered message, and handoff should not lose context.
From the Prompt
Keep message order, draft state and handoff status clear.
Make It Your Own
Review the customer support inbox against this requirement: Keep message order, draft state and handoff status clear. Switch conversations with a draft, reassign a thread and handle a failed send. A local draft should never look like a delivered message, and handoff should not lose context. Preserve approved content and revise only the parts that fail this check.
Review Your Customer Support Inbox Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Switch conversations with a draft, reassign a thread and handle a failed send. A local draft should never look like a delivered message, and handoff should not lose context.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current customer support inbox. Switch conversations with a draft, reassign a thread and handle a failed send. A local draft should never look like a delivered message, and handoff should not lose context. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
