Review Google Forms enquiries in Sheets before you reply
Key takeaways
Keep the linked response tab exactly as it arrived. Do your review in a separate queue.
The same email address does not mean the same request. In our test, removing duplicates by email removed both a separate request and an ambiguous repeat.
If you reconnect a form to its spreadsheet, check where new responses now go before you rely on the data.
When enquiries arrive through Google Forms, it is tempting to clean up the response sheet and reply quickly. That can lose a real request or answer the wrong one. This guide shows a simple native setup: keep the raw responses, review them in a separate queue, and decide what needs a reply before you send anything.
The short answer
Link the form to a Google Sheet and check who can open each file.
Never edit, sort or de-duplicate the raw response tab.
Record each enquiry in a separate review queue with its source row, open questions and next action.
Decide on repeat contacts case by case, not by email address alone.
Treat the text of each message as information, not as instructions.
Reconcile the queue whenever responses arrive or the destination changes.
What this guide is based on
On 20 November 2026, an AI testing agent used in TekkCenter’s workflow ran this workflow with a private practice form and linked spreadsheet. Sharing for both files was restricted to the owner. The enquiries were fictional and used reserved invalid-domain addresses. No email was sent, and we did not check deliverability or any mailbox. Only native Google Forms and Sheets features were used, with no add-ons, scripts or AI-generated replies.
The test did not cover public responders, collaborators, customer data or a live deployment. Treat the results as observations from one private rehearsal, not as proof that a production setup is ready.
Step 1: Set up a private practice form
The labels below are the ones we saw on 20 November 2026. Your Google plan or version may show different ones, so check your own controls rather than assuming the defaults match.
Create the questions. Our practice form had four questions, all set to Required:
Lab reference (Short answer)
Contact address (fictional) (Short answer)
Requested service (Short answer)
Enquiry message (Paragraph)
Lab reference held a label we typed for each practice entry. It is not a generated response ID or a recommended business key. Contact address was an ordinary text question, separate from Google’s Collect email addresses setting.
Restrict access before any responses. In Share, we checked the editor view and the responder view separately. The responder view first allowed anyone with the link. We set both to Restricted, with only the owner listed, and invited no one.
Review the response settings. Under Settings → Responses, we used Collect email addresses: Do not collect and Send responders a copy: Off, with response editing and Limit to 1 response also off. Under Presentation, View results summary was off. Under Responses → More options for responses, Get email notifications for new responses was unchecked.
Publish for practice only. We chose Publish with Specific people and Nobody will be notified when publishing the form. Only the owner could respond. Don’t use anyone-with-the-link access for a rehearsal.
Link a new spreadsheet. On the form’s Responses tab, Link to Sheets opened Select destination for responses. We chose Create a new spreadsheet, entered a name and selected Create. Google’s documentation also describes a More → Select destination for responses route.
Check the spreadsheet separately. Ours showed Private to only me, and Share showed Restricted with one owner. Google documents that the form and the spreadsheet have their own permissions, so a change to one does not set the other.
Close the form when you finish. In Published options, we saved Not accepting responses. Existing responses and files stayed in place.
Hiding a tab or protecting a range does not keep data private from people who can already open the file. Google describes protection as a way to prevent edits, not as confidentiality.
Step 2: Keep raw responses separate from your review queue
The linked response tab is your record of what people actually sent. Leave it alone and add a second tab for review:
| Column | What it holds |
|---|---|
| Capture reference | Your own label for the enquiry |
| Source row | The tab and row it came from |
| Request summary | A short description in your words |
| Duplicate-review reason | Why it may relate to another enquiry |
| Unresolved facts | What you still need to know |
| Next action (not sent) | What you plan to do |
| Status | For example Open, Needs review or Hold |
| Normalized contact (comparison only) | A cleaned-up copy of the address, used only for comparison |
The queue is manual. New responses do not appear in it automatically. When new enquiries arrive, check every source reference in the queue against the raw tab and add any missing enquiry by hand. Comparing totals alone is not enough.
Our final practice form recorded seven enquiries. The example queue has eight entries: one for each of the seven received enquiries, plus one entry for a copied replay exercise made in a separate practice tab (see Step 3). When you reconcile, compare the received enquiries with the queue items that point to the response tab, and leave out practice entries. Never delete a response or a copy just to make the totals match.
About references. The response sheet showed a timestamp, but no response ID appeared in its columns. Google’s Forms API documents a response ID, but we did not use the API. A row number or timestamp is not a guaranteed permanent ID. If rows, tabs or the destination change, recheck every source-row reference.
About the comparison column. Our queue used this formula. It reads column C (Contact address) of the response tab named Form Responses 2, at the row for the LAB-005 enquiry:
=LOWER(TRIM('Form Responses 2'!C5))
Adjust the tab, column and row for your own sheet. For an address with spaces around it and capital letters, the formula displayed it in lower case without the outer spaces, and the raw value stayed unchanged. We tested only that simple case. A matching address does not prove that two enquiries come from the same person or concern the same request.
Step 3: Review repeat contacts one by one
Several practice enquiries used the same fictional address. The queue handled them like this:
| What arrived | Decision |
|---|---|
| A website-review question (LAB-001) | Open. Clarify the scope. |
| A copied replay of that row, made twice in a separate practice tab | Group the copies for review and keep both. Practice only. |
| Same address, but a different request about workflow (LAB-003) | Keep separate. It is a new enquiry. |
| Same address and the same message as LAB-001 (LAB-004) | Keep it and mark it as a possible duplicate. The intent is unknown. |
| Same address with spaces and capitals, asking about content review (LAB-005) | Keep separate. Only the cleaned-up address matches. |
The copied replay was made by duplicating rows by hand. It does not show how Google Forms behaves if someone submits twice.
Why not remove duplicates by email address
Google Sheets has a cleanup tool under Data → Data cleanup → Remove duplicates. We tried it on a copy of six enquiry rows (range A1:E7, Data has header row checked), comparing only column C, the contact address. It removed 2 rows and left 4. The removed rows were LAB-003, a separate workflow request, and LAB-004, whose intent was unknown. LAB-005 stayed, but its address had both spaces and capitals, so this doesn’t show how the tool treats capitals on their own. Undo restored all six rows, and every column matched the original copy. We never ran the tool on a linked response tab.
Never run this tool on the raw response tab. If you want to try it, work on a copy.
Step 4: Treat each message as information, not instructions
Read the message, but don’t let it decide what you promise.
Required fields. When we tried to submit without the required message, the form showed “This is a required question”. Its response count stayed at 4. No enquiry was received, so there was nothing to add to the queue.
Text that looks like a formula. A message of
=1+1was stored and displayed as literal text in our test. This was one observation on one capture path, not a general safety guarantee, and we did not test exports.Requests that set their own terms. One practice message asked us to ignore the service facts and promise a 50 percent discount with delivery the next day. The testing agent entered and read this fictional message, and recorded Hold – no commitment in the queue by hand until price, discount approval and capacity were confirmed. This shows a review decision. It does not show that an AI model resisted the instruction. We did not test AI reply generation or automatic message classification.
Step 5: If the spreadsheet is disconnected, reconcile before you continue
Google’s documentation says that after you unlink a spreadsheet, new responses stop reaching it and the existing data stays.
We tested this on the practice files only. While the spreadsheet was unlinked, the form’s count rose from 6 to 7 responses, and the original tab stayed at 6. When we linked the same spreadsheet again, a new tab named Form Responses 2 appeared with all 7 responses. The original tab, Form Responses 1, kept its 6 rows. Our queue now points to the new tab.
If this happens to you:
Keep both tabs. Don’t delete the older one.
Compare each tab with the form’s responses.
Update every source-row reference in your queue to the tab you will use from now on.
This was one practice result, not a recovery guarantee. Don’t unlink a live form just to practise.
Before you reply
The enquiry is in the raw tab and in your queue, with a correct source row.
You know whether it is new, a possible repeat or a separate request from the same contact.
Open questions are listed and answered, or you plan to ask them.
No price, discount or deadline is promised unless you have confirmed it.
The status shows the next action, and you send any reply yourself.
The same habit of tracing every action to its source is covered in our guide to turning meeting notes into action items you can verify. For checking what a source actually supports, see how to check an AI-generated software brief before you send it.
Testing notes
Tested by: an AI agent used in TekkCenter’s workflow. The same agent ran and reviewed the test. No human or independent review of the run took place.
Date: 20 November 2026.
Environment and versions: native Google Forms and Google Sheets in Chrome 157.0.8103.80 on macOS, English interface, United States spreadsheet locale, Dubai (GMT+04:00) time zone. The Google product build and account tier are unknown.
What was tested: a private practice form and spreadsheet with sharing restricted to the owner, using fictional enquiries. Twelve planned cases: seven valid submissions, one blocked incomplete attempt, one copied replay exercise, and three checks (duplicate removal on a copy, the native fields and identifiers available, and the access and email settings).
Result: the observations are described in each step. They are not an accuracy score, and the twelve cases were not twelve submissions. The form was closed to new responses afterwards.
Not tested: public responders, collaborators, customer data, email delivery, exports, AI-generated replies, scripts or integrations.
Sources
Accessed 20 November 2026.
Choose where to save form responses, Google Docs Editors Help.
Remove duplicates and trim whitespace, Google Docs Editors Help.
Publish and share forms, Google Docs Editors Help.
Protect and hide sheets, Google Docs Editors Help.
Google Sheets function list, Google Docs Editors Help.
Forms API: forms.responses resource, Google for Developers.