{
    "id": 1079469,
    "title": "Three days that have not happened yet, and the kind of request we built for",
    "slug": "three-premium-intent-days",
    "type": "post",
    "url": "https://teas.co.uk/three-premium-intent-days/",
    "modified": "2026-11-15T01:40:58+00:00",
    "excerpt": "I use three imagined customer days to explain Premium Intent, so here is what the term means, what is honestly built at teas.co.uk today, and what is still a plan.",
    "content_text": "I use three imagined customer days to explain Premium Intent, so here is what the term means, what is honestly built at teas.co.uk today, and what is still a plan.\n\nImagine two messages reaching a tea shop on the same evening.\nThe first says: best decaf green tea.\nThe second says: I want a good decaf green tea for my mother. She likes lighter flavours, caffeine keeps her awake, she drinks two cups a day, she is on a tight budget and she would prefer organic if possible.\nBoth want decaf green tea. Only one has told me enough to help properly. The second tells me who the tea is for, when she drinks it and what she can afford. Two cups a day on a tight budget means price per cup matters more than the price on the box.\nThat second message is what I call Premium Intent.\nWhat I mean by Premium Intent\nPremium Intent, as I use the term, is a request that carries the whole situation: the context, the emotional stake, the timing, the constraints, the budget, what a good result would look like and what the person would rather avoid. Years of search boxes trained most of us to squeeze a need into three words. Talking to an AI assistant, by voice or by typing, lets the need come out at full length.\n\"Premium\" describes how much the request tells you, not a fee and not a posh customer. I came up with the name in June 2026 while rebuilding teas.co.uk. Marketers talk about high intent and buyer intent, and the two words may well have met before. I don't know whether anyone has used the name this way, but it suits what we've built. My Tea Wiki entry notes when I started using it.\nA person who explains their situation has already done much of the choosing, so an answer that respects what they said is more likely to fit and to bring them back. It also raises the bar. If someone tells you the truth about their situation, pushing whatever you would rather sell betrays that trust.\nThree imagined days\nWhen I explain the idea, I follow three of these requests from start to finish. I want to be plain about them. The days are real only in the sense that they are ordinary life. They are not my customers and none of it happened. They are three imagined requests, written to show the shape of the idea.\nThe father. Picture a man who has his son for two months this summer, after four years without two full weeks together. The boy loves Pok\u00e9mon, and the father cares less about cost than whether the money makes the trip better for his son. A keyword search hears \"Pok\u00e9mon holiday\". A good answer hears a father trying to close a gap. It spends more on a hotel near the big day, so the boy does not arrive exhausted, and less on a flight upgrade he would sleep through. As I put it: spend where it helps the boy, refuse where it does not.\nThe proposal. A man in London has the ring and a partner who cannot stand being the centre of attention. A good answer starts with her: a private box rather than the front row, a quiet table, no photographer, and a straight \"Do not pay for the premium suite, you will be asleep most of the time you are in it.\" In that version of the day, tea has a small part, a calming tea waiting in the room for the morning after. That is the right size for a tea shop in someone else's big day.\nThe family. Two parents, an eleven year old and a six year old, plan New York, Las Vegas and the Grand Canyon by hire car without realising how far apart they are. A good answer will not let them plan a thirteen hour drive with a six year old in the back. It flies the long legs, drives the short ones, and raises what they did not know to ask, such as insurance and rest days.\nEach answer is shaped by what the person said, and says where not to spend as clearly as where to spend more.\nWhat is built, and what is not\nNone of those days can be booked through teas.co.uk. What I picture is hotels, theatres and restaurants each holding their own checked facts, with an assistant joining them into one plan. Most of that network does not exist yet. An assistant acting for a customer across several businesses belongs to version five of the build, which is planned, not built.\nWhat is built is the tea end, and it is real.\nThe Ask API at teas.co.uk declares premium_intent_supported. It asks any assistant calling it to send the full human request, with the context, constraints, budget and what success looks like, not a keyword summary. The mother's decaf green tea should arrive as the whole sentence, not as \"decaf green\".\nBehind that sits one checked set of product facts, live since version two launched on 10 May 2026. Every product has structured data behind its page, with identifiers, prices, availability, source links and price per cup. And since 6 October 2026, with the customer's approval, an assistant can search our catalogue, compare teas and fill a basket through the teas.co.uk MCP server. The customer checks the basket and pays on teas.co.uk.\nI cannot yet tell you how many of the requests reaching us are long and rich ones, and I will not guess.\nWhy I opened the door\nMuch of what I read about search and AI is about blocking AI systems to guard content. I went the other way. teas.co.uk is open to every assistant that behaves well, and protected against the ones that do not, because I want as many AI systems as possible to know the shop. The more that know us, the more often we are cited, and citations bring visitors and, in time, orders.\nPremium Intent is why that bet makes sense for a small specialist. A long, careful question is where depth beats size. A shop that has done the work on its facts can answer the tea part of a request better than a catalogue of everything.\nThose three days have not happened. The request they describe is already the kind we ask assistants to send us.\nWhat others have found\nOutside research and reporting that bears on this, with links to the original sources.\n\nGoogle's own report on the first year of AI Mode in the US found that the average AI Mode query is three times the length of a traditional search, and that follow-up questions grew by more than 40% a month (Google, May 2026). Search Engine Journal covered the findings in Google data shows AI search users moved past keywords and AI Mode queries are 3X longer.\nIn the same Google data, planning queries grew 80% faster than AI Mode queries overall, and comparison questions beginning with \"which\" grew 40% faster (Search Engine Journal).\nOpenAI launched Instant Checkout in ChatGPT in September 2025, built on an open standard called the Agentic Commerce Protocol (OpenAI). Search Engine Journal later reported that Instant Checkout gathered roughly thirty Shopify merchants in six months before it was retired (Search Engine Journal).\nSlobodan Manic argues in Search Engine Journal that agentic commerce is a structural change rather than another voice shopping fad, but that it is still unproven (Agentic commerce is not the next voice shopping, but it is still unproven).\n\nRead more\n\nPremium Intent\nThe complete payload\nClaim boundaries\nBuilt versus planned\nWide versus deep\nLee Samuel Tucker's builder vocabulary\nMeet the founder: why I built teas.co.uk\nLee Samuel Tucker on the Tea Wiki\nUnder the Hood\n\nMore from the newsWhy I call it Premium IntentThe decaf fruit tea problemWhat's inside a tea shop built for AI to read\nLee Samuel TuckerFounder, teas.co.ukTunbridge Wells, Kent",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}