How to set up automated partner notifications in Partnered to boost deal collaboration

If you're running partner deals and feeling like half your energy goes into chasing updates, you're not alone. Coordinating with partners is messy: emails get buried, Slack pings go unanswered, and deals stall. The good news? If you're using Partnered, there are real ways to automate notifications and make sure folks actually see what matters—without turning your team into spam bots.

This guide is for anyone who owns partner relationships, runs sales ops, or just wants less chaos in their pipeline. We'll walk through how to set up automated partner notifications in Partnered, what actually helps collaboration (and what just adds noise), and a few honest notes about what to skip.


Why Automate Partner Notifications (And When Not To)

Before we dive into setup, let's be clear: more notifications aren't always better. The goal here is to keep people in the loop on the stuff that really matters—deal movement, action items, and roadblocks—without flooding inboxes or Slack channels.

Automated partner notifications are worth your time if:

  • You have deals that involve multiple partner reps or teams.
  • You're tired of updating people manually and missing steps.
  • You want a reliable way to keep both sides accountable.

But skip heavy automation if:

  • You only have a handful of deals and talk with partners daily.
  • Your partners hate email or ignore notifications anyway.
  • Internal alignment is your real issue (no tool can fix that).

Now, let's get to the setup.


Step 1: Get Clear on What Needs Notifying

First, map out what actually needs a notification. Partnered can automate updates on almost anything, but that doesn't mean you should.

Start by asking:

  • When do partners actually need an update to act? (e.g., deal stage change, intro needed)
  • Where do people want to get notified? (email, Slack, in-app)
  • What info is critical, and what’s just noise?

Pro tip: Run through a recent stalled deal. Where did communication break down? Use that as your notification blueprint.

Common Triggers Worth Automating

  • Deal assigned or accepted: When a new deal is shared with a partner, let them know immediately.
  • Deal stage changes: Update partners when a deal moves (e.g., from "Intro Needed" to "Discovery").
  • Tasks or asks: When someone requests an intro, meeting, or resource.
  • Notes or updates added: Only if they're substantial—skip the "FYI" fluff.

Skip automating:

  • Every time someone adds a comment or tweaks a note
  • Generic “deal touched” activity logs

Step 2: Set Up Notification Channels in Partnered

Partnered lets you push notifications via email, Slack, and in-app alerts. Decide what works for your team and your partners.

Email: - Good for external partners who don’t live in Slack. - Tends to get ignored if overused.

Slack: - Faster response for internal teams. - Works if your partners are on shared Slack channels (not always the case).

In-app: - Least intrusive, but only works if folks actually log into Partnered.

How to set channels: 1. Go to your Partnered settings (usually under your profile, then 'Notifications'). 2. For each event type (deal assigned, stage update, etc.), pick the default notification method. 3. For key partners, check if they're set up for Slack or email. Don’t assume—ask them.

Pro tip: Start with email for partners, Slack for your own team. Don’t set up both unless people specifically ask.


Step 3: Configure Notification Triggers

Now, set up the actual triggers. Here's how to do it without overwhelming everyone:

  1. Log into Partnered and head to the "Workflow Automation" or "Notifications" section.
  2. Pick a deal type or workflow. (e.g., “New deal shared with partner”)
  3. Choose your trigger: This might be “deal assigned,” “stage changed,” or “task created.”
  4. Select recipients: Internal team, partner rep, or both. Be specific—avoid “all users” unless you love clutter.
  5. Set frequency: Instantly is usually fine, but for non-urgent stuff, try daily digests.

Example setup:
- Trigger: Deal moves to “Needs Intro” - Recipients: Partner AE and your AE - Channel: Email for partner, Slack for your AE - Message template: “Deal {{deal_name}} needs an intro to {{contact_name}}. Please respond by {{due_date}}.”

Don’t overthink it: Start with the most critical trigger (e.g., when someone is actually needed to act). You can always add more later.


Step 4: Customize Message Content (But Don’t Get Fancy)

Partnered usually lets you tweak notification text. Keep it short and actionable.

What to include:

  • Deal name and link
  • What happened (trigger)
  • What’s needed (if anything)
  • Who owns the next step

What to skip:

  • Long summaries or deal histories (nobody reads it)
  • Generic “just checking in” language

Example notification:

“New partner deal assigned: ACME Corp. Needs intro to Jane Doe. Click here to update status.”

Pro tip: Test your message by sending it to yourself. If you wouldn’t respond to it, neither will your partner.


Step 5: Test With a Real Deal—Not a Dummy

Don’t rely on the “test notification” button alone. Run your setup with an actual in-flight deal and a real partner. Here’s why:

  • You’ll see if the right people get notified (and if they see it).
  • You’ll spot where notifications get lost (e.g., stuck in spam, buried in Slack noise).
  • You’ll notice if the messages actually drive action.

Checklist for your test:

  • Did both sides get the notification?
  • Was the info clear—did anyone have to follow up for details?
  • Did the notification get the right action in a reasonable time?

If something’s off:
Tweak the channel, message, or trigger. Don’t be afraid to turn things off if they’re not helping.


Step 6: Set Boundaries (And Avoid Notification Fatigue)

The fastest way to kill trust is to drown people in notifications. Be the person who actually makes things easier, not harder.

Tips to avoid overload:

  • Limit notifications to critical changes—less is more.
  • Use batch or digest mode for minor updates.
  • Ask partners what works for them (and listen).

If a partner says they're ignoring emails:
Switch to Slack or in-app, or just cut back. There’s no point automating what nobody reads.


Step 7: Review and Adjust Regularly

Automation isn’t “set and forget.” Deal flow changes, partners come and go, and what worked last quarter might be ignored now.

Every quarter (or after a big deal):

  • Ask users and partners: “Are the notifications actually helpful?”
  • Check if deals are moving faster or just getting more noise.
  • Prune triggers that aren’t pulling their weight.

What to ignore:
Fancy analytics dashboards about “notification engagement” aren’t the point. If deals are moving and people respond, it’s working.


Honest Takes: What Works, What Doesn’t

Works:

  • Automating the moments when someone needs to act, not just to “keep folks in the loop.”
  • Using channels people already check (don’t force partners into your stack).
  • Keeping messages short, with a link to more detail if needed.

Doesn’t Work:

  • Notifying everyone of everything—people tune out.
  • Relying on in-app only (most partners won’t log in daily).
  • Assuming one setup works for all partners—flexibility matters.

Ignore:

  • Cosmetic customizations and “branding” notifications. The point is action, not pretty emails.
  • Automating every tiny update—manual is fine for edge cases.

Keep It Simple—And Iterate

Automated partner notifications in Partnered can actually help, as long as you keep things focused and don’t overdo it. Start small: pick one or two critical triggers, get feedback, and adjust. If folks are acting faster and you’re spending less time chasing status updates, you’re on the right track.

Keep it simple, keep it useful, and don’t be afraid to turn things off. The best collaboration tool is the one people actually use—and that goes for notifications, too.