Renewal outreach, FNOL intake, and new business — connected to EZLynx.
WFW connects to EZLynx API. Renewal calls go out at 60/30/10 days with actual policy data. FNOL calls create structured claim records in EZLynx before the call ends. New business inquiries become applicant records.
GLBA NPI handling and CFPB communication guardrails built into every call. Your producers focus on high-value conversations — not routine outreach.
Live Data Flow — FNOL Call
GLBA/CFPB compliance built in
NPI never stored in WFW. Call timing and disclosures follow CFPB guidelines automatically.
Capabilities
What this integration enables.
Three concrete capabilities unlocked by connecting WFW to EZLynx.
Live Data
Policy Renewal Outreach at 60/30/10 Days
WFW queries EZLynx for policies expiring in 60, 30, and 10 days and initiates automated outbound calls at each interval. Each call references the client's actual policy number, coverage type, and expiration date — not a generic renewal reminder.
Live Data
FNOL Call Handling → EZLynx Claim Creation
When a policyholder calls to report a loss, the agent guides them through first notice of loss collection — incident date, description, location, and involved parties. The FNOL details are extracted and a claim record is created in EZLynx before the call ends.
Live Data
New Business Intake → EZLynx Applicant Record
Inbound calls from prospects generate structured applicant records in EZLynx. The agent collects coverage type, current carrier, effective date, and key risk data — enough for the agent to run a quote on first contact.
Data Flow
How it works.
From client identification to structured EZLynx record — what moves on every call.
Client identified in EZLynx
For inbound calls, the caller's phone number is matched to a client record in EZLynx. The agent has access to the client's policy numbers, coverage types, carrier, and renewal dates in full context before the first response.
Renewal cadence triggered from EZLynx data
WFW queries EZLynx daily for policies in the 60/30/10-day expiration window. Outbound calls are queued and initiated via POST /v2/calls/initiate, with each call script referencing the specific policy details from the client's EZLynx record.
FNOL details extracted and structured
During a loss reporting call, WFW extracts incident date, type of loss, property or vehicle description, claimant contact, and any witnesses mentioned. These structured fields write directly to the EZLynx claim record — reducing manual data entry.
Extraction data available for agent review
GET /v2/calls/{id}/extractions returns FNOL details, renewal response, or new business intake data — structured for the producer or CSR's review in EZLynx. All NPI is handled per GLBA standards throughout.
Use Cases
Before and after.
Real insurance agency workflows transformed by the EZLynx + WFW integration.
Before
Renewal reminders sent via email — open rates around 20%. Producers manually calling high-value renewals at the 30-day mark. Mid-tier clients often lapse silently.
After
WFW calls every renewing policyholder at 60, 30, and 10 days. Clients who express intent to shop are flagged in EZLynx for immediate producer follow-up. Retention improves across all tiers.
Before
Claim calls come in at unpredictable hours. After-hours claims result in voicemails that delay FNOL submission, frustrate clients, and occasionally miss carrier reporting windows.
After
WFW answers every FNOL call 24/7, collects structured loss data, and creates the claim in EZLynx immediately. Morning staff see a complete FNOL record — not a vague voicemail message.
Before
Inbound prospect calls that reach voicemail or a busy CSR are frequently lost. The cost per acquired lead is high when conversion rates from first contact are low.
After
WFW answers every new business inquiry, collects coverage type, current carrier, and risk data, and creates an EZLynx applicant record. The producer calls back with enough data to quote on the first conversation.
Technical Details
Integration specifications.
API connection, data fields, renewal cadence, and GLBA/CFPB compliance posture.
| Connection method | EZLynx API — REST over HTTPS |
| Auth method | EZLynx API credentials stored encrypted in WFW vault |
| Data pulled from EZLynx | Client record, policy numbers, coverage types, expiration dates, carrier, premium history |
| Data written to EZLynx | FNOL claim records, applicant intake records, renewal call notes, client contact updates |
| Renewal cadence | 60/30/10-day windows — configurable per agency in WFW agent settings |
| Compliance | GLBA NPI handling: data never persisted in WFW. CFPB communication guidelines followed for call timing and disclosure language. |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once EZLynx is connected. Trigger renewal outreach campaigns, pull FNOL extraction data, and monitor agency call performance via the WFW REST API.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger renewal outreach call from EZLynx policy expiration data
/v2/calls/{id}/extractionsRetrieve FNOL details or new business intake data extracted from the call
/v2/agents/{id}Check agent health and EZLynx connection status
Setup
Connect EZLynx in three steps.
API credentials, renewal window configuration, agent activation. Done.
Add EZLynx credentials
Enter your EZLynx API credentials in WFW admin under Integrations → EZLynx. Encrypted and stored in the WFW vault per GLBA data security requirements.
Configure renewal windows
Set your renewal outreach cadence (default: 60/30/10 days) and which policy types receive each outreach call. Per-line-of-business configuration available.
Enable on your agent
Toggle EZLynx active on your agent. Renewal outreach, FNOL handling, and new business intake go live from the first call.
Get Started
Connect EZLynx to your voice agents.
Renewal outreach, FNOL intake, and new business capture — all automated through live EZLynx data. GLBA/CFPB compliant. No middleware required.
Connect EZLynxQuestions? Talk to our team →