Skip to content
EmailCampaigns.io

Agencies / partner referral

Clarify Agency Scope with a Potential Partner

Clarify complementary agency scope before discussing referrals.

Sender: Partner owner · After confirming relevant partner context and permission to contact, with current scope and exclusions approved by the delivery owner.

Bottom line

A relevant permissioned partner conversation is ready to compare verified agency capabilities and exclusions.

Best for

A relevant partner discussion where scope and handoff fit need clarification.

Use when

After confirming relevant partner context and permission to contact, with current scope and exclusions approved by the delivery owner.

Watch for

Unsolicited bulk outreach, unsupported capabilities or an assumed exclusive arrangement.

The Job This Email Does

Business outcome

Build a useful partnership based on complementary work rather than vague referral volume.

What the recipient gets

Understand when an introduction would help and when it would not.

Point of view

A clear limit is as useful as a capability when deciding fit.

Success looks like

A concrete scope question leads to agreed handoff expectations.

Primary action: Reply with a scope question.

How to Use This Email

When to use this

A relevant permissioned partner conversation is ready to compare verified agency capabilities and exclusions.

What’s on their mind

The partner needs to know whether work overlaps and who would own the client handoff.

What this email should do

Clarify complementary agency scope before discussing referrals.

Best sender

Partner owner

Read the Finished Email

Review the message as a recipient would see it. The names and business details are fictional.

Subject Line Variations

  • A scope question before any introductions

    Names the specific decision or useful evidence without adding urgency.

  • Comparing our agency services

    Names the specific decision or useful evidence without adding urgency.

Best for

  • A relevant partner discussion where scope and handoff fit need clarification.

Don’t send this if

  • Unsolicited bulk outreach, unsupported capabilities or an assumed exclusive arrangement.

When to Send It

Trigger

A relevant permissioned partner conversation is ready to compare verified agency capabilities and exclusions.

Timing

After confirming relevant partner context and permission to contact, with current scope and exclusions approved by the delivery owner.

Frequency

One message for this distinct decision need; stop on any response or changed eligibility.

Timing note

No invented deadlines, capacity limits or results.

Make This Email Yours

  • Use current capabilities the delivery team can support.
  • Name a meaningful exclusion rather than claiming the agency handles everything.
  • Review the partner’s known work without assuming an exclusive arrangement or ownership of their clients.

Before You Use This Email

Why This Approach Works

Platform Setup Steps

Trigger

A relevant permissioned partner conversation is ready to compare verified agency capabilities and exclusions.

Segment

Known authorized referral partner

Delay

After confirming relevant partner context and permission to contact, with current scope and exclusions approved by the delivery owner.

Reply owner: Named agency account or partner owner

  1. Verify partner context, contact permission and current agency scope.
  2. Assign the owner who can answer capability and handoff questions.
  3. Route replies to that person and document any later handoff arrangement separately before sharing client information.

Stop conditions

  • Stop when the goal is met or the recipient replies; assign human handling.
  • Stop on approval, decline, revision, active conversation, unsubscribe, complaint or hard bounce.
  • Suppress stale or conflicting context; route safety, dispute or regulated-review concerns to a qualified human.

Mistakes To Avoid

  • Offering referrals before checking overlap

    It can confuse client ownership and service expectations.

    Use instead: Compare capabilities and exclusions first.

  • Treating a friendly reply as a partnership agreement

    Interest does not settle commercial or data-sharing terms.

    Use instead: Agree any operating arrangement separately.

Sequence Placement

Send for the specific verified scope discussion, permitted referral update or quarterly feedback event. These distinct jobs do not form an automatic sequence; replies and concerns go to the named owner.

Related Email Platform Guidance

  • teams running behavior-based nurture with branching, scoring, and segmentation

    Not best for: teams whose requirements stop at newsletters and a short welcome series

    View ActiveCampaign
  • SaaS and digital-product teams with trustworthy behavioral events

    Not best for: small teams without event instrumentation or technical implementation capacity

    Visit Customer.io
  • B2B organizations aligning marketing, sales, and service around shared CRM data

    Not best for: small teams needing only broadcasts and a simple welcome sequence

    View HubSpot

Disclosure

Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.