# Operating Principles for Super Connectors

The mechanics of using Boomerang are covered in [Super Connector Setup](https://help.getboomerang.ai/super-connectors/setting-yourself-up-on-the-product) and [Reviewing Requests and Making Introductions](https://claude.ai/local_sessions/local_427b048b-a021-4943-82f8-698de75ea062#). This article describes how the program expects Super Connectors to operate. Most of it will already match your instincts.

### Selectivity

Boomerang surfaces fewer, better matches by design. The expectation is that Super Connectors continue that filtering on their end. A handful of well-placed introductions a quarter contributes more to the program — and to your network's standing — than a higher volume of reluctant ones.

If a request doesn't sit right, decline. There is no penalty for declining and no target acceptance rate.

### Honesty About Fit

The most common reason to decline is relationship strength. "I don't know them well enough to make a warm intro" is a sufficient and accurate reason. The program team uses these declines to refine matching.

Conflicts of interest — commercial, personal, or otherwise — are also valid grounds. Naming the conflict in the decline reason is helpful but not required.

### Both Sides Matter

The sales rep is visible in the request; the prospect isn't. Both rely on your judgment. The useful test for any request: would the prospect be glad about this introduction tomorrow morning?

### Communication

A few conventions:

**Response time.** Within a week of receipt is the program norm. The Weekly Clearing Session, configured during setup, is the simplest way to maintain this.

**Tone.** Introductions sent from your inbox should read like any introduction you'd write — warm, brief, in your voice. The generated draft is a starting point, not a template to send verbatim.

**Confidentiality.** Deal context the rep shares with you stays between you, the rep, and the program team. Light framing for the prospect ("they're working on something I thought you'd find interesting") is sufficient.

### Capacity

**Engagement Preferences** (Settings → Engagement Preferences) control request volume. Tightening filters — minimum deal value, opportunity stage, contact seniority — is the recommended way to manage load.\ <br>

<figure><img src="/files/tbJMJUJhLYophNPiSyWm" alt=""><figcaption></figcaption></figure>

For longer pauses, **Alumni Status** (Settings → Privacy & Data) reduces engagement without removing your data. Reactivation is available at any point.

<figure><img src="/files/cLLhIFpfOzs8hNr12aDw" alt=""><figcaption></figcaption></figure>

### Edge Cases

**You don't remember the prospect well.** Decline. Citing relationship strength is the right reason.

**A past intro went poorly.** Don't carry it forward unless the same prospect appears again, in which case it's worth flagging in the decline reason.

**The rep follows up.** A short decline closes the loop. Extended engagement isn't expected.

**The prospect replies asking about the rep.** Vouch at whatever level is true and hand the conversation back. Super Connectors aren't expected to act as the rep's spokesperson.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.getboomerang.ai/super-connectors/operating-principles-for-super-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
