Skip to the main content.

WEBSITE GROWTH & CONVERSION

• Web Design & Development


• SEO & AEO


• Conversion Rate Optimization


• Lead Generation Strategies


HUBSPOT SUPPORT & ENABLEMENT

• HubDesk


• HubSpot Training


• HubSpot Change Management


• HubSpot AI Agent Implementation

IMPLEMENTATION & INTEGRATIONS

• Technology Consulting


• HubSpot Migration Services


• HubSpot Integration Development


• HubSpot Integration Library


• HubSpot & Aircall Integration


• HubSpot & Trustpilot Integration


• Klaviyo Onboarding and Setup


• Custom AI Agent Development

FREE TOOLS & ASSESSMENTS

• AEO Auditor


• HubSpot Al Readiness Scorecard


• HubSpot Al Solutions Design


LEARN & WATCH

• View All Resources


• Ebooks & Templates


• Webinars On-Demand


• Expert Videos

Campaign Creators · Lead Relay · Multi-account HubSpot

One parent. Many portals. Every lead relayed in real time, every result written back.

The Lead Relay connects a parent HubSpot portal to the child and sub-child portals around it: brands, subsidiaries, franchisees, dealers and agencies. It delivers each lead to the right portal in seconds, then writes the outcome back up the chain, so nobody has to chase it by spreadsheet, email or phone.

Franchise systemsMulti-brand manufacturersCompanies with subsidiariesDealer and agency networks
The Lead Relay character: a glowing cobalt-blue hexagon with a forked antenna, passing small glowing orbs from one side to the other.
Real-time lead relay

Each lead lands in the right child and sub-child portal as a deal, contact and company in about 12 seconds.

Results written back

When the sub-child works the lead, its quality, deal size and stage go through the Relay to the child and parent at once.

One view at the top

Every lead, outcome and result lands in the parent portal, so one HubSpot dashboard covers the whole network.

Built for organizations that run HubSpot as a family of portals

The parent generates or receives the lead. A child portal owns the brand or business unit. A sub-child portal, often run by a separate sales team or an independent company, closes the deal. The Lead Relay is the connection between them, in both directions.

Portal names are examples. A dashed portal isn't connected yet; its leads stay with the child until it joins.

Today, people carry the lead. And chase the answer.

Every time a lead crosses from one portal to another, someone moves it by hand. Here's what the Relay takes off their plate.

The manual wayWith the Lead Relay
Forward the lead by emailSomeone reads the form and looks up the territory owner.
Routed in secondsBy brand and by your existing territory data.
Re-key it in another CRMThe receiving team types it in, or doesn’t.
Already in their HubSpotDeal, contact and company, created or matched.
Call to ask “was it any good?”Check-in calls and emails, weeks later.
Quality written backTo the child and parent within a minute.
Update a shared spreadsheetDeal size and status, late or missing.
Value and stage, liveEvery stage move mirrored up the chain.
Stitch reports togetherOne export per portal, merged by hand each month.
One dashboardThe whole network, in the parent portal.
Lose the odd onesNo owner, bad ZIP or wrong country: it sits in an inbox.
Nothing goes missingEvery lead gets an outcome and a written reason.

Two jobs. Both automatic. Both in real time.

The Relay sits between your portals. Leads go down through it. Results come back up through it.

1 · Down the chain

Real-time lead relay

Parent→Relay⇉ ChildSub-child

A new lead in the parent is delivered to the right child and sub-child portal at the same time, in about 12 seconds.

  • Child picked by the form's brand
  • Sub-child picked by ZIP territory
  • Deal, contact and company created in both
2 · Back up the chain

Write-back

Sub-child→Relay⇉ ChildParent

When the sub-child team works the lead in its own HubSpot, the Relay picks up the result and writes it to the child and the parent at the same time.

  • Lead quality
  • Deal size
  • Deal stage, forward or back

Every portal keeps its own HubSpot, users and pipelines. The Relay never overwrites the sub-child team's own fields.

Watch one lead make the round trip

Pick a brand, a form and a ZIP code, then press Send. Blue is the lead going down. Green is the result coming back.

WEBSITE FORMSPARENT PORTALLEAD RELAYCHILD PORTALSSUB-CHILD PORTALS (BY ZIP) Summit Play Cedar Rec Harbor Shade Parent portalevery lead, outcomeand resultONE DASHBOARD Lead Relay form type · brand · ZIP Summit Playchild portal Cedar Recchild portal Harbor Shadechild portal Pacific Play CoSummit · ZIP 900–935 Empire RecreationSummit + Cedar · ZIP 100–149 Lakeshore ParksSummit · ZIP 600–629 · not connected Lone Star PlayCedar · ZIP 750–799 Gulf Coast ShadeHarbor · ZIP 320–349 Rocky Mtn RecHarbor · ZIP 800–816 WRITE-BACK · QUALITY · SIZE · STAGE
Delivered

Brands, teams and territories in the diagram are fictional.

Delivered

To the child portal and to the sub-child that owns the territory.

Child only

The territory's owner isn't connected yet, or it's an in-house rep. The lead stays with the child.

Held

Brand, postal code or country missing or out of scope. The reason is written on the parent deal.

Not routed

Not a sales lead, such as a parts or support enquiry. It stays with the parent.

HubSpot's native tools stop where your network starts

HubSpot offers multi-account management for linking a few sister companies. It was never built to relay leads across a network and bring the results home. Side by side:

HubSpot native multi-accountLead Relay
How many portals✕30 maxThe organization plus 29 portals. Everyone else is left out.✓No portal capAdd every brand, location, dealer and agency you have.
Who can join✕Pro or Enterprise onlyEnterprise on the owner, Professional on every other portal.✓Starter and upSmall dealers and franchisees join on the plan they already have.
Results back to the parent✕NoneA deal can be created in another portal, but nothing comes back after that.✓Real-time write-backQuality, deal size and stage, to the child and parent within a minute.
Routing by territory✕Build it by handWorkflow branches you maintain, one action per destination portal.✓Your territory map, loadedExact ZIP lookup from your Salesforce or spreadsheet export.
What gets created✕One record, one portalA deal, or a contact with name and email, per workflow action.✓The full lead, twiceDeal, contact and company in the child and sub-child at once.
Network reporting✕5 portals per reportNo custom objects, same hosting region only.✓One dashboard, every portalAll results land in the parent, so native HubSpot reports cover it all.
Admin access✕Super Admin in every portalOne person needs top-level rights across every company.✓Each portal keeps controlConnects with its own key and can disconnect any time.

See it with your network

Move the sliders to match your organization.

HubSpot native30 of 49portals connected
Lead Relay49 of 49portals connected
Every portal in, on the plan it already has. Results from all of them land in one parent dashboard.

Native figures assume the parent is on Enterprise and every child on Professional. The Relay has no portal cap by design; we confirm capacity before each rollout stage.

Native is enough when

  • You're linking a few companies you own, all on Professional or above.
  • You only need reps to see each other's contacts.
  • You want to copy emails, forms and lists between portals.

You need the Relay when

  • Leads must reach the right portal by brand and territory, instantly.
  • The parent needs the result back, not just the handoff.
  • You have more than 30 portals, Starter portals, or independent companies in the network.
  • You can also run both side by side.
HubSpot sources for this comparison

Checked October 31, 2026. HubSpot is still building this feature, so we recheck before every proposal.

Built for a multi-brand manufacturer first

The Lead Relay was built for a manufacturer with a parent portal, several brand portals and independent sales agencies, each in its own HubSpot. It is installed in the parent portal now, with the live pilot next.

The first network

One parent, brand portals, agency portals

  • 41,659ZIP codes in one brand's territory, owned by 31 sales reps, loaded straight from its Salesforce export with no errors
  • 12 secfrom a new lead to a deal in the brand and agency portals, in testing on live HubSpot accounts
  • < 1 minfor the agency's quality, deal size and stage to reach the brand and parent
  • 3 in 1one agency portal serving three territories, with each deal labelled with the territory it came from
126 real leads, replayed in a dry run

One brand's website leads from October 1 to 18, routed against its own territories with one agency connected. Nothing was written to any portal. As more agencies connect, child-only leads become delivered leads.

What gets set up in each portal

The Lead Relay works in its own pipelines and a few fields. Existing pipelines, reports and automations stay as they are.

Parent portalParent
  • A Relay Intake pipeline, separate from your sales pipeline
  • A workflow that turns each qualifying form fill into an intake deal
  • Outcome, reason, child, sub-child, quality, deal size and stage on every deal
  • One network dashboard
Each child portalBrand
  • A dedicated Relay pipeline with the shared stages
  • Deal, contact and company for every lead it owns
  • Territory imported from its existing Salesforce or spreadsheet data
  • Results from its sub-child portals written onto its deals
Each sub-child portalDealer, agency
  • A Relay pipeline: New lead, Contacted, Qualified, Quote sent, Won, Lost
  • Deal, contact and company, matched to what they already have
  • Lead quality and deal size fields, or their existing ones
  • Connected in about five minutes, on Starter or higher

Start with a map of your portals

Three steps, each with a sign-off. Nothing is written to your portals until you approve the dry run.

Step 1 · Start here

Portal Network Map

Your portals, your handoffs and your territory data, on one page.

Then a dry run on last month's real leads

  • Every parent, child and sub-child portal and its tier
  • How leads move today, and where results get lost
  • Territory data checked and loaded
  • Your leads replayed with no delivery, outcome by outcome
Map my portal network
Step 2

Pilot

Live relay and write-back for one slice of the network.

The parent, two child portals, a few sub-child portals

  • Relay pipelines and fields in every pilot portal
  • Sub-child portals connected with their own keys
  • Parent dashboard live
  • Go-live checklist and sign-off
Talk about a pilot
Step 3

Network Rollout

Every child and sub-child portal, monitored daily.

Monthly operations after launch

  • New child portals added from their territory data, no new code
  • Sub-child onboarding in about five minutes each
  • Alerts, daily checks and a runbook
  • Hosting moved into your name when you're ready
Plan a rollout

Fixed-scope pricing for each step, quoted after the network map.

The Lead Relay character

How do leads move between your portals today?

In 30 minutes we'll map your parent, child and sub-child portals, see how leads and results move between them now, and show you what the Lead Relay would do with last month's leads. If HubSpot's native multi-account tools are enough for your network, we'll tell you that.

HubSpot Elite Solutions Partner · 600+ HubSpot onboardings and implementations · One of the first 50 partners worldwide with HubSpot's Advanced Implementation Accreditation

HubSpot is a trademark of HubSpot, Inc.