Add a customer note from a WhatsApp photo with Alfie and preserve its source

Attach only the relevant photo context to the correct customer and project while keeping identity, permissions and follow-up explicit.

Enfin editorial team3 minute read

A photo of a defect, finish choice or measurement can arrive in a busy WhatsApp conversation with no project number. Saving it under the wrong customer creates false evidence that may influence a quote or site decision.

Resolve the real construction record

The current Alfie product page positions Alfie as Enfin's construction execution layer. Current application source registers add_customer_note and classifies this workflow as low risk. This article claims no external integration, autonomous outcome or roadmap capability.

Review one bounded proposal

Resolve sender, customer and project before proposing the note. Show the selected media, concise context, date and requested follow-up, and exclude unrelated chat content or people from the record.

Separate preparation from execution

Keep source and uploader with the note. Adding evidence does not approve a variation, create a task, message the crew or invoice the work. Convert those outcomes only through separate reviewed actions.

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.

All articles