FIGR / UI TEMPLATE

Player Support

Handle player issues with account and platform context, purchases, gameplay details, attachments, troubleshooting, ticket status, and agent replies.

This inbox reference covers gaming. Its sample screen includes Rank points missing and Purchase not delivered and the Create ticket action. Adapt its workflow to your product and design system.

Player Support

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Inbox

Primary action

Create ticket

Pattern

Player Support inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The player support screen supports “Create ticket” while keeping my tickets and known issues in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Create ticket
  • Main area: My tickets brings the user to the relevant workflow
  • Related area: Known issues keeps nearby context accessible
  • Open tickets: 2 in the sample screen
  • Avg reply: 4h in the sample screen
  • Example 1: Rank points missing
  • Example 2: Purchase not delivered
  • Input: Player ID

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Preserve the page structure and explain what is still loading
  • Empty: Show that the current queue or filter has no matching conversations
  • Error: Keep draft replies and clearly mark send failures
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Create ticket and say what happens next

Where it fits

My tickets → Known issues → Create ticket → Review result

Patterns in this screen

Player Support inbox, My tickets, Known issues, permission handling, error recovery

UX choices to review

Keep the selected thread, sender, and next action visible

In this example, Rank points missing is one of the records worth checking. Keep the sample data clearly separate from a live system.

Show ownership, priority, and reply state without hiding the conversation

Preserve a draft when the user switches threads or a send fails

Try a similar screen in Figr

Design a player support screen for an existing gaming product. Use our actual design system, components, and content rules. Cover My tickets and Known issues, include believable records such as Rank points missing, and make "Create ticket" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗