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.
A site enquiry may name a homeowner, a company and an architect in the same message. Creating the first visible name as the customer can split one relationship across records or attach later quotes to the wrong legal party.
Resolve the real construction record
The current Alfie product page positions Alfie as Enfin's construction execution layer. Current application source registers create_customer and classifies this workflow as low risk. This article claims no external integration, autonomous outcome or roadmap capability.
Review one bounded proposal
Search customer names, enterprise or VAT identifiers, email, phone and address. Present the proposed legal identity, operational contact, source and intended project context, and leave uncertain roles unresolved instead of merging them silently.
Separate preparation from execution
Keep the original enquiry and duplicate search with the new record. Creating a customer does not create a lead, deal, quote or project and does not send a message; those decisions remain separate.
Test ambiguity and recovery
Test the workflow with a missing identifier, two records sharing a name, stale source data, insufficient rights and a temporarily unavailable service. Alfie should ask one focused question or leave an unexecuted proposal. A plausible guess is not a safe substitute for the exact customer, project, quote, document, amount or date.
Repeat the review when a party, amount, scope, schedule, recipient or document version changes. Earlier consent is context, not standing permission. Store the request, selected record, useful source fields, user, timestamp, confirmation state and final result without copying unrelated personal or payment data.
Make recovery visible. A colleague who did not prepare the action should be able to reconstruct what was known, which uncertainty remained, what was proposed and whether it was confirmed, executed, rejected or blocked. Define who may correct a mistake and which related quote, project, planning or invoice records need another check.
Run a second-person test before relying on the workflow every day. Change the project, document version or date while a proposal is pending; the old proposal should no longer be executable. This keeps AI interpretation useful while Enfin remains the governed execution layer around identity, permissions, confirmation and audit history.
Keep the commercial path connected
Enfin connects CRM, quotes, projects, planning, tasks, costs and invoicing in one Belgian construction record. Alfie can interpret that context and prepare registered actions within the user's permissions; consequential steps remain reviewable and confirmable. Explore Alfie, compare pricing or discuss your workflow.
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 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.
Approve an invoice inbox item with Alfie after project, amount and duplicate checks
Approving an incoming invoice is a financial decision, not a document-processing shortcut. An AI layer can collect evidence and prepare the decision, but it…