AutoDev Lead Intake

02 / Challenge

A service request needs a trustworthy handoff, not another lost inbox message.

AutoDev explores how a small service business could collect web and Messenger requests, show what happened to each submission, and keep follow-up visible to its owner. The boundary is deliberate: routing rules organize work, while a person reviews and decides what to do next.

03 / Approach

One intake path records the request and returns a verifiable receipt.

I built the web entry and shared n8n intake workflow, then connected an owner-only queue to Google Sheets, Telegram, Brevo fallback, and a next-day Calendar reminder. Validation, duplicate prevention, stored readback, redacted proof, deletion, and retention behavior were exercised with fictional requests.

• Messenger was demonstrated only through an app-role account, not public Meta access.
• Routing categories are illustrative rules, not AI qualification or CRM synchronization.
• A private human-review queue remains the operational handoff.

04 / Result

Controlled local runs showed the complete handoff and its limits.

The workflow canvases show how the system is built. The queue, Sheet, Telegram, Calendar, and ledger captures show observed states from controlled local tests; the system map is an illustration, not run evidence. The two full-length recordings show the web and app-role Messenger entry paths and private follow-up. There is no public hosted demo yet, and hosted acceptance remains the next gate.