Book a Demo

Make your demo show an empty state

Format: Company perspective.

“No requests” can be the wrong answer even when a screen has nothing to show.

Carbon's design guide notes that a screen can be empty when data exists but cannot be shown.[15] Ask what the screen has checked before trusting its message.

Use this four-part demo check with fictional records:

  1. Genuinely no data: The authorized read succeeds and finds no matching requests. Ask: “What evidence lets this screen say there are none?” Check whether a hidden filter is narrowing the result.
  2. Still loading: The read has not finished. Ask: “What tells the operator to wait rather than conclude the queue is clear?” A loading state should not briefly report a false zero.
  3. Failed connection: The data could not be retrieved. Ask: “Where can staff see the failure and last verified read?” If old records remain visible, their age should remain visible too.
  4. No access: This user lacks permission. Ask: “Who handles an access request without exposing protected records?” The message should not encourage staff to borrow someone else's login.

In a hypothetical account review tool, the same blank panel could mean any of these things. Staff need to know whether to move on, wait, report a failed connection or ask the person who grants access.

Do not accept invented sample activity as the fix for a sparse screen. Demo records should stay clearly labeled and separate from genuine work.

Core Agentic scopes custom interfaces around those operational decisions. Book a Demo and ask what a proposed screen says when it has no verified result to show.

Sources

These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.