How to Route Google Form Submissions to Different People Based on Answers

Blogs How to Route Google Form Submissions to Different People Based on Answers

Morgan Hopkins

Mar 10, 2026

Google Forms has no built-in way to send submissions to different people based on the answers provided. Every notification goes to the form owner, regardless of what the respondent selected. With the Fast Forms add-on, you can dynamically route each form submission to the right person using Google Sheets lookup tables and routing conditions — so that a help desk ticket goes to the correct support team, a purchase request goes to the correct department head, or an incident report goes to the correct regional manager, all automatically.

Consider a common scenario: an IT help desk form. Employees submit tickets for hardware issues, software problems, network connectivity, and account access. Each category is handled by a different specialist or team. Without routing, every ticket lands in the same inbox, and someone has to manually read it, figure out who should handle it, and forward it. That manual step introduces delays, creates bottlenecks, and inevitably leads to tickets falling through the cracks. The solution is to route each submission automatically to the right person based on the data in the form response.

Two Ways to Route Submissions with Fast Forms

Fast Forms provides two complementary routing mechanisms: dynamic recipients via Google Sheets lookup tables, and routing conditions that control whether a specific recipient receives a notification. You can use either one independently, or combine them for more sophisticated routing logic.

Dynamic Recipients with Google Sheets Lookup Tables

A lookup table is a simple mapping stored in a Google Sheet that connects a form response value to a recipient's email address. When a form is submitted, Fast Forms reads the response, looks up the corresponding value in the table, and sends the notification to the matched email address.

Here is how it works with the IT help desk example. Your Google Form has a dropdown question called "Issue Category" with options like Hardware, Software, Network, and Account Access. In the linked Google Sheet, you create a lookup table on a separate tab with two columns:

Issue Category (Column A)	Recipient Email (Column B)
Hardware	hardware-team@company.com
Software	software-team@company.com
Network	network-team@company.com
Account Access	accounts-team@company.com

When an employee submits a help desk ticket and selects "Network" as the issue category, Fast Forms looks up "Network" in Column A, finds the corresponding email address in Column B (network-team@company.com), and sends the notification to that address. Each submission is routed to the right team without any manual intervention.

The power of using a spreadsheet as the lookup source is that it is easy to maintain. When a team lead changes, when a new category is added, or when responsibilities are reassigned, you update the spreadsheet and the routing changes take effect immediately for all future submissions. There is no need to reconfigure the form or the add-on. For full setup instructions, see our support article on adding recipients.

Routing Conditions for Targeted Delivery

While lookup tables determine who receives the notification, routing conditions determine whether a specific recipient receives it at all. A routing condition is a rule attached to a recipient that evaluates the form response data and either includes or excludes that recipient from the notification.

Continuing the IT help desk example: suppose you want the IT Director to be notified only when an employee marks a ticket as "Critical" priority. You would add the IT Director as a recipient and attach a routing condition that says: only send to this recipient if the answer to "Priority Level" equals "Critical." For all other priority levels, the IT Director does not receive a notification, and the ticket is handled by the assigned team as usual.

Routing conditions can evaluate text values, numeric values, and selections from dropdown or multiple-choice questions. You can set conditions like "equals," "does not equal," "contains," "greater than," and other comparison operators. Each recipient can have its own independent set of conditions. For detailed setup instructions, see our support article on adding recipient logic.

Combining Lookup Tables and Routing Conditions

The real power of Fast Forms routing emerges when you combine both mechanisms on the same form. Here is a more complete version of the IT help desk example:

Dynamic team routing: A lookup table maps the "Issue Category" response to the correct support team email address. Hardware tickets go to the hardware team, software tickets go to the software team, and so on.
Escalation for critical tickets: The IT Director is added as a separate recipient with a routing condition that triggers only when "Priority Level" equals "Critical." This means the IT Director is notified about critical tickets in any category, while normal and low-priority tickets are handled by the teams without escalation.
Respondent confirmation: The employee who submitted the ticket is added as a recipient using the email address collected by the form. They receive a personalized confirmation email with their ticket details, regardless of category or priority.

With this configuration, a single form submission can trigger up to three separate notifications — each with its own personalized content — all routed automatically based on the form response data.

Step-by-Step Setup

Here is how to set up dynamic routing with both lookup tables and routing conditions:

Create your Google Form with the questions you need. For routing to work, include at least one question whose answer determines who should receive the notification (such as a department, category, location, or email address field).
Link a Google Sheet to your form by clicking the Responses tab and then the spreadsheet icon. If a spreadsheet is not already linked, follow the prompts to create one.
Create a lookup table. In the linked Google Sheet, add a new tab. In Column A, list the possible values for your routing question (e.g., department names, issue categories, or employee email addresses). In Column B, list the corresponding recipient email addresses.
Install Fast Forms from the Google Workspace Marketplace, then open your Google Form and launch the add-on from the puzzle piece icon.
Add a dynamic recipient. In the add-on, add a dynamic recipient and select the form question that should determine the recipient. Then click the lookup table icon next to the recipient, and select the sheet tab you created in Step 3.
Add routing conditions (optional). For any recipient that should only receive notifications under certain circumstances, add a routing condition specifying the question, the comparison operator, and the value to match.
Personalize the notification. Customize the subject line and email body for each recipient using data markers. This ensures each person receives a notification that is relevant and useful to them. See our guide on personalizing notifications for details.
Save and test. Save your configuration in the add-on, then submit a test response that matches your routing criteria. Verify that the correct recipients received the correct notifications.

Real-World Examples Beyond IT Help Desk

Multi-location operations: A restaurant chain uses a Google Form for daily opening checklists. Each store manager selects their location from a dropdown. A lookup table maps each location to the regional manager's email address, so the regional manager automatically receives the checklist from every store in their region. When a store reports a health and safety issue, a routing condition sends an additional notification to the compliance officer.

Employee onboarding: A human resources team uses a Google Form to collect new hire information. The form includes a "Department" dropdown. A lookup table routes the notification to the correct department head. A routing condition ensures that if the new hire selects "Yes" for the question "Do you require IT equipment?" then the IT provisioning team also receives a notification with the employee's name, start date, and equipment requirements.

Customer intake: A professional services firm uses a Google Form for new client intake. The form asks which service the client is interested in. A lookup table routes the submission to the appropriate practice lead. A routing condition ensures that if the estimated project value exceeds a certain threshold, a senior partner is also notified.

School administration: A school district uses a Google Form for parent communication requests. The form includes a "School" dropdown. A lookup table maps each school to the principal's email address. When a parent marks the request as "Urgent," a routing condition also notifies the district superintendent. For more on using Google Forms in education, see our post on Google Forms for schools.

Why Spreadsheet-Based Routing Beats Hard-Coded Recipients

Some automation tools require you to hard-code recipient email addresses into the form configuration. This works fine when your organization is small and stable, but it becomes a maintenance burden as you grow. Every time someone changes roles, joins the company, or leaves, you have to update the form automation.

With Fast Forms, the routing logic lives in a Google Sheet that anyone with access can update. When a regional manager is replaced, you update one cell in the spreadsheet and the change takes effect immediately. When a new department is created, you add a row. When responsibilities shift, you rearrange the mappings. The form itself never needs to be touched. This separation between the form and the routing rules makes the system easier to maintain, especially in larger organizations where dozens or hundreds of people are mapped to different recipients.

Frequently Asked Questions

Can I route submissions to more than one person at the same time?
Yes. You can add multiple recipients to the same form, each with their own lookup table and routing conditions. A single form submission can trigger notifications to several different people simultaneously.

What happens if a form response value does not match anything in the lookup table?
If the submitted value does not have a match in the lookup table, no notification is sent to that dynamic recipient for that particular submission. You should make sure your lookup table covers all possible response values for the question you are routing on.

Can I use routing conditions without a lookup table?
Yes. Routing conditions and lookup tables are independent features. You can use routing conditions on static recipients (where the email address is entered directly) to control whether they receive notifications based on form response values.

Do I need to know how to code to set up routing?
No. Fast Forms is a no-code add-on. Both lookup tables and routing conditions are configured through a visual interface within your Google Form. The lookup table is a standard Google Sheet — no formulas, scripts, or APIs required.

How much does Fast Forms cost?
The Free plan supports up to 30 notifications per month at no cost. The Individual plan is $4/month when billed annually, and the Team plan is $24/month when billed annually. You can install Fast Forms from the Google Workspace Marketplace.

Ready to route your Google Form submissions automatically?

Install Fast Forms from the Google Workspace Marketplace and start routing submissions to the right people today. With over 4,000,000 installs and plans starting at Free, you can set up dynamic routing in minutes.