Postal Code Routing with Routing Forms
Learn how to route leads to different team members or destinations based on their postal code or ZIP code
Need to route leads to regional sales reps or service teams based on their location? meetergo's routing forms make it easy to direct visitors to the right person based on their postal code (ZIP code, PLZ, or postcode).
Why Use Postal Code Routing?
Postal code routing is essential for businesses with:
- Regional sales territories - Route leads to the rep responsible for their area
- Service coverage areas - Direct customers to technicians who serve their location
- Franchise networks - Connect visitors with their local franchise
- Multi-office operations - Guide clients to the nearest office location
Setting Up Postal Code Routing
Step 1: Create Your Routing Form
- Go to Routing & Funnels
- Click New Routing Form & Funnel
- Enter a name like "Regional Sales Routing"
- Click Create Form
Step 2: Add a Postal Code Field
- In the form builder, add a new field
- Choose Text Field as the field type
- Label it appropriately (e.g., "Postal Code", "ZIP Code", or "PLZ")
- Make it a required field to ensure you always capture this information
Consider adding placeholder text like "e.g., 10115" or "e.g., 90210" to guide users on the expected format.
Step 3: Create Routing Rules
Add one route per region in the Routing Logic tab, each with a condition on your postal code field and a destination such as that region's meeting type. Setting Up Routing Conditions walks through adding a route step by step. What matters for postal codes is which operator you pick.
Using "Starts With" for Regional Routing
The Starts With operator is the right choice for postal code routing because postal codes are hierarchical: the first digits represent larger regions. A condition of Postal Code Starts With 1 catches every code in the Berlin region.
Example: German PLZ Routing
In Germany, the first digit of a PLZ indicates a major region:
- 0xxxx = Eastern Germany (Dresden, Leipzig)
- 1xxxx = Berlin region
- 2xxxx = Hamburg & Northern Germany
- 3xxxx = Hannover region
- 4xxxx = Düsseldorf region
- 5xxxx = Cologne region
- 6xxxx = Frankfurt region
- 7xxxx = Stuttgart region
- 8xxxx = Munich region
- 9xxxx = Nuremberg region
Create one route per digit you serve, and repeat for each region you want to cover.
Using "Contains" for Specific Areas
To match specific postal codes inside a region, use Contains instead, for example Postal Code Contains 101 for a group of Berlin districts.
Using Numeric Comparisons for Ranges
For purely numeric postal codes such as US ZIP codes, the numeric operators let you route by range. To catch West Coast leads, combine two conditions in one route: Postal Code Greater Than 89999 and Postal Code Less Than 100000. Both conditions in a route must be true, so the route matches only ZIP codes in the 9xxxx block.
Step 4: Set Up Fallback Route
Configure the fallback route so that unexpected postal codes and international visitors still land somewhere useful, for example a general sales meeting type or a contact form. See The Fallback Route.
Advanced Postal Code Routing Strategies
Sending Several Prefixes to the Same Team
Conditions inside one route are combined with AND, so a single route cannot match "starts with 1 or starts with 2". To send both the Berlin (1xxxx) and Hamburg (2xxxx) regions to the same Northern Germany team, create two routes, one per prefix, and point both at the same meeting type. See Routing Conditions.
Combining with Other Criteria
Postal code routing works even better when combined with other qualification criteria:
- Company size + Location - Route enterprise leads in specific regions to senior reps
- Service type + Location - Direct installation requests to local service teams
- Budget + Location - Qualify leads before regional routing
Priority-Based Routing
Because the first matching route wins, order your postal code routes from narrow to broad: an exact code like 10115 for a VIP area above the broader 1 prefix for the rest of Berlin, with the fallback at the bottom.
Real-World Examples
Example 1: Insurance Sales Territories
An insurance company with regional agents:
| Route | Condition | Action |
|---|---|---|
| 1 | PLZ starts with 8 | → Munich Agent |
| 2 | PLZ starts with 7 | → Stuttgart Agent |
| 3 | PLZ starts with 6 | → Frankfurt Agent |
| Fallback | - | → General Sales Team |
Example 2: Home Service Company
A home service company with coverage limitations. Since conditions inside a route are combined with AND, each prefix gets its own route, all pointing at the same destination:
| Route | Condition | Action |
|---|---|---|
| 1 | ZIP starts with 90 | → Schedule Installation |
| 2 | ZIP starts with 91 | → Schedule Installation |
| 3 | ZIP starts with 92 | → Schedule Installation |
| 4 | ZIP starts with 93 | → Schedule Installation |
| Fallback | - | → "Sorry, we don't service your area yet" message |
Example 3: Multi-Office Law Firm
A law firm with offices in different cities:
| Route | Condition | Action |
|---|---|---|
| 1 | PLZ starts with 1 | → Berlin Office Calendar |
| 2 | PLZ starts with 2 | → Hamburg Office Calendar |
| 3 | PLZ starts with 8 | → Munich Office Calendar |
| Fallback | - | → Virtual Consultation |
Best Practices
- Keep it simple - Start with broad regional routing and refine over time
- Test thoroughly - Use various postal codes to verify your routing works correctly
- Document your territories - Maintain a reference of which postal codes go where
- Review regularly - Update routes when territories change or new team members join
- Use clear labels - Name your routes descriptively (e.g., "Northern Region - Hamburg Team")
FAQ
Can I route international postal codes?
Yes! The Starts With and Contains operators work with any postal code format, including alphanumeric codes like UK postcodes (e.g., "SW1" for Central London).
What if someone enters an invalid postal code?
Invalid or unrecognized postal codes will fall through to your fallback route. Consider adding validation hints in your form or using the fallback to request clarification.
Can I have multiple team members for one region?
Yes! When setting the route action, you can redirect to a round-robin meeting type that distributes leads among multiple team members in that region.
How do I handle leads from outside my service area?
Use your fallback route to either show a "not in service area" message, redirect to an alternative resource, or collect their information via a contact form for future expansion.
Can I update routes without recreating the form?
Absolutely! You can edit routing rules anytime. Changes take effect immediately for new form submissions.
Need help setting up your postal code routing? Check out our Getting started with Routing Forms & Funnels guide for the basics.
Was this article helpful?
Let us know if this article answered your questions.
Related articles
- Form Template MarketplaceStart a new form from a ready-made template, or share one of your own forms as a public template others can copy.
- Getting started with Routing Forms & FunnelsBuild a routing form on the Premium plan, add fields and pages, set booking or fallback routes, then publish and share it.
- How to Route Leads Based on CRM Data (New vs. Existing Customers)Use routing forms with HubSpot integration to automatically identify existing customers before booking
- How to Route New vs. Existing Customers to Different TeamsUse routing forms to pre-qualify visitors and direct them to the right team based on customer status