# Design a graceful no-match experience

Use case · Platforms · Planned API workflow

Canonical page: https://datasdk.ai/use-cases/design-a-graceful-no-match-experience

Avoid misleading users with guessed names or stale company cards.

## Who this helps

A product should still be useful when company identification returns no result.

## How to use it

1. Define separate pending, unmatched, and unavailable interface states.
2. Keep earlier records from appearing as the current visitor's result.
3. Confirm response meanings against the eventual API contract.

## Illustrative example

A proposed interface would say no company match instead of substituting an example silently.

## What to check

The full API is coming soon; do not infer its public response schema from this concept.

## How Data SDK fits

The full Data SDK API is coming soon. Platform and AI-agent workflows are planning examples. Confirm access, data delivery, usage, branding, and resale terms before building or selling a feature.

These are suggested workflows, not a list of built-in integrations. Use your own approved analytics, CRM, and research process where needed. Matches and fields vary. A company match does not identify a person or prove buying intent.

## Related reading

- [Unmatched visit](https://datasdk.ai/glossary/unmatched-visit): An unmatched visit is a recorded visit without an available company association.
- [Schema](https://datasdk.ai/glossary/schema): A schema describes the structure and expected fields of data.
- [Fallback](https://datasdk.ai/glossary/fallback): A fallback is the behavior used when the preferred result is unavailable.
- [Offer identification in a website-builder product](https://datasdk.ai/use-cases/offer-identification-in-a-website-builder-product): Plan identification as a clearly explained optional website capability.
- [Build a tenant-safe company lookup service](https://datasdk.ai/use-cases/build-a-tenant-safe-company-lookup-service): Plan company lookup around authorized customer contexts.
- [Plan a retry-safe enrichment workflow](https://datasdk.ai/use-cases/plan-a-retry-safe-enrichment-workflow): Design safer retries before connecting company data to actions.

[Glossary](https://datasdk.ai/glossary) · [Use cases](https://datasdk.ai/use-cases) · [Comparisons](https://datasdk.ai/vs) · [For businesses](https://datasdk.ai/for-businesses) · [For builders](https://datasdk.ai/for-builders)