Scattered intake risk
Without a structured form, client requirements could become scattered across emails, manual notes, and separate planning documents.
Case Study
HL Tech Insight needed a simple, reusable way to collect Smart Contact Router client intake details, notify the internal team, and acknowledge the client without manually checking form responses.
The Problem
Smart Contact Router Setup was becoming a productized HL Tech Insight service. That meant the service needed more than a public-facing offer page. It needed a structured client intake workflow.
Without a structured form, client requirements could become scattered across emails, manual notes, and separate planning documents.
HL Tech Insight needed to know when a new intake was submitted without manually checking the response sheet.
A professional service should acknowledge the client and explain what happens next after intake is submitted.
The goal was to create a lightweight but reliable intake notification workflow that could support the first step of the Smart Contact Router delivery process.
Scenario 0 was not designed to be a full CRM. It was designed to be a clean onboarding trigger for a productized automation service.
Once a client intake is submitted, the workflow starts the path toward scope review, route mapping, tracker planning, Make.com build work, testing, UAT, and handover.
Tools Used
| Tool | Role in the Workflow |
|---|---|
| Google Forms | Collected structured client intake responses. |
| Google Sheets | Stored the form responses in a response sheet. |
| Make.com | Watched for new rows and ran the automation workflow. |
| Microsoft 365 Outlook | Sent internal notification and client acknowledgement emails. |
| Smart Contact Router Delivery Kit | Provided the service process behind intake, scope, testing, UAT, and handover. |
Workflow Architecture
The workflow begins when a Smart Contact Router intake form is submitted and ends with both an internal notification and a client acknowledgement email.
Google Form submission
→ Google Sheets response row
→ Make.com Watch New Rows
→ Valid intake filter
→ Microsoft 365 Outlook internal notification
→ Client email exists filter
→ Microsoft 365 Outlook client acknowledgement
Filters
Scenario 0 uses filters to avoid sending emails from incomplete intake responses.
The first filter checks that the response contains the minimum fields needed to continue.
Business name is not empty
AND Primary contact email is not empty
AND Website URL is not empty
AND Client approval confirmation is not empty
The second filter checks that a client acknowledgement email can be safely sent.
Primary contact email is not empty
During testing, the Google Form successfully submitted responses into Google Sheets. However, the Make.com Google Sheets trigger initially failed during row parsing because the header row range was configured too broadly.
Initial setting:
A1:DJ
Corrected setting:
A1:DJ1
After correcting the range to the exact header row, the scenario ran successfully end-to-end.
Current Result
Scenario 0 is now working as a reusable intake notification pattern for Smart Contact Router Setup.
The client submits the Smart Contact Router intake form with website, contact, routing, tracker, and approval details.
Make.com detects the new Google Sheets row and sends an internal notification with key intake details.
The client receives confirmation that their intake was received and that the next step is scope review.
Why It Matters
This workflow is small, but strategically important. It turns Smart Contact Router Setup from a simple service idea into a repeatable delivery process.
Client details are collected consistently before the project moves into scope and route planning.
HL Tech Insight receives an internal notification instead of relying on manual response sheet checks.
The client receives an acknowledgement email with clear next-step expectations.
The same workflow can support future Smart Contact Router clients and other intake-based services.
The workflow connects the public service page with the backend delivery kit and SOP system.
Scenario 0 becomes a proof point for the Smart Contact Router Client Delivery Kit.
Delivery Kit Connection
Scenario 0 is the first automation bridge in the broader Smart Contact Router Client Delivery Kit.
Client Intake Form collects the starting information for the project.
Scope Checklist converts client answers into project boundaries.
Route Mapping Worksheet defines how submissions should be classified and handled.
Tracker Setup Plan defines fields, statuses, follow-up logic, and handover needs.
Make.com Build Checklist and Testing Log guide implementation and QA.
Client UAT Checklist and Handover Note help the client approve and operate the workflow.
This case study is shared for educational and service demonstration purposes.
The workflow improves intake handling, internal visibility, response consistency, and onboarding structure. It does not guarantee leads, sales, revenue, rankings, conversions, email deliverability, or platform uptime.
Every client workflow should be scoped, approved, tested, and reviewed before go-live.
Related Resources
Explore the dedicated service page for website enquiry automation, routing, tracking, and follow-up support.
See how HL Tech Insight uses AI, automation, and smart website workflows to support practical digital systems.
Read the broader AI Services Contact Router case study that helped shape this service offer.
Start Here
HL Tech Insight can help turn your basic website form, client intake form, or lead magnet request into a structured workflow with routing, tracking, internal notifications, user acknowledgements, follow-up support, and handover documentation.
Best starting point: share your website URL, current contact form page, main enquiry types, and whether you already use Google Sheets, Supabase, Outlook, Make.com, or another workflow tool.