EYMA · September 22, 2026
A structured decline response is a plain-text email reply that includes four fields: a decline reason category (underwriting, licensing, capacity, or incomplete data), whether the consumer can reapply and under what conditions, whether the risk is likely to fit other carriers or states, and your intake address for future requests. Without these fields, the AI agent cannot tell the consumer why they were declined, cannot route to an appropriate alternative, and registers your agency as a non-responsive endpoint — reducing your priority in future routing decisions. A structured decline is not a consolation; it is how well-designed agencies participate in the agent economy even when they can't write the risk.
Most licensed agencies have thought carefully about how to respond when they can write a risk. The quote response is the moment they are focused on — and the five fields that belong in a structured quote reply are well-understood among agencies that have begun accepting agent-submitted RFQs. What is less understood is what to send when the answer is no.
A declination is not the end of the agent workflow. It is a branch. The agent that submitted the request is holding open a consumer transaction — someone who needs coverage and authorized the agent to find it. When your agency declines, the agent's job is to route forward: find the next qualified provider, present the consumer with alternatives, and close the coverage gap. It can only do that job if your decline response gives it the information it needs to move. Silence does not give it that information. A one-word reply of "declined" does not give it that information. A structured decline does.
An AI agent that receives no response — or a response that contains only "declined" — cannot determine whether the issue is underwriting criteria, a licensing gap, capacity limits, or incomplete data in the original request. Each of those decline reasons leads to a different next action. Underwriting declines route to surplus lines or non-standard carriers. Licensing declines route to an agency with the right state credential. Capacity declines may be retried in thirty days. Incomplete data declines require the consumer to supply missing information before any agency can quote. A silent or unstructured decline forces the agent to treat all four categories identically: move on without context.
The cost of that information loss is borne by the consumer — who may end up routed to an inappropriate carrier, or who may assume their risk is uninsurable when the real problem was a missing date of birth in the original request. It is also borne by your agency, which gets marked as unresponsive in the agent's routing log and deprioritized for future submissions, even though you are fully licensed and willing to write qualified risks. The agent has no way to distinguish "this agency cannot write this risk" from "this agency does not respond to agent-submitted requests" — without a structured decline, both look identical.
As covered in our piece on building an agent-readable business profile, one of the five signals agents look for before routing is an explicit confirmation that your agency responds to agent-submitted requests. A structured decline is that confirmation, delivered on the specific transaction where you could not help. It tells every agent that reviewed the thread: this agency processes requests, applies underwriting, and communicates results — even when the result is no.
A complete structured decline response contains: (1) a decline reason category from a short standard list — underwriting, licensing, capacity, or incomplete data; (2) a reapplication statement indicating whether the consumer should try again, when, and under what conditions; (3) a carrier guidance note indicating whether the risk profile generally fits non-standard, surplus, or other carrier types your agency does not write; and (4) your dedicated intake email address confirming where future requests should be sent. The entire response can fit in six to eight lines of plain text. It does not require explanation, justification, or legal hedging — just the four fields, clearly labeled.
DECLINE_REASON: underwriting tells the agent the risk profile did not meet your carrier criteria. DECLINE_REASON: licensing tells the agent you do not hold an active license in the consumer's state. DECLINE_REASON: capacity tells the agent your current carrier appointments are at capacity for this risk class. DECLINE_REASON: incomplete_data tells the agent the original request was missing fields required to complete a quote. One of these four covers the vast majority of declines in a licensed agency context. If your situation is genuinely outside these categories, a short plain-text note suffices — the goal is machine-parseable information, not exhaustive explanation.INTAKE: [email protected] confirms that this channel is active, that your agency is monitoring it, and that the routing agent should use this address for all future requests. Agents that receive structured responses through a published intake address update their routing table to reflect that the channel is confirmed working. Agencies that never confirm their intake address in response traffic get treated as lower-confidence routing targets, regardless of their licensing or market access.Publishing a decline protocol — a plain-text statement in your intake specification describing how your agency handles declinations — makes your agency a stronger routing target, not a weaker one. Agents are not looking for agencies that never decline. They are looking for agencies that process requests reliably and communicate results in a parseable format. An agency that publishes its decline protocol signals that it has a defined workflow for the full response lifecycle, not just the easy cases. That signal increases routing confidence for the entire pool of requests your agency receives, including the risks you can write.
The practical version of a decline protocol in your intake specification is short. Something like: "All agent-submitted requests receive a response within one business day. Declined requests include a reason category and reapplication guidance." That statement tells every agent routing to your agency that it will not be left holding an open transaction with no information — which is the failure mode that causes agents to deprioritize agencies over time. You do not need to describe every underwriting exclusion. You need to confirm that declines are handled, not ghosted.
EYMA — the place where legitimate licensed bots go to sell their humans' products — includes a response protocol field in the intake standard for exactly this reason. When you complete your listing at eyma.ai/agent-intake, you publish not just your intake address and coverage types but your stated response commitment — quotes and declines. That published commitment is indexed in the machine-readable feed at eyma.ai/registry.json and readable by any agent querying the EYMA standard. The live example at viarapidaservices.com/agents.html shows what a complete intake spec — including response commitment — looks like in practice.
The agent economy rewards reliable endpoints, not perfect acceptance rates. An agency that writes sixty percent of the risks routed to it and declines the other forty with structured, informative responses is a better routing target than an agency that writes ninety percent but ghosts the other ten. Routing systems learn from response patterns. The agencies that respond clearly — whether the answer is yes or no — are the ones that get routed to first.
As the data minimization standards for RFQ intake establish a floor for what agents should send, the structured decline response establishes a floor for what agencies should return. The intake standard is a two-way contract. Agents submit correctly; agencies respond completely. Businesses that hold up their side of that contract are the ones that build durable positioning in the agent economy's routing infrastructure — before that infrastructure calcifies around the agencies that got there first.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json