# Carrier-request AI agent | Working Pace Canonical: https://workingpace.com/work/carrier-request-agent Updated: 2026-10-22 - [Home](https://workingpace.com/) - [Selected work](https://workingpace.com/work) - Carrier-request AI agent Client work · Commercial insurance # Carrier requests. Without the chase. A custom operations system for a commercial insurance brokerage, connecting client signatures, carrier follow-up, incoming documents, exception review and CRM updates. [Explore the workflow](#workflow-demo) Image: A recreated request, retrieval, follow-up and review scene using fictional records. 8.0% → 39.4% Request completion within 60 days 4.9× Original completion rate Observed during May–August 2026. Completion means every required loss run received from every carrier. See the result section for context. Explore the workflow ## One request. The whole context. This walkthrough recreates the project’s workflow with fictional account details. 01Authorize02Retrieve03Follow up04Review ### Start with the client’s approval. The request identifies the client, required carriers and policy years. The workflow coordinates the authorization and signature before carrier actions proceed. Authorization received - 01Harbor Operations · fictional account - 02Required: 2023, 2024 and 2025 loss runs - 03Approved request · ready for carrier collection ### Connect replies to the records needed. The agent interprets incoming email and attachments. The workflow matches available records to the request and keeps missing years visible. Two records received - 012025 loss run · matched to this request - 022024 loss run · matched to this request - 032023 loss run · still outstanding ### Keep the missing item moving. The agent follows up for the outstanding record within the configured communication rules. The request history retains the message and its context. Follow-up sent - 01To: carrier team - 02Still needed: 2023 claims history - 03Please confirm availability for the authorized request. ### Give your team the exception, with context. An unavailable record does not quietly become a completed request. A person receives the missing item, the carrier response and the actions already taken. Ready for team review - 012023 record unavailable · carrier response retained - 022024 and 2025 records attached to request - 03Your team decides the appropriate next step ## The challenge: a sent request was not a completed request. The brokerage needed verified claims-history documents from every relevant carrier before the team could move the account forward. Completion depended on client authorization, policy years, carrier replies and missing information. The work was fragmented across communication and records. People had to reconstruct what had been requested, which documents had arrived and what still needed follow-up. ## The build: one connected request lifecycle. The delivery work covered workflow mapping, requirements, implementation coordination, quality assurance, rollout and adoption across sales and operations. The system coordinates client signatures, carrier follow-up, incoming emails and attachments, exception review and CRM updates. AI interprets email and document context. Deterministic rules govern authorization and state changes. Image: A connected request lifecycle with an agent retrieving records and returning an unavailable record for team review. ## The agent keeps the outstanding work moving. After authorization, the workflow identifies the required carrier records and keeps communications tied to the request. Incoming responses and attachments are matched to the relevant work. Missing records remain outstanding rather than disappearing behind a sent status. The agent handles follow-up within the configured workflow. An unavailable record or uncertain response routes back to a person with the context and actions already taken. - Coordinate client authorization and signatures - Request and retrieve the required carrier records - Interpret replies and connect attachments - Follow up on missing items and route exceptions Image: An agent follow-up kept with the original request and its missing record. ## The observed result: 8.0% to 39.4% completion. During the May–August 2026 production window, the reported completion rate rose from an 8.0% baseline to 39.4%, approximately 4.9 times the original rate. Completion means receiving all required loss runs from all of the client’s insurance companies within 60 days of the initial request for client approval. The project owner confirmed the definition and reporting window. This is an observed result for one brokerage workflow, not a controlled estimate of AI’s isolated effect or a forecast for another business. Discovery for a new implementation establishes its own baseline and completion rules. ## What a new implementation would need. The carrier landscape, authorization process, agency systems and operating rules vary by business. We would validate those inputs before proposing a similar system. Start with one redacted request. We can map where the work waits, which steps can be automated and which decisions belong with your team. [Explore automation for commercial insurance](https://workingpace.com/industries/commercial-insurance) Keep exploring ## A useful next step. [Commercial insurance](https://workingpace.com/industries/commercial-insurance)[Loss run automation](https://workingpace.com/solutions/loss-run-automation)[AI agent development](https://workingpace.com/services/ai-agent-development)[How to automate loss run requests](https://workingpace.com/guides/loss-run-automation-guide) Start where you are ## A useful first conversation. Tell us about your business and the work you would like to improve. No finished technical brief needed. [Talk with Working Pace](https://workingpace.com/book) --- Contact: jake@workingpace.com Book a conversation: https://workingpace.com/book