Concept project · Workflow automation
One intake path for every lead source, so nothing is retyped and follow-up does not rely on memory.
An intake pipeline for a business taking leads from a website form, a shared inbox and a social inbox. Every enquiry is captured once, matched against existing records, written to the CRM with its source and owner, and given a dated follow-up task. Duplicates merge instead of multiplying, and a failed step says so.
Concept project: an illustration of the build, not a client site.
01
Leads arrive from a website form, a shared inbox and a social inbox. Someone retypes each one into a spreadsheet, and sometimes into the CRM as well. The same person appears as three records with three different spellings, nobody is certain which list is current, and follow-up happens when a person remembers — which, in a busy week, means it does not.
02
A single intake path. Every enquiry, whatever its source, is captured, matched against existing records, written to the CRM with its source and an owner, and given a dated follow-up task. Duplicates merge instead of multiplying, and when a step fails it says so loudly rather than dropping the lead.
What was built
An enquiry arrives from a form, an inbox or a social message.
It is normalised into one shape: name, contact, source, message, timestamp.
The system looks for an existing record by email and phone.
A match updates the existing record; a near-match is flagged for review; anything else creates a new one.
The outcome
A working demonstration in which leads from several sources land as single, attributed records with follow-up tasks attached, and failures surface instead of disappearing. Built against test data; no client deployment, so there is nothing measured to report.
