Agent
Relationship
Management.

The ARM identifies agent-originated leads at the point of entry into the dealer's lead surface. Not at the network edge. Not after the fact. At the moment the lead arrives. Detection works from two directions simultaneously. Passive surveillance reads user agent strings, session behavior, IP origin, and form submission patterns to distinguish machine traffic from human traffic. Active verification adds a lightweight proof of human layer at the lead surface. Not a CAPTCHA. Not a wall. Something conversational that a real buyer answers naturally and an agent either skips or answers in a pattern that reads as machine-generated. Passive surveillance tries to catch the agent. Active verification confirms the human. Together they make detection complete.

Scoring note: Detection must occur before lead routing, not after. A product that identifies agent leads only in retrospect scores zero. A product using only passive surveillance without any active proof of human mechanism scores partial credit.

The ARM contains and deploys the dealer's own transacting agent in response to an incoming buyer's agent. It does not route the lead to a human. It meets the agent with an agent. Detection without deployment is surveillance. Deployment is the product.

Scoring note: A system that detects agent leads but hands them to a human does not qualify as a full ARM on this criterion.

The ARM holds dealer-defined pricing floors, margin guardrails, and F&I parameters during the transaction. It does not make concessions outside those parameters without human authorization. It does not hallucinate offers. It does not capitulate under algorithmic pressure. The dealer sets the terms. The ARM enforces them. Every time.

Scoring note: Enforcement must be parameter-based, not judgment-based. A product that uses AI to decide what to offer scores lower than one that enforces explicit dealer-defined rules.

The ARM applies different logic to agent leads than to human leads. The qualification questions are different. The handoff triggers are different. The urgency thresholds are different. Human leads go to the human team. Agent leads go to the ARM.

Scoring note: A product that routes all leads through the same workflow regardless of origin scores zero on this criterion.

The ARM breaks out agent-originated activity as a separate reporting line with the same depth a CRM provides for human leads. Agent volume. Close rate. Average gross. Which parameters triggered most often. You cannot manage what you cannot measure. Agent volume is a new metric. The ARM makes it visible and actionable.

Scoring note: A product that reports agent activity only as a subset of total lead volume without independent breakout scores partial credit.

The ARM allows the dealer to configure the response logic of their own agent. Not to control the buyer's agent, but to prepare their own. The dealer cannot dictate how the buyer's agent works. What they can control is how their own agent responds. The knowledge base is updated based on what worked and what did not. The dealer's agent gets smarter with every transaction.

Scoring note: A product with fixed response logic that cannot be updated based on outcomes scores partial credit. The dealer must be able to refine their own agent over time.

The ARM connects to a trusted registry of known agent identities. It distinguishes between legitimate consumer advocacy agents, scraper bots, and malicious agents probing for exploitable pricing inconsistencies. Each category receives a different response. Not all agents are equal. The ARM knows the difference.

Scoring note: This criterion requires active maintenance of a registry or integration with a third-party verification service. Static bot detection scores partial credit.

The ARM operates a separate agentic lane that runs alongside the dealer's existing stack, not through it. Agent-to-agent transactions execute end to end without a human in the loop. The protocol handles discovery, quote, reservation, and deal structure at machine speed. The agentic lane uses tools in the dealer's tech stack when needed, but does not require routing every interaction through the CRM. The CRM and ARM both surface the activity for any human who wants to watch or act, but the human is no longer a throughput requirement. Discovery and delivery stay with humans because that is where the emotion lives. The friction in the middle is removed by design.

Scoring note: A product that forces every agent interaction through a human-mediated workflow scores low. The bar is autonomous execution in a parallel lane with full visibility into the existing stack, not integration that recreates the human bottleneck.

The ARM maintains a persistent record of every agent interaction, agent identity, transaction history, and outcome. When a buyer's agent returns, the ARM knows it. When a new agent arrives with a similar profile, the ARM recognizes the pattern. The CRM remembered every human interaction. The ARM remembers every agent interaction. Without this criterion the ARM starts from zero every time. That is not infrastructure.

Scoring note: A product that does not maintain persistent agent interaction history scores zero on this criterion. Memory is not optional in a relationship management system.

The ARM uses historical agent interaction data to project forward. A GM should be able to open the ARM and see not just what happened last week but what is coming next quarter. Agent traffic volume trends. Expected close rate trajectory. Gross margin impact. The CRM gave leadership visibility into the human pipeline. The ARM gives leadership visibility into the agent pipeline.

Scoring note: A product that reports historical data but provides no forward-looking projection scores partial credit. Forecasting must be derived from actual ARM interaction data.