Create a construction lead from a site enquiry with Alfie after review
Turn a site, phone or WhatsApp enquiry into one traceable lead after checking identity, project context, consent and ownership.
A new enquiry may arrive as a photo, voicemail, forwarded message or brief site conversation. Creating a CRM lead too early can duplicate an existing customer; waiting too long loses the source and promised follow-up. Alfie can structure the request, while a governed lead-creation step protects identity, ownership and the next action.
Preserve the enquiry source
Record the original channel, date, sender and exact request. Separate facts supplied by the prospect from staff assumptions about budget, timing or project type. If a colleague forwarded the message, keep the original contact details and note who has permission to reply.
Search existing leads and customers by company number, email, phone and address. A spelling variation should not create a second commercial history.
Prepare the minimum useful lead
A useful proposal contains name or company, contact route, site location when relevant, requested work, source, responsible colleague and next action. Unknown fields stay unknown. Do not invent a project value or qualification score from a short message.
Restrict sensitive photographs or personal details to roles that need them. The CRM summary can link to evidence without copying everything into free text.
Review the creation action
Show possible duplicates, proposed owner and the first follow-up before saving. Alfie interprets the request, while Enfin remains the governed execution layer. The current action catalogue defines what can be done, organisation context limits which records are visible, and a preview makes the real effect reviewable. The model does not receive independent authority to change company data. Missing or conflicting evidence should stop the flow for clarification.
Creating a lead is distinct from creating a customer, quote or project. Each transition has a different data standard and business effect. A request to summarise the enquiry should not silently trigger any of them.
Close the loop with one owner
After creation, send only the communication that the user separately authorises. Give the follow-up a date and cancel it when the prospect responds. Preserve lost or disqualified reasons so later reporting reflects real demand rather than deleted records.
Use the broader lead-to-quote CRM guide and explore Alfie in Enfin for governed commercial actions.
Final control before closure. For “Create a construction lead from a site enquiry with Alfie after review”, review four points together. Is the source current and attached to the correct customer, quote, invoice or project? Does the user have authority for this exact change? Are uncertain fields, conflicts and missing evidence still visible? Does the result name an owner for the next step? Record exceptions in the business file, not only in a separate conversation. Another colleague should be able to distinguish what was proposed, what was confirmed and what was deliberately left unknown. Test the flow with a wrong record, a duplicate document and a withdrawn instruction as well. A governed action should stop before execution in each case and let the user correct the proposal safely.
Create a construction customer with Alfie after a VAT and duplicate review
Resolve the legal customer, contact source, project context and duplicate risk before creating a reusable construction CRM record.
Create invoices from several quotes with Alfie after a batch scope review
Review every accepted quote, customer, billable line and duplicate risk before a governed construction invoice batch is prepared.
Create a site task from a message with Alfie after confirming scope and owner
Turn an unstructured site request into one named task with project, owner, due date and evidence before it enters planning.