One Form Link for Support, Sales, Press: Route Messages Using URL Metadata

Use a single contact form across your entire site while tracking sources and routing messages intelligently.

Why One Form is Better Than Many

The Multiple-Form Problem

Common but inefficient approach:

• Create separate form for Support
• Create separate form for Sales
• Create separate form for Press
• Create separate form for Partnerships
• Create separate form for each landing page

Problems:

• Maintaining multiple forms
• Inconsistent styling
• Multiple dashboards
• Scattered conversations
• Duplicate effort
• More to test and update

The One-Form Solution

Single form with URL parameters:

• One form to maintain
• Consistent appearance
• Centralized conversations
• Single dashboard
• Easy updates
• Context-aware routing

How it works:

<!-- All point to same form, different parameters -->
<a href="https://supportretriever.com/form/your-form-id?type=support">Support</a>
<a href="https://supportretriever.com/form/your-form-id?type=sales">Sales</a>
<a href="https://supportretriever.com/form/your-form-id?type=press">Press</a>

The parameters appear in your conversation metadata, so you know exactly where each message came from.

How URL Parameters Work

Adding Parameters to Your Form Link

Base form URL:

https://supportretriever.com/form/your-form-id

Add parameters with ? and &:

https://supportretriever.com/form/your-form-id?source=homepage
https://supportretriever.com/form/your-form-id?source=homepage&type=sales
https://supportretriever.com/form/your-form-id?type=support&priority=high

Syntax:

• First parameter: ?key=value
• Additional parameters: &key=value
• Use URL-safe characters (no spaces)

Parameters You Can Add

Common parameter names:

Parameter	Purpose	Examples
source	Page or location	homepage, footer, blog, pricing
type	Message type/department	support, sales, press, partnerships
topic	Specific subject	bug, feature, billing, account
priority	Urgency level	high, medium, low
product	Which product	pro, enterprise, starter
page	Specific page	pricing, features, about
campaign	Marketing campaign	launch2026, holiday, referral
team	Team member	john, sarah, support-team

You can use any parameter names that make sense for your business.

How Parameters Appear in Conversations

In Your Dashboard

When someone submits through a form link with parameters, the metadata appears in the conversation:

How to Use Metadata

1. Identify message type instantly

• See department (support, sales, press)
• See priority level
• See source page
• Understand context before reading

2. Route to the right team member

• Support messages → support team
• Sales inquiries → sales team
• Press requests → PR contact
• Billing issues → billing department

3. Prioritize responses

• High priority → respond first
• From pricing page → likely buying
• From blog post → research phase
• From error page → urgent issue

4. Track conversion sources

• Which pages generate most leads
• Which campaigns perform best
• Which content drives inquiries
• Which CTAs work best

Copy-Paste Examples for Common Links

Website Footer

<footer>
  <nav>
    <a href="https://supportretriever.com/form/your-form-id?source=footer&type=support">
      Support
    </a>
    <a href="https://supportretriever.com/form/your-form-id?source=footer&type=sales">
      Sales
    </a>
    <a href="https://supportretriever.com/form/your-form-id?source=footer&type=press">
      Press
    </a>
    <a href="https://supportretriever.com/form/your-form-id?source=footer">
      Contact
    </a>
  </nav>
</footer>

Metadata you'll see:

• source: footer
• type: support | sales | press (or none)

Navigation Menu

<nav class="main-nav">
  <a href="/">Home</a>
  <a href="/features">Features</a>
  <a href="/pricing">Pricing</a>
  <a href="https://supportretriever.com/form/your-form-id?source=nav">
    Contact
  </a>
</nav>

Metadata you'll see:

• source: nav

Support Page

<div class="support-page">
  <h1>Need Help?</h1>
  
  <div class="support-options">
    <a href="https://supportretriever.com/form/your-form-id?type=support&topic=bug" 
       class="support-card">
      <h3>Report a Bug</h3>
      <p>Something not working? Let us know.</p>
    </a>
    
    <a href="https://supportretriever.com/form/your-form-id?type=support&topic=feature" 
       class="support-card">
      <h3>Request a Feature</h3>
      <p>Tell us what you'd like to see.</p>
    </a>
    
    <a href="https://supportretriever.com/form/your-form-id?type=support&topic=account" 
       class="support-card">
      <h3>Account Issues</h3>
      <p>Problems with your account?</p>
    </a>
  </div>
</div>

Metadata you'll see:

• type: support
• topic: bug | feature | account

Pricing Page

<div class="pricing-page">
  <!-- After pricing tiers -->
  
  <div class="pricing-cta">
    <h2>Have Questions?</h2>
    <a href="https://supportretriever.com/form/your-form-id?source=pricing&type=sales" 
       class="button-primary">
      Talk to Sales
    </a>
  </div>
  
  <p style="margin-top: 20px;">
    <a href="https://supportretriever.com/form/your-form-id?source=pricing&topic=billing">
      Questions about billing?
    </a>
  </p>
</div>

Metadata you'll see:

• source: pricing
• type: sales (or none)
• topic: billing (if used)

Contact Page

<div class="contact-page">
  <h1>Get in Touch</h1>
  
  <div class="contact-departments">
    <div class="department">
      <h3>Customer Support</h3>
      <p>Get help with your account or product.</p>
      <a href="https://supportretriever.com/form/your-form-id?source=contact&type=support">
        Contact Support →
      </a>
    </div>
    
    <div class="department">
      <h3>Sales & Partnerships</h3>
      <p>Interested in our products or partnering?</p>
      <a href="https://supportretriever.com/form/your-form-id?source=contact&type=sales">
        Contact Sales →
      </a>
    </div>
    
    <div class="department">
      <h3>Press & Media</h3>
      <p>Press inquiries and media requests.</p>
      <a href="https://supportretriever.com/form/your-form-id?source=contact&type=press">
        Contact Press →
      </a>
    </div>
    
    <div class="department">
      <h3>General Inquiries</h3>
      <p>Everything else.</p>
      <a href="https://supportretriever.com/form/your-form-id?source=contact">
        Contact Us →
      </a>
    </div>
  </div>
</div>

Metadata you'll see:

• source: contact
• type: support | sales | press (or none)

Blog Posts

<!-- At end of blog post -->
<div class="blog-post-cta">
  <p>
    Have questions about this article? 
    <a href="https://supportretriever.com/form/your-form-id?source=blog&page=how-to-reduce-spam">
      Get in touch
    </a>
  </p>
</div>

Metadata you'll see:

• source: blog
• page: how-to-reduce-spam

Error Pages

<!-- 404 page -->
<div class="error-page">
  <h1>Page Not Found</h1>
  <p>The page you're looking for doesn't exist.</p>
  <a href="https://supportretriever.com/form/your-form-id?source=404&priority=high">
    Report this broken link
  </a>
</div>

Metadata you'll see:

• source: 404
• priority: high

Email Signatures

<div class="email-signature">
  <p>
    <strong>John Smith</strong><br>
    Customer Success Manager<br>
    <a href="https://supportretriever.com/form/your-form-id?team=john&source=email-signature">
      Contact me
    </a>
  </p>
</div>

Metadata you'll see:

• team: john
• source: email-signature

Advanced Routing Patterns

By Product

<!-- Product A page -->
<a href="https://supportretriever.com/form/your-form-id?product=productA&type=support">
  Get Support
</a>

<!-- Product B page -->
<a href="https://supportretriever.com/form/your-form-id?product=productB&type=support">
  Get Support
</a>

Route internally based on product parameter.

By Customer Tier

<!-- For enterprise customers -->
<a href="https://supportretriever.com/form/your-form-id?tier=enterprise&priority=high">
  Contact Enterprise Support
</a>

<!-- For free tier users -->
<a href="https://supportretriever.com/form/your-form-id?tier=free">
  Contact Community Support
</a>

Prioritize based on tier parameter.

By Campaign

<!-- Holiday campaign -->
<a href="https://supportretriever.com/form/your-form-id?campaign=holiday2026&type=sales">
  Claim Your Holiday Offer
</a>

<!-- Product launch -->
<a href="https://supportretriever.com/form/your-form-id?campaign=launch-v2&type=sales">
  Learn About v2
</a>

Track campaign performance with campaign parameter.

By Language/Region

<!-- English page -->
<a href="https://supportretriever.com/form/your-form-id?lang=en&region=us">
  Contact US Support
</a>

<!-- Spanish page -->
<a href="https://supportretriever.com/form/your-form-id?lang=es&region=mx">
  Contactar Soporte MX
</a>

Route to appropriate language support.

Copy-Paste Template

Replace your-form-id with your actual form ID, then customize parameters:

<!-- BASE TEMPLATE -->
<a href="https://supportretriever.com/form/your-form-id?[PARAMETERS]">
  [LINK TEXT]
</a>

<!-- COMMON PATTERNS -->

<!-- Footer -->
<a href="https://supportretriever.com/form/your-form-id?source=footer">
  Contact
</a>

<!-- Support -->
<a href="https://supportretriever.com/form/your-form-id?type=support">
  Get Help
</a>

<!-- Sales -->
<a href="https://supportretriever.com/form/your-form-id?type=sales&source=pricing">
  Talk to Sales
</a>

<!-- Urgent -->
<a href="https://supportretriever.com/form/your-form-id?priority=high&type=support">
  Report Critical Issue
</a>

<!-- Specific page -->
<a href="https://supportretriever.com/form/your-form-id?source=features&page=integrations">
  Ask About Integrations
</a>

<!-- Team member -->
<a href="https://supportretriever.com/form/your-form-id?team=sarah&type=sales">
  Contact Sarah
</a>

<!-- Campaign tracking -->
<a href="https://supportretriever.com/form/your-form-id?campaign=webinar-feb&type=sales">
  Register for Webinar
</a>

<!-- Multiple parameters -->
<a href="https://supportretriever.com/form/your-form-id?source=blog&page=guide-name&topic=question">
  Ask Question
</a>

Best Practices

Parameter Naming

Use consistent names:

• Good: type=support, type=sales, type=press
• Bad: type=support, dept=sales, category=press

Use lowercase:

• Good: source=pricing
• Bad: source=Pricing

Use hyphens for spaces:

• Good: page=getting-started
• Bad: page=getting started (breaks URL)

Keep it short:

• Good: src=blog, pg=pricing
• Bad: source_page_location=blog, page_identifier=pricing

Organizing Your Parameters

Create a standard system:

source  = where on your site (footer, nav, blog, pricing)
type    = department (support, sales, press)
topic   = specific subject (bug, feature, billing)
priority = urgency (high, medium, low)
page    = specific page name
campaign = marketing campaign
product = which product
team    = team member name

Document your system:
Keep a reference of what parameters you use and what they mean.

Related Topics

• Using metadata in form URLs
• Understanding conversation metadata
• Getting your form URL
• How to replace mailto links with a spam-protected contact form