---
type: Article
name: A table for four at eight is not a search query.
id: "https://selfe.ai/insights/agent-ready-transactions/a-table-for-four-at-eight"
url: "https://selfe.ai/insights/agent-ready-transactions/a-table-for-four-at-eight"
publisher: "did:web:selfe.ai"
description: A customer request contains the variables that determine whether an offer is possible. Treating it as a loose search loses the information needed to give a trustworthy commercial answer.
datePublished: 12 September 2026
author: The Selfe team
---

# A table for four at eight is not a search query.

> A customer request contains the variables that determine whether an offer is possible. Treating it as a loose search loses the information needed to give a trustworthy commercial answer.

## In short

- A request needs its commercial context before availability or price can mean anything.
- The right structure lets an agent ask a useful follow-up instead of guessing.
- A complete request should travel into the booking, order or hand-off flow.

"A table for four at eight" contains a time, party size and a service context. Add a date, location, dietary need, occasion or policy requirement and the answer may change again. The same is true of a product order, an appointment or a quote.

## Requests have conditions

"A table for four at eight" contains a time, party size and a service context. Add a date, location, dietary need, occasion or policy requirement and the answer may change again. The same is true of a product order, an appointment or a quote.

If those conditions are lost, a result can look helpful without being useful. The customer still has to discover whether it applies to their actual situation.

## Ask the missing question early

An agent should not invent a detail simply to keep a journey moving. It should identify the one question that changes the answer and ask it before returning a confident recommendation. This is a better customer experience than a generic result followed by a late refusal.

For the business, it also creates a more useful inbound request. The team sees the constraints that shaped the choice instead of a short message that must be unpacked from scratch.

## Match the request to the source of truth

Some parts of a request can be answered from a stable description. Others need live availability, price, delivery terms or a person with the authority to confirm an exception. The transaction route should make that distinction clear.

The goal is not to expose every internal system. It is to connect the request to the system or person that can return the next true answer.

## Keep the context as it moves

When an agent sends a customer onward, the request should arrive with its important details. That allows the booking, order or service team to continue the conversation rather than repeat discovery.

This is the foundation of an agent-ready transaction: a specific need stays specific from the first question to the next permitted commercial action.

## Act on this

- [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan.
- [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry.
- [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size.
- [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`.
- [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.