Before: every enquiry is handled manually.
- Find the message and copy the information.
- Check whether the enquiry already exists.
- Draft a reply and keep a record.
A customer enquiry, from start to finish.
Discover a practical method for collecting an enquiry, preparing follow-up and keeping control.
Educational simulation. This page has no connection to Google, Make or AI. No messages are sent.
After: a prepared record, a human decision.
- An identified, structured input.
- A duplicate stopped before another write.
- A draft reviewed before any message is sent.
Hypothesis to measure: reducing handling from 8 to 3 minutes over 80 enquiries gives 6 h 40 gross hours per month. Review, maintenance and exceptions still need deducting. This is fictional, not a customer result.
The workflow in 36 seconds
Explanatory video with on-screen text, without sound. Full transcript below.
InputCheckDuplicateRegisterDraftApproval
Your first exercise: a reliable enquiry register
Allow about 15 minutes. Use the simulator below with fictional data. No account, payment or external tool is needed.
- Reset the simulator, then process D001 with its example email and need. Check that exactly one row is created.
- Click “Test duplicate”. Check that there is still one row.
- Click “Test missing field”. Check that the incomplete enquiry is rejected.
- Read the draft. Which action is needed before sending it?
Standard learning worksheet, not a certificate. If the download does not start, open the file directly.
Expected result and explanation
One row for D001; no extra row for the duplicate; rejection when email is missing. Human review is required before any send. This simulation handles one request at a time: it does not prove duplicate safety under concurrent real requests.
Try the three essential cases
Simulation register
| ID | Status |
|---|
Draft to review
—Data stays in this page only and resets on reload.
Reproduce the pilot with your tools
Computer, Google and Make accounts required. Any subscriptions are your responsibility. Interface labels can change. This tutorial prepares a supervised pilot; it does not configure your accounts automatically.
1. Prepare two tables
In a test Google Sheet, create Input and Register tabs. Headers: request_id, email, need, status, draft. Keep rows continuous without blank gaps. Use fictional data only.
2. Collect enquiries in one place
Start by entering a test row in Input. For a form, add email and need questions in Google Forms and link responses to Sheets through Responses. Every request needs a stable identifier; for this pilot, assign D001, D002 and so on manually.
3. Trigger the scenario
In Make, create a scenario and add Google Sheets > Watch New Rows. Connect your account, choose the file and Input tab, and enable column headers. Test with a new row. This module checks on the chosen schedule; do not promise instant processing.
4. Validate the data
Add a filter allowing only rows with request_id, email and need populated. For this pilot, manually check the email address. Leave rejected rows in Input for correction rather than deleting them.
5. Check duplicates
Use Google Sheets > Search Rows in Register to search for the exact request_id. Configure continuation when the search returns no result. Found route: do not create a new request. No-result route: create it with Add a Row. Keep this pilot sequential: search-then-add does not guarantee uniqueness under concurrent executions.
6. Map fields and status
In Add a Row, map request_id, email and need to the matching columns. Set status to review needed. Start with a fixed draft asking for more details. Do not add a sending module to this first scenario.
7. Add AI after collection works
Once collection works, prepare a draft in an assistant using the prompt below and fictional data. Copy it into draft. This manual step checks meaning before any API connection. Do not send real customer data without an appropriate framework.
8. Test and hand over the pilot
Test a valid row, a repeated ID, a missing field and a disconnected account. Check Register and Make execution history. Document recovery, permissions and the owner. Enable scheduling only after validation. A person reviews and sends messages outside this pilot.
Starter prompt
Draft a short reply using the supplied need. Thank the person and ask for necessary details. Do not invent any price, deadline, commitment or missing information. List points to review. Need: monthly maintenance. Human approval required.
Your acceptance test
- Valid D001: one row needing review.
- D001 repeated: no new row.
- D002 without email: stop and request a correction.
- Disconnected account: no sending, incident documented.
Official resources checked on 3 October 2026: Google Forms → Sheets · Make : premier module · Make : modules Sheets
Does this first project fit your needs?
The full course adds two more projects, service costing, handover templates and an answered assessment.
Notify me when it opensNo payment required. No income guaranteed.
Help us make this project clearer.
After trying it, tell us which step was confusing or what you need to reproduce the pilot.
Feedback stored privately to improve the course. Do not enter personal or confidential information. No email required.