Google Forms Response Receipts: Set Up Client Confirmation

Digital Business / Client intake / Google Forms

To send clients a copy of a Google Forms submission, enable email collection and the form’s response-receipt setting. Pair that copy with a clear on-screen message explaining what happens next. A submission copy should not be presented as approval, payment confirmation, or a reserved appointment.

That distinction matters when a form starts a business process. A client may need evidence of what they submitted, while your team still needs to review availability, prepare a quote, or verify documents. Design the acknowledgement around that gap so neither side mistakes receipt for a completed decision.

This guide describes a desktop setup and a suggested business workflow. Official documentation was checked on 27 October 2026. The examples are hypothetical; no live form, email delivery, or client outcome is claimed to have been tested.

Define what the acknowledgement does for the client

Start by completing this sentence: “After submitting, the client should know…” The answer might be that the enquiry was received, that the submitted details are available for reference, or that a staff member will review the request. Avoid promising a result the form itself does not establish.

Hypothetical example: a design studio collects project enquiries. The acknowledgement says the brief has been submitted for review. A later staff reply confirms whether the studio can take the project. Calling the initial acknowledgement “Your project is booked” would create an expectation before anyone has reviewed the work.

Write the intended meaning down before changing settings. It gives the person configuring the form and the person answering clients the same definition of success.

Set up email collection and the response copy

Google’s response-management instructions document the built-in receipt controls. In the form editor:

1. Open Settings and expand Responses.
2. Enable Collect email addresses, choosing verified collection or manual responder entry.
3. Under Send responders a copy of their response, choose When requested or Always.

Verified collection uses the responder’s confirmed Google Account email. Manual collection relies on an address the person enters. Select around your audience and the address your business needs, then check the resulting experience with a representative client account.

A Google Account address is not necessarily the client’s preferred billing contact. If you need a separate business-contact address, explain its purpose in the form rather than assuming every email field has the same role.

For optional copies, make sure the test participant can recognize the choice. For automatic copies, decide whether sending the submitted information by email fits your process. These are communication decisions as well as configuration decisions.

Write a confirmation message that stands on its own

Google documents a separate confirmation-message setting: in Settings, expand Presentation, edit the confirmation message, and save it. Use this message to state the next step plainly.

A useful message answers three questions: what was submitted, whether anything is still under review, and how the client can obtain help. Add a response timeframe only if someone owns that commitment and can meet it.

Replace the generic contact direction with a real, maintained route in your own form. If the team promises a reply within a stated number of business days, define which working calendar applies and what happens during holidays. Avoid a confident deadline that exists only in the form text.

Read the message as a client would. Words such as “approved,” “confirmed,” and “accepted” can imply more than you intend. Choose language that matches the actual stage of the process.

Review response visibility separately from acknowledgement

The same publishing guidance explains that the results-summary option can expose full-text responses or charts to people who can respond. For client intake, inspect that setting deliberately rather than enabling it to help someone retrieve their own answers.

Publish the form for the intended responders and test that audience’s access. Give clients responder access, not editing access to the form. Google distinguishes collaboration from responding; sharing the editing workspace is a different action from sharing a questionnaire.

Consider the content before offering emailed copies. Do you need detailed personal information, confidential commercial terms, or sensitive attachments at this stage? Remove questions that have no clear purpose. A shorter intake form can reduce both the client’s work and the amount of information your team must handle.

If file collection is part of the process, our Google Forms versus Microsoft Forms upload guide covers the separate account-access and attachment questions. A receipt plan should follow the collection design, rather than deciding which information to request.

Give the team a place to review and resolve submissions

A client-facing copy is only one half of the handoff. Name the person responsible for reviewing requests, the location of the working list, and the point at which a request becomes resolved. Otherwise, clients can receive acknowledgements while the actual work remains unattended.

Google’s response-storage documentation describes viewing responses in the form and saving them to a linked Google Sheet. It also notes that form and linked-sheet permissions need separate attention. Check both when a colleague joins or leaves the process.

Choose a review routine that fits the volume. For a small team, that might be a named owner checking new enquiries each working morning. A busier operation may need assignment, escalation, and a separate case-management system. The important question is who notices an unanswered request.

• One person owns the next action for each enquiry.
• The team can distinguish new, in-review, and completed work.
• Urgent requests have a defined escalation route.
• Staff know how corrections are matched to the original enquiry.
• The confirmation wording matches the team’s actual process.

Keep a simple operating note with the form’s purpose, audience, receipt choice, review owner, and contact route. Revisit it when the service changes, rather than leaving an old promise in a form nobody remembers configuring.

Test the entire handoff with harmless sample data

Use a suitable test form or clearly marked sample submission. Avoid real client details for the initial check. The plan below is a suggested verification routine, not a statement that any particular account has passed it.

Record the test time, selected settings, sample identifier, recipient address, and outcome. If your intake is embedded on a website, repeat the check through that actual entry point. A convenient editor preview does not represent every path a client will use.

After the test, remove sample data according to your process without deleting real submissions. If something changes later, repeat only the checks affected by that change and preserve enough notes to explain the difference.

Handle a missing copy without immediately asking for resubmission

Google warns that spam filters and counter-abuse measures can prevent expected receipts. Do not promise delivery to every inbox.

When a client reports a missing copy, first establish whether your team has the submission. Ask for only enough information to locate it, such as an approximate time and a non-sensitive reference. Check the intended recipient address and ask the client to inspect relevant inbox folders.

If the submission exists, resolve the communication problem without automatically creating another request. If it cannot be found, investigate the access and submission path before deciding that the client must repeat the whole process. Duplicates can create conflicting instructions or extra work.

When you need a branded decision email, approval chain, or delivery audit, define those requirements separately. Evaluate an appropriate workflow tool or carefully managed integration around the missing capability. Do not assume a submission-copy setting satisfies every follow-up requirement.

Frequently asked questions