AccuLynx AI lead intake means an agent watches for every new lead that lands in AccuLynx, checks it against existing contacts, fills in the missing details, drafts a first reply and proposes an inspection slot. AccuLynx already captures and ranks leads on its own. The agent covers the minutes between "lead created" and "someone called back".
This page stays on that one job. For how an agent connects to AccuLynx in general, see how to connect AccuLynx to ChatGPT or an AI agent.
What does AccuLynx already do for lead intake?
More than most owners use. Check these before you pay for anything.
- Lead Intelligence. AccuLynx's built-in AI assigns a Lead Rank to each lead based on demographic, financial and property data, shown on Lead and Prospect records, and you can sort by it. AccuLynx says it is available to all users at no additional cost.
- CallRail. Through the AppConnections add-on, inbound calls and CallRail form submissions create new unassigned leads in AccuLynx with name, phone, city, state, notes and call recordings. You choose triggers (only qualified calls, certain forms or campaigns) and map campaigns to branch locations.
- Zapier and lead apps. The Zapier connection can create a new lead record from a third-party app, and every key you create carries a Lead Source so you can tell Facebook leads from website leads. AccuLynx's integrations page also lists lead connections with Angi, Roofle, SalesRabbit, Spotio and HubSpot. Roofle's RoofQuote PRO, for example, creates unassigned leads from website quote requests.
- A better lead form. The Spring 2026 update redesigned the lead form with "possible matches" to catch duplicates, custom fields, and side-by-side calendars for booking the first appointment.
- Automated texts. The Automation Manager can send a text, send an email or assign a task when a job event happens, such as an appointment being set.
If your problem is "leads are typed in by hand," turn on CallRail or Zapier first. That alone may be enough.
Where does lead intake still break in AccuLynx?
Capture is usually solved. What breaks is the next ten minutes. Leads land in Unassigned Leads and wait for a person to notice. A homeowner who called last year about a gutter repair comes in again as a new lead. A web form says "hail, need inspection" with no phone number. A storm brings forty leads before lunch and the rank helps you sort them but doesn't call anyone.
A rank also isn't a reply. Lead Intelligence tells you who to call first. It doesn't text the homeowner, ask whether they've filed a claim, or offer Thursday at 10.
What does an AI agent add to AccuLynx lead intake?
The agent does the clerical part of intake the moment the lead arrives, and hands a person a ready decision.
| Step | AccuLynx on its own | What the agent adds | Who approves |
|---|---|---|---|
| Capture | CallRail, Zapier and lead apps create unassigned leads | Catches leads that arrive by email or voicemail and creates them through the API | No one, it's data entry |
| Duplicate check | "Possible matches" on the lead form when a person enters it | Searches contacts by phone, email and address for every lead, including ones created by integrations | Office manager merges |
| Missing details | Empty fields stay empty | Drafts a short question for the homeowner (address, insurance or retail, roof age) | Office manager sends |
| Priority | Lead Rank | Adds what the lead said: active leak, storm date, claim filed | Sales manager |
| First reply | Fixed automated text if you set one up | A reply that answers what this homeowner asked | Office manager sends |
| Assignment | A person assigns from Unassigned Leads | Suggests the rep by territory and calendar | Sales manager confirms |
How does it work, step by step?
- The lead arrives. AccuLynx's API index lists webhook topics for a contact added and a job created. Zapier lists the same events as Contact Added and Job Created triggers.
- The agent reads it. Through the API it pulls the contact, the lead source and any notes CallRail passed in. It searches existing contacts for the same phone number or address.
- It drafts. A first reply, a question for anything missing, and a suggested rep and time.
- A person approves. The office manager sees the draft and the facts behind it in one place, edits if needed, and sends.
- It writes back. The agent logs what happened on the contact and posts a note to the job's message feed so the rep sees the context.
For leads that come in by email or a form with no integration, the agent can create the record itself. AccuLynx's Create Job endpoint creates a job in the Lead milestone with no assigned representative, linked to an existing contact, so it shows up exactly where your team already looks.
A worked example
This is an illustration of the pattern, not a client result.
A hailstorm passes through on Tuesday afternoon. At 7:40 p.m., a homeowner fills out the website form: "Hail last night, think we have damage, insurance is State Farm." The form is connected through Zapier, so AccuLynx creates an unassigned lead with Lead Source "Website".
- The agent finds an existing contact with the same phone number: a 2023 gutter estimate that never closed. It flags the duplicate instead of letting a second record exist.
- It notes the storm date, the insurance mention and the missing street number.
- It drafts a text: "Hi Karen, this is Summit Roofing. Sorry about the hail. We can inspect Thursday at 10 or Friday at 2. What's the street address? If you've already opened a claim, have the claim number handy."
- It suggests assigning Mike, who covers that zip code and has Thursday open.
At 7:42 the office manager's phone shows the draft. She approves it. Karen picks Thursday. The rep walks in knowing about the old gutter estimate.
What should stay with a person?
- Anything about insurance coverage. The agent can ask whether a claim exists. It should never tell a homeowner what insurance will pay.
- Price. No numbers in a first reply.
- Merging records. The agent flags duplicates. A person merges them.
- The first weeks of sends. Start with every reply approved. Loosen it for after-hours acknowledgments only once you've read enough drafts to trust them.
Where it falls short
- Phones without CallRail. If calls don't flow into AccuLynx, a missed call never becomes a lead. Fix that first; see missed call text back.
- Texting. The AccuLynx API lists no endpoint for sending a text to a homeowner. Replies go out through AccuLynx's own messaging or your phone system, which the build has to account for.
- Double messages. If an Automation Manager text and the agent's reply both fire on a new lead, the homeowner gets two. Pick one per step.
- Storm volume. AccuLynx allows 10 API requests per second per key. That's plenty for intake, but a careless build that re-reads every contact on each lead will hit it during a storm.
Storm leads have their own timing problems, which we cover in AI for roofing storm leads. For why the first reply's speed matters so much, see website form speed to lead.
Where Cortex fits
Cortex builds lead intake agents on the AccuLynx API with their own named key, read access plus the few writes intake needs, and a person approving every reply until you decide otherwise. We aren't an AccuLynx partner, and if CallRail plus an automated text covers your volume, we'll say so. See how this fits a roofing company, or start with the free AI Operations Audit.
