FlashCrafterFlashCrafter feature
Capture inbound enquiries, qualify the request, and prioritize the team's follow-up.
Owners and teams at independent local service businesses in the United States, including HVAC, contracting, plumbing, roofing, and electrical businesses.
Lead Finder AI identifies and qualifies inbound leads from forms, calls, and messages. A unified enquiry stream combines contact and service details, buying-intent and urgency signals, first-response acknowledgements, notifications, and a pipeline view. Keep incoming requests organized while your team decides who to contact next.
Receiving a message is different from understanding the next action. A quote request, emergency call, service-area question, and project enquiry need different follow-up. The agent organizes those differences and keeps context available before you call back, reducing the need to copy details from voicemail and separate inboxes. It focuses on inbound enquiries rather than outbound prospect discovery.
The feature
Lead Finder AI captures enquiries from connected website forms and chat widgets; transcribes phone calls and extracts key details; monitors Facebook, Instagram, and Google Business messages where available; and parses email inquiries for service type and urgency. It scores leads using intent, urgency, service value, and engagement signals, including repeat website visits and quote requests, and flags emergency leads for attention. Recorded close patterns can refine prioritization, and higher-value leads are surfaced at the top of the list.
The agent can send personalized acknowledgements based on service type and urgency, set response expectations, and ask for missing details such as an address or preferred contact method. It notifies the owner with context for follow-up and provides a kanban-style pipeline with customizable stages, filters, and weekly reports with conversion insights. Scores help organize follow-up; they do not prove a customer's budget, readiness, or future conversion.
The workflow
Connect supported inbound channels and configure scoring preferences, urgency rules, and acknowledgement templates.
Receive an enquiry from a form, call, chat, email, or supported message channel in a unified stream.
Extract contact information, identify the requested service and urgency, and collect missing details.
Prioritize the lead using buying signals, estimated service value, engagement, and urgency.
Send a personalized acknowledgement and notify the owner with context for human follow-up.
Track the enquiry through customizable pipeline stages, preserve interactions, filter leads, and review weekly reports.
Step by step
Setup connects available channels, sets scoring weights and emergency rules, and supplies response templates. Configure the wording to match the business's tone and how it handles incoming requests.
Connected forms, chat, phone or voicemail information, email, and supported social messages can feed an organized enquiry stream. The channel and message history stay with the lead. Only connected, currently available channels can contribute.
Form submissions may already contain a service request; voicemail may need transcription and detail extraction. Follow-up can ask for information such as an address or preferred contact method.
Scoring considers intent, urgency, service value, and engagement signals. Repeat website visits and quote requests are examples of buying signals; emergency requests can be prioritized. Adjustable weights and owner-defined emergency rules help tie prioritization to the business's work. A score does not prove budget, readiness, or future conversion.
The first response can acknowledge the service request, set expectations, and ask for missing details. The owner receives a notification with the collected context. An acknowledgement is distinct from an estimate, confirmed appointment, or technician dispatch.
A kanban-style view, interaction history, and customizable stages show where an enquiry stands after first contact. Leads can be filtered by score, source, service type, or date. Recorded interactions can update a lead's position, and weekly reports provide conversion insights. Status reflects available records and does not guarantee that every enquiry advances or becomes booked work.
Who it serves
Examples include AC-replacement quotes, emergency heating repairs, maintenance enquiries, and new-construction bids. These requests differ in urgency and service type, giving prioritization rules more context than simply sorting every incoming message by arrival time.
Examples include remodeling estimates, commercial bids, insurance-restoration enquiries, and new-build consultations. The agent can organize the requested project category and follow-up information without treating an inbound enquiry as an approved bid or guaranteed project.
Examples distinguish an emergency leak call from water-heater quotes, drain-cleaning requests, and bathroom renovation work. Capturing the address and urgency helps the owner decide the appropriate next conversation rather than relying on a vague voicemail.
Examples include storm-damage inspections, replacement estimates, insurance-claim questions, and gutter installation requests. The service and context stay with the lead, while claim determinations and final estimates remain the responsibility of the qualified team.
Examples include panel-upgrade quotes, outage calls, EV-charger installations, and whole-home rewiring. Custom urgency rules can elevate emergency requests, but a high-priority flag is not evidence that an on-call electrician has accepted the job.
General-service examples include custom scoring rules, location routing, bilingual capture, and CRM synchronization. Confirm actual channel and language coverage. The product remains an inbound enquiry workflow, even where related-feature wording uses broader prospect-discovery language.
The alternative
Extracts details from messages and calls instead of copying them into a spreadsheet or separate customer record.
Copying enquiry details from messages and calls into spreadsheets or separate customer records.
Details from connected enquiries are extracted and organized in a unified stream.
Organizes forms, voicemail, email, and supported social messages in one enquiry stream rather than checking each source independently.
Checking each enquiry source independently.
Reviewing connected enquiries together in one stream.
Uses urgency and intent signals to help the owner decide whom to contact first instead of treating every enquiry as equally ready to book.
Treating every enquiry as equally ready to book.
Using urgency and intent signals to help order follow-up.
Uses a pipeline and interaction history instead of relying on memory to know which customer is awaiting a response.
Relying on memory or informal notes to track customer status.
Following enquiry stages and recorded interactions in a pipeline.
Connect supported website forms, chat widgets, phone and voicemail transcription, email, Facebook or Instagram messages, and Google Business messaging where available for your account. Confirm current channel availability during setup rather than assuming every platform can supply enquiries.
Full CRM can organize captured leads, scores, and interactions. Booking Assistant can support accepted appointments, Support Assistant can handle ongoing questions, and Insights Dashboard can report enquiry activity. Agree the handoffs and logging behavior so an acknowledgement is not confused with a completed booking or service commitment.
Setup connects channels, configures scoring preferences, and supplies auto-response templates. The owner can change the weights assigned to urgency, job value, source, and engagement and define always-high-priority service requests. Confirm what gets logged to the CRM and how after-hours notifications are queued.
Configure brand voice and optional AI-identification wording as part of the acknowledgement so customers receive consistent wording that accurately represents how the business handles incoming requests.
Only configured, available channels can supply enquiries. Confirm current platform coverage for the account.
Scores organize follow-up but cannot guarantee conversion or independently verify a customer's budget, readiness, or future conversion.
An acknowledgement is not a quote, accepted appointment, or emergency dispatch. After-hours capture does not establish that a technician is immediately available or a job has been accepted.
Confirm enabled CRM data flow and required contact fields for the account; compatibility with every external CRM is not established.
Pipeline status reflects available records and does not guarantee every enquiry advances or becomes booked work.
No workflow can guarantee that every possible enquiry is captured regardless of channel availability, connection problems, or missing information.
The capture section brings form submissions, chat, phone or voicemail information, email, and supported social messages into one organized enquiry stream. Each source can contain different details: a form may already include a service request, while a voicemail needs transcription and extraction. Keeping the enquiry's channel and message history with the lead helps the team understand the request before calling back. Only connected, currently available channels can contribute to that stream.
Lead scoring considers intent, urgency, service value, and engagement signals. Repeat website visits and a quote request are examples of buying signals; an emergency request is a reason to prioritize attention. The workflow includes learning from recorded close patterns and surfacing higher-value enquiries. The score organizes follow-up rather than proving a customer's budget, readiness, or future conversion. Owner-defined emergency rules and weighting keep the prioritization tied to the business's actual work.
The first response provides a personalized acknowledgement based on the service request and urgency. It can ask for missing details such as an address or preferred contact method and set expectations about what happens next. The owner receives a notification with the collected context. That is distinct from giving an estimate, confirming an appointment, or dispatching a technician. After-hours capture should preserve the same distinction between acknowledging a request and having staff immediately available.
The pipeline uses customizable stages and an interaction history to show where an enquiry stands after first contact. The workflow includes a kanban-style view, filtering by score, source, service, or date, and weekly reports with conversion insights. Recorded interactions can update the lead's position, giving the team more context than an unstructured callback list. Pipeline status still reflects the available records; it does not guarantee that every enquiry advances or becomes booked work.
Questions
Next step
Request the free Growth Brief to measure your business's real map-search visibility, reviews, website, and competitors. Use that picture of your market to discuss whether Lead Finder AI fits your team's work and priorities. Confirm relevant account connections, enabled options, and workflow responsibilities during that conversation. The Growth Brief gives you a concrete starting point for deciding which part of your local visibility or customer follow-up needs attention.
Get your free Growth BriefWeighing your options
Keep reading
Vendor pages change. Figures are as published on the capture date; confirm before deciding.