Email every support request to your shared inbox
Each support request arrives as an internal email, CC'd to the on-call rep, with the customer set as Reply-To.
New support request submission
Gmail sends an internal email to your shared support inbox, CC'd to the on-call rep
One-directional. A submission triggers the action — nothing is written back into your form.
Support teams that already live in Gmail do not want a second place to check. This flow keeps the queue where it is: a submission becomes an ordinary email in the shared inbox — threaded, searchable, and answerable with a keyboard shortcut.
The part that earns its keep is Reply-To. Because the customer's address sits in that header rather than buried in the body, hitting reply writes to the customer, not to the Zap. Small SaaS teams and one-person support desks run this before they buy a helpdesk, and often instead of one.
Setting it up
- 1
Publish the support form with Subject and Message required — they become the email's subject line and body, and an empty one is hard to triage.
- 2
In Zapier, start the Zap with the formformform New Submission trigger and select the support form.
- 3
Add the Gmail Send Email action, connected to an account allowed to send as your support alias.
- 4
Put the shared support address in To and the on-call rep in CC, so one person owns the response without the thread being hidden from the team.
- 5
Map Email Address into Reply-To, not into To. This is the step that lets a teammate answer the customer straight from the thread.
- 6
Build the subject as "Support:" plus Subject, so everything arriving from the form sorts together and can be filtered.
- 7
Lay the body out with Full Name, Phone Number and Message on separate lines rather than one run-on paragraph, so the first responder can scan it.
- 8
Send a test submission, reply to it from Gmail, and confirm the reply reaches the test address before turning the Zap on.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Gmail |
|---|---|
| Email Address | Gmail Reply-To header, so replies reach the customer |
| Subject | Email subject line, behind a "Support:" prefix |
| Message | Body of the email, quoted in full |
| Full Name | Body — the name the responder greets |
| Phone Number | Body — the fallback contact if the thread stalls |
Variations worth knowing
Add a Zapier filter that looks for "down", "charged twice" or "refund" in Message. Matching submissions get a second Gmail action with URGENT in the subject and the team lead in CC; everything else takes the normal path.
Include the submission's date and time from the trigger step in the subject line. Two messages from the same person then never look identical in the thread list, and a teammate can quote the reference back when asking for more detail.
If something isn't arriving
Reply-To is empty or the customer's address was mapped into To. Open the Gmail action, put your support alias back in To and map Email Address into Reply-To only, then send a test and hit reply on it.
CC the single on-call address rather than the whole team, and have responders reply-all so the thread shows who took it. Gmail groups the replies under the original, which is enough ownership signal for a small queue.
Frequently asked questions
Can this replace a helpdesk tool?
For a low-volume queue, often yes — you get a thread per request, search, and labels. What you do not get is ticket status, assignment or response-time reporting. Teams usually move on when they need those, not before.
Does the customer see who is CC'd?
Yes. CC is visible to everyone on the message, including the customer if they are ever added to the thread. Use BCC for the on-call rep instead if you would rather keep internal routing private.
Can an agent update the submission from Gmail?
No. The integration is one-directional — the submission triggers the email and nothing travels back. Notes and status changes stay in Gmail; the original response in formformform remains exactly as it was submitted.
Related automations
- Confirm every RSVP with the joining details
Registrants get a confirmation carrying the joining details, and the organiser mailbox is BCC'd on every one.
- Email an order confirmation to every buyer
Every order form submission sends the buyer a confirmation listing what they ordered and how it will reach them.
- Route feedback to the right team and label it
Feedback reaches the alias that owns it, labelled and laid out so a triage pass takes seconds.
- Send an instant reply to every new lead
Every quote request gets a personalised reply from your Gmail account within seconds of the form being submitted.
- Stage each application as a draft for the hiring manager
Each new application lands as a Gmail draft addressed to the hiring manager, filled in and waiting for a human to press send.
- Add every event signup to your Outlook contacts
Everyone who registers is written into your Outlook address book with their phone, employer and job title already filled in.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free