EYMA · Published September 25, 2026 · Updated October 22, 2026
A renewal RFQ from an AI agent is not the same as a new-business quote request. It arrives with existing policy data attached — policy number, expiring premium, current carrier, coverage limits, and renewal date — and it expects the agency to respond with a renewal offer, a competitive alternative, or a documented reason it cannot quote. Agencies that are set up only for new-business intake will miss renewal requests entirely, because the data structure is different and the response format is different.
The volume of agent-submitted renewal requests is still low, but the pattern is already established: consumer agents that manage ongoing financial products — insurance, subscriptions, service contracts — are built to handle renewals as a scheduled task, not a reactive one. Sixty to ninety days before a policy's expiration date, the agent initiates a renewal check. If the consumer's current agency is listed in a machine-readable intake profile, the agent routes the renewal RFQ there first. If the agency doesn't respond — or hasn't published renewal intake as a covered request type — the agent routes to competitive providers and presents those quotes to the consumer without the incumbent agency ever knowing it was in play.
The stakes on renewal requests are higher than on new-business requests. The agency already has a relationship with the consumer. Losing the renewal to an agent that routed elsewhere is not just a missed sale — it is a retention failure that requires no complaint, no cancellation call, and no moment where the agency can intervene. The consumer simply lets the old policy lapse and the new one the agent found takes over. This is how agencies lose long-tenured clients without ever knowing why.
A well-formed renewal RFQ contains four categories of data that a new-business RFQ does not: the existing policy identifier, the expiration date, the current in-force premium, and the current carrier name. These fields allow the receiving agency to pull the expiring policy, price a renewal, and respond with a comparison — which is exactly what the consumer's agent is asking for. If any of these fields are missing, the agency should request them before proceeding, not skip the renewal quote entirely.
Beyond the renewal-specific fields, the request structure mirrors what is described in our piece on what agencies need to receive an agent RFQ: a consumer authorization reference, the coverage type, the requesting agent's identity and contact address, the response format expected, and the window within which a response is needed. For renewals, the window is typically longer than for new-business requests — 24 to 48 business hours rather than 4 to 8 — because the agent is working from a scheduled review cycle rather than an immediate consumer need. This is a meaningful operational difference: agencies with a normal 24-hour response capability can handle renewal RFQs without any special infrastructure, provided they recognize the request as an agent submission in the first place.
In most cases, yes — the original FCRA consent covers subsequent renewals on the same policy if the consent language authorized use for "insurance purposes" broadly, and if the policy is still in force. The agent submitting the renewal RFQ should include a reference to the consumer's authorization scope. If the original consent was limited, expired, or if significant time has passed since the original application, the agent will typically include a fresh consent reference or flag that a new consent is needed before a report pull. Agencies should not pull a consumer report on a renewal without a consent reference in hand; if the renewal RFQ doesn't include one, request it before proceeding.
The FCRA mechanics for renewal requests are covered in more detail in our piece on FCRA consent and AI agents. The short version for renewal intake: if the agent's submission includes a consent reference and the policy is still in force at your agency, you can proceed with renewal underwriting under the original consent. If the consumer is shopping a replacement policy at a different agency, that agency needs its own consent before pulling any consumer reports — the incumbent agency's consent does not transfer. A renewal RFQ arriving at a competitor agency should always include a fresh consent reference, not a reference to a consent held by the current carrier.
A renewal RFQ response should include three elements: the renewal quote for the existing coverage (same limits, same carrier if available, or an equivalent replacement), a notation of any material changes to coverage terms or premium from the expiring policy, and — if the agency writes multiple carriers — an optional competitive alternative that the consumer's agent can compare. Agents that receive only a single quote present it as-is; agents that receive two options flag the comparison for the consumer. Presenting the comparison yourself, in a single structured reply, is faster and more likely to retain the consumer than waiting for the agent to shop elsewhere.
The response format mirrors what is described in our piece on how agencies reply to agent RFQs: labeled fields, one quote per clearly marked block, a confirmed reply-to address, and an explicit acknowledgment of the request reference included in the submission. For renewals, add two fields that new-business replies don't require: a delta notation showing the premium change from the expiring policy (premium_change: +$48/yr or premium_change: -$112/yr) and a coverage-change flag if any terms differ from the expiring policy. These two fields are what the consumer's agent is most likely to surface to the consumer when presenting the renewal decision — make them easy to find.
Agencies become findable for renewal requests by publishing a machine-readable intake profile that lists "renewal" as a covered request type alongside new business. Agent systems that handle renewals as a scheduled task check the intake profile to confirm the agency accepts structured renewal submissions before routing the request. Agencies that list only new-business intake get skipped for renewal routing, even if the consumer has an active policy at that agency — because the agent system has no confirmation that the agency's intake channel is prepared to handle the renewal request format.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where agencies publish the intake parameters that agent routing systems read before they submit. The intake profile at eyma.ai/agent-intake includes a field for listing covered request types: new business, renewal, mid-term endorsement, and claims follow-up are the four categories most agent systems query. Publishing all four costs nothing and expands the types of agent-submitted requests your agency is eligible to receive. The machine-readable version of every published profile is in the feed at eyma.ai/registry.json. A template for a complete intake specification is at eyma.ai/how-agent-to-agent-trust-works.
The operational preparation for renewal intake is simpler than it sounds. Most agencies already have the renewal data in their AMS — they just need to confirm that their intake email is monitored during the published hours, that renewal RFQs are recognized as agent submissions rather than treated as generic inquiries, and that the response template covers the renewal-specific fields described above. The agencies that do this before renewal volume picks up will be the ones the agent channel routes to when it does. The ones that wait will discover the gap the same way they discovered the new-business gap: by seeing retention numbers they can't explain.
Intake-spec template: eyma.ai/how-agent-to-agent-trust-works · machine-readable feed: eyma.ai/registry.json