When the ECD slips — because a radar bracket is backordered, because the adjuster sat on the supplement for 72 hours, because the calibration failed on the first dynamic drive — four systems go out of sync. The SMS shows the new date. The Enterprise ARMS portal still thinks the rental expires Friday. The CCC insurer portal has no notation. The customer has no idea. Somebody at the shop swivels between four browser tabs for fifteen minutes to reconcile them, and gets interrupted twice before the job is done. Agent 03 watches the ECD field. When it changes, it extends the rental, posts the justification to the carrier, and texts the customer — all in the same second, all with matching codes, all with an audit trail.
The customer's rental car authorization is a legal artifact. When the adjuster writes the initial estimate and approves the ECD, the insurer's rental coverage expires on that exact date. If the vehicle is not finished and the shop has not affirmatively extended the rental through the proper carrier and rental-vendor channels, the customer starts paying out of pocket at roughly $45 a day. The phone call that follows — "I thought you said it would be done Friday and now Enterprise is charging my credit card" — is where customer satisfaction scores collapse and Google reviews turn into litigation referrals.
Preventing this outcome is, on paper, simple. In practice, it is one of the most miserable administrative rituals in the shop. When the ECD changes in CCC ONE or Mitchell RepairCenter — and ECDs change constantly; Q4 2025 CCC data shows the average moderate-severity repair experiences 1.8 ECD slips before delivery — the estimator or CSR must:
armsweb.ehi.com, sort by "Past Due" or "Due Today," find the customer, and manually extend the "Last Day" field. Input a justification code from a fixed-dropdown list.Each of those four systems lives behind its own login. None of them share data bidirectionally. The CSR is doing copy-and-paste translation across four browser tabs, and doing it for every ECD slip on every active job. A mid-sized MSO with 120 vehicles in process will see 40–60 ECD slips a month. At 12–18 minutes per reconciliation, that is 10 to 18 hours of purely mechanical swivel-chair work.
It gets worse. If the CSR forgets one of the four steps — because the phone rang, because a customer walked in, because the estimator needed help — the entire chain breaks. The rental lapses. The insurer's system still shows the old ECD. The customer calls in anger. The shop eats the rental overage as a goodwill concession. The friction of a siloed technology stack becomes a direct line item on the P&L.
Every ECD slip is four manual actions across four different authenticated systems. Miss one, and the customer's credit card pays for the shop's administrative failure.
Agent 03 fires on a single event: the ECD field on an active workfile is updated to a date later than the current rental authorization expiration. The event is detected via SMS webhook (CCC ONE's workfile update events or Mitchell RepairCenter's OData change feed) or, for SMS platforms without webhooks, a 60-second polling loop over active workfiles with rental coverage.
The payload includes the workfile, the old and new ECD, the declared delay reason, the customer contact profile, the rental vendor, the rental authorization reference, and the insurer plus DRP program.
// Trigger payload (normalized ECD-change event) { "eventType": "workfile.ecd.changed", "workfileId": "WF-2026-041532-A", "shopId": "SHP-7741", "customer": { "name": "Jordan Ramirez", "mobile": "+15125550183", "smsOptIn": true }, "ecd": { "previous": "2026-04-18", "updated": "2026-04-23", "delayReasonCode": "PART_BACKORDER", "delayDetail": "OEM radar bracket ETA 04/21" }, "rental": { "vendor": "ENTERPRISE", "authId": "ARMS-9918772-A", "currentLastDay": "2026-04-18" }, "carrier": { "id": "STATEFARM-DRP-T3", "portal": "CCC_ESTIMATE_REVIEW" }, "changedAtUtc": "2026-04-15T16:04:12Z" }
Agent 03 is the most integration-heavy agent in the catalog because it is the only one that writes to four systems in parallel. The routine is orchestrated with strict ordering (rental first, so the customer is never uncovered) and bounded retries. If any leg fails, the agent rolls the remaining legs back to a safe state and flags a human.
Pull customer contact info, current rental authorization, carrier portal target, and the free-text delay reason. Map the delay reason to two parallel taxonomies: the rental vendor's code set (ARMS "Parts Delay" vs. HIRS "Waiting on Parts") and the carrier's accepted narrative format.
Authenticate into Enterprise ARMS or Hertz HIRS using a shop-scoped service credential. Locate the authorization by ID. Update the Last Day field to the new ECD. Enter the justification code. Confirm the portal returns a success response and capture the confirmation ID.
Using the CCC ONE communications API (or Mitchell Connect or Solera XpertEstimate depending on the carrier's preferred channel), post a structured note: delay reason, supporting evidence reference, new ECD, rental confirmation ID from Leg A. Attach the evidence PDF (backorder confirmation, calibration failure report) if one exists on the workfile.
Through the shop's SMS gateway (Twilio, Podium, or equivalent), send a templated message: new ECD, rental extension confirmed, the shop's direct line. Personalize with the customer's first name and the vehicle description. Log the outbound message ID for two-way threading.
If all three legs succeeded, write a single structured record to the agent audit log linking the three confirmation IDs and the original ECD event. If any leg failed — most commonly the rental portal throwing a rate limit or a carrier portal requiring MFA re-auth — roll the remaining legs back to safe states and flag the job for human intervention via Slack or email.
The shop operator sees a single line in the Agent 03 audit feed: "ECD moved 4/18 → 4/23 on WF-2026-041532-A. Rental extended. Carrier notified. Customer texted. All confirmations captured." Below is what those three downstream systems actually received, rendered as they would appear to a human opening each one.
All three updates posted within 11 seconds of the ECD change. Audit trail captures confirmation IDs from each system. The CSR is not involved.
Agent 03 returns value on three axes. The first two are hard dollars: admin time reclaimed and customer rental-overage charges eliminated. The third is harder to price but matters more — the customer experience differential between "I had to call the shop three times to figure out what was happening" and "I got a text before I even knew there was a problem."
Combined hard-dollar value: roughly $880/month per shop, or $10,560/year. This excludes the much larger secondary effect — Google review scores, repeat-business rates, and DRP scorecard CSAT metrics that influence the shop's claim volume in the next cycle.
Agent 03 is the only agent a shop owner can hand a customer directly. "We texted you before you had to call us" is the single most durable differentiator against the consolidator down the street.
This agent integrates the most external systems and therefore carries the most integration risk. The architecture isolates each portal behind a dedicated connector so outages or credential expirations in any one leg do not cascade.
| Function | Endpoint / Source | Auth Model |
|---|---|---|
| ECD change detection (CCC) | CCC Secure Share workfile webhook | OAuth 2.0 + API key |
| ECD change detection (Mitchell) | OData change feed, 60s poll fallback | OAuth 2.0 + client cert |
| Enterprise rental extend | armsweb.ehi.com shop-service API | Shop-scoped service credential |
| Hertz rental extend | HIRS partner API | HIRS partner credential |
| CCC portal notation | POST /communications/estimate-review | OAuth 2.0 |
| Mitchell portal notation | POST /api/v1/Communications | OAuth 2.0 + client cert |
| Customer SMS | Twilio /Messages or Podium outbound | Account SID + auth token |
| Evidence attachment | Shared with Agents 01/02 attachment API | SMS OAuth |
| Audit log sink | Internal event store + shop dashboard | Private, shop-scoped |
The routine emphasizes ordering (rental first, always), idempotency (retries are safe), and rollback discipline (partial success is not success).
// Agent 03 — Routine: status_synchronizer_v1.3 MISSION When an Estimated Completion Date on an active workfile moves beyond the current rental authorization, synchronize the new date across the rental vendor portal, the carrier portal, and the customer's phone — with matching audit references. INPUT - ecd_event.json (old/new ECD, reason code, reason detail) - workfile.json (vehicle, customer, rental, carrier) - shop_config.json (rental credentials, portal creds, SMS gateway, templates) STEPS 1. Guard: abort if new ECD <= current rental last day. 2. Guard: abort if customer.smsOptIn is false AND no other communication channel is configured. 3. Build justification strings from reason code: - ARMS/HIRS code (vendor-specific taxonomy) - carrier narrative (plain English + evidence ref) - customer SMS copy (friendly, first name, rental confirm) 4. LEG A — Rental extend: a. Authenticate to ARMS or HIRS per workfile.rental.vendor. b. Patch Last Day to new ECD. c. Post justification code. d. Capture confirmation ID. If non-2xx, abort entire run. 5. LEG B — Carrier portal notation: a. Post structured note to carrier portal with new ECD, reason, rental confirmation ID from Leg A. b. Attach evidence PDF if present on workfile. c. Capture note ID. If fails, roll back Leg A (revert rental last day) and flag human. 6. LEG C — Customer SMS: a. Render template with first name, vehicle, new ECD, rental vendor name. b. Send via configured gateway. c. Capture message SID. If fails, do NOT roll back prior legs (customer will be reached via phone fallback). Flag human for manual outreach. 7. Write audit record: event ID, three confirmation IDs, rendered SMS copy, runtime, any soft failures. CONSTRAINTS - Never extend a rental to a date beyond DRP coverage cap. If new ECD exceeds cap, flag human; do not silently commit the shop to uncovered liability. - Never send a second SMS for the same ECD event (idempotency by workfile + new ECD hash). - Never log customer PII in plaintext audit records. - Every external call is retry-safe with exponential backoff; max 3 retries per leg. - If MFA challenge is returned by any portal, flag human immediately. Do not attempt automated MFA defeat. OUTPUT SCHEMA { workfileId: string, previousEcd: date, newEcd: date, legA: { vendor, authId, confirmationId, latencyMs }, legB: { portal, noteId, latencyMs }, legC: { channel, messageSid, latencyMs, rendered }, rolledBack: boolean, humanFlagged: boolean, flagReason?: string, totalRuntimeMs: number }
Agent 03 has the highest integration complexity in the catalog and the longest go-live (roughly 6 weeks) because of the rental-portal credential provisioning and the carrier-specific communication API nuances. Deployment follows a deliberate phased rollout.
Provision Enterprise ARMS and Hertz HIRS shop-service credentials (these are issued by the rental vendor partner-integrations team; lead time 5–10 business days). Configure SMS gateway. Subscribe to CCC workfile webhook or Mitchell change feed. Establish the shop's rental + SMS audit log in the agent's configuration store.
Run in shadow mode: the agent detects ECD changes and generates the three proposed updates (rental, carrier, SMS) into a preview dashboard, but does not execute. The shop's lead CSR reviews each proposed run daily and tunes the SMS copy templates and the carrier narrative phrasings for local customer voice.
Week 5: live on rental extension only (Leg A). Week 6: add carrier portal notation (Leg B). End of week 6: enable customer SMS (Leg C). Staging the customer-facing leg last is intentional — it is the highest-trust action and the most sensitive to tone.
Weeks 1–2: credential provisioning (the gating factor; start first). Weeks 3–4: shadow mode + template tuning. Week 5: rental leg live. Week 6: carrier + customer legs live. First full month of captured value lands in month 2.
The customer SMS goes live last. A wrong number, wrong name, or wrong tone in week one destroys a decade of word-of-mouth. The agent earns the right to speak to customers by being boringly reliable on rental and carrier first.