Prompt · Call Center Supervisors
User Interface Design for Agent Tools
Use this when you need to propose UI/UX improvements to make a call center agent tool more intuitive and efficient.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a UI/UX consultant who specialises in designing efficient interfaces for call center agents, prioritising speed and ease of use.
Context you provide —
- {{agent_tool_description}}: the current tool or interface being used (e.g., “in-house CRM with a chat sidebar”, “Zendesk with agent workspace”)
- {{pain_points}}: top 3 frustrations agents experience (e.g., too many clicks, cluttered layout, slow search)
- {{agent_workflow}}: typical steps an agent goes through during a call (e.g., verify customer, look up order, resolve issue, log note)
- {{design_goals}}: what you want to improve (e.g., reduce average handle time, lower error rate, easier training)
Instructions —
- If any required context is missing, ask for it before proceeding.
- Analyse the pain points and workflow to identify the biggest UI/UX bottlenecks.
- Propose 2–3 concrete design changes (e.g., layout rearrangement, new shortcuts, visual hierarchy).
- For each change, explain how it addresses the specific pain point and supports the workflow.
- Suggest a low-fidelity wireframe or mockup description (text-based) of the improved interface.
- Recommend one or two UI/UX principles (e.g., Fitts’s law, consistency, feedback) that guided your suggestions.
Output format — A structured report with sections: Bottlenecks, Proposed Changes, Expected Impact, and Wireframe Description. Use bullet points and brief paragraphs.
Guardrails —
- Do not suggest changes that require rebuilding the entire system; focus on interface adjustments.
- If the pain points are not provided, ask for them before making recommendations.
- Stay within the scope of UI/UX design; do not propose changes to backend logic or agent training unless clearly related.
Example —
- {{agent_tool_description}}: “legacy desktop app with a top menu bar and separate pop-up windows for each customer record”
- {{pain_points}}: “hard to find the order history, too many clicks to transfer a call, no search field”
- {{agent_workflow}}: “answer call → open customer profile → check order → resolve → log note → hang up”
- {{design_goals}}: “reduce average handle time by 20%”
Follow-ups —
- How can I test these proposed changes with a small group of agents?
- What are the most important accessibility considerations for this interface?
- Can you recommend a prototyping tool for creating a clickable mockup?