Skip to main content
UI Coach Logo
Back to challenges
Hard

Verified Caller Identity Card

Design an incoming-call experience that shows identity information the caller has explicitly verified and shared, without covert imaging or detection.

Mobile

The brief

Understand the problem

Background

Unknown calls may be legitimate deliveries, clinics, banks, or scams. A profile photo alone is weak evidence, and collecting an image from the caller without consent would be invasive and unreliable.

User context

Laila receives a call claiming to be from her bank's fraud team. She needs to know what has been verified and a safe way to continue without reading account secrets aloud.

Product problem

The interface must distinguish phone-number reputation, organization verification, contact-book data, and user reports while never presenting one signal as proof of intent.

Objective

Create an incoming-call identity card, verification detail, safe callback, and reporting flow.

What to design

Define the experience

Required experience

  • Incoming call identity summary
  • Evidence and warning detail
  • Verified callback path
  • Block and report

Screens and states

  • Incoming call
  • Identity evidence
  • Safe callback
  • Report outcome

Core user flow

Follow the critical path

  1. 01

    Laila sees the claimed organization and verification status

  2. 02

    She opens details without answering

  3. 03

    She declines and uses the bank's verified in-app callback

  4. 04

    She reports the original number as suspicious

Product rules

Requirements and constraints

Requirements

  • Attribute every identity signal
  • Never capture a caller image without consent
  • Offer a callback using independently verified contact details
  • Avoid exposing private contact labels to other users
  • Support block and correction requests

Constraints

  • Caller ID can be spoofed
  • Some legitimate organizations use shared numbers
  • The phone operating system limits pre-answer interaction

Reality check

States worth considering

A verified number is compromised
A legitimate caller uses a new number
The phone is offline
Community reports are malicious
An emergency caller lacks verification

Ready-to-use content

Mock data

Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.

Call evidence

  • Claimed caller: North Bank
  • Number not listed on the bank's official site
  • Similar calls reported by 18 users this week
  • Safe option: call through the North Bank app

Finish line

What to deliver

  • Four mobile call states
  • An evidence hierarchy that avoids a single misleading trust score

If you want more

Optional extensions

Add business call reason verification
Design a correction flow for mislabeled numbers

Optional direction

Visual resources

Use these as a starting constraint if you want one. They are not part of the required solution.

Color palette
#1B1A1A
#E9C5B7
#716561
#8B8C8A
#8C848C
Font pairing
ElsieRoboto

Elsie & Roboto

Clear interface writing gives people the confidence to understand what changed and decide what to do next.

Icons
Illustrations