Shared inbox routing

Google Forms shared inbox notification setup

When a Google Form feeds support, admissions, event operations, or internal intake, the response should not sit with one form owner. FormNotifier lets you send owner alerts to a shared inbox or team mailbox, test the setup before launch, and check the latest send result after a submission.

When this setup fits

Use a shared inbox notification when more than one person may need to respond to a form submission.

Support requests

Send each new request to a shared support inbox so the next available person can respond.

Admissions or applications

Route new applications to a reviewer mailbox while keeping the form owner informed.

Event operations

Notify the operations inbox when someone registers, cancels, or asks for help.

Internal intake

Use a team inbox for procurement, IT, HR, facilities, or other forms where ownership rotates.

Setup pattern

  1. Open the Google Form in edit mode and launch FormNotifier from the Extensions menu.
  2. Enable owner alerts for new form submissions.
  3. Put the shared inbox address in the recipient list, then add any extra operator addresses only when needed.
  4. Write a subject line that makes inbox triage easy, such as "New support request: {{Issue type}}".
  5. Keep the email body short and include the fields the shared inbox team actually needs to act.
  6. Run Preflight, save the setup, and send one test email before sharing the public form link.
  7. After the first live response, reopen FormNotifier and check the recent send result.
A shared inbox works best when there is already an owner for the next step. The add-on can send the alert, but the team still needs a process for who claims the request.

What to check before launch

Recipient permission

Make sure the shared inbox accepts mail from your Google account and does not silently route the test to spam.

Copied forms

If the form was duplicated from an older workflow, remove stale recipients before saving the new setup.

Respondent email source

If you also send confirmations, confirm which form field supplies the respondent email address.

Recent send status

Use the latest send result as the first troubleshooting stop if the team says no alert arrived.

Suggested shared inbox email

Keep the message operational. The inbox needs enough context to act, not a long report.

Subject

New form submission: {{Request type}}

Body

New request received.
Requester: {{Name}}
Email: {{Email}}
Priority: {{Priority}}
Summary: {{Summary}}

Fallback line

If any field is missing, open the form response sheet before replying to the requester.

Owner copy

Keep the form owner on the notification when they are accountable for the workflow, even if the shared inbox handles day-to-day triage.

Related guides