# Requesting an Introduction
Once you've found a contact you want to reach and reviewed the available paths, submitting a request takes three steps. This article walks through the flow and shares best practices for getting your request approved and acted on quickly.
***
## How it works at a glance
Boomerang uses **Rudy**, its AI engine, to do most of the heavy lifting in composing your request. You provide the *context* — who you want to reach, why, and what you're hoping to unlock — and Rudy drafts two things for you:
1. A **briefing card for the connector** — giving them the context they need to decide whether to make the intro.
2. A **draft intro for the target** — the email or message the connector will forward to the target contact.
You review both before submitting. The connector sees the briefing; the target sees only the intro.
{% hint style="info" %}
Your context stays internal. Deal context, competitor notes, and anything sensitive you share in Step 1 are visible only to the connector reviewing your request. Rudy strips them out of the draft that goes to the target.
{% endhint %}
***
## Step 1: Provide context for the intro
Click **Ask for Intro** on any contact row. The Request Intro modal opens.
You'll see a set of questions that your admin has configured. A typical set includes fields like:
* Who you (or your team) are currently working with at the account.
* What problem or use case the target is likely solving.
* What this intro would unlock for the deal or relationship.
* Any additional context that's relevant (e.g., a competitor pushing, a renewal coming up, a recent news trigger).
**The exact questions vary by organization** — your admin has customized the form to match how your team sells.
### How to write great context
The quality of this step determines the quality of everything that follows. Rudy uses what you write here to draft both the briefing card and the intro — so the more useful your context, the better both outputs will be.
* **Be specific, not generic.** "Helps ZScaler scale their go-to-market motion" is vague. "Competing with OneTrust for ZScaler's data privacy renewal in Q3 — Rita Zhou is the budget owner" is useful.
* **Explain the *****why*****, not just the *****what*****.** Connectors approve intros when they understand the business reason. "Want to explore" rarely converts; "we've been working with four teams at ZScaler and this person owns the remaining one we need to close the deal" almost always does.
* **Share the current state.** Who you're already talking to, what's already been tried, and why the intro matters now. This prevents duplicate outreach and shows you've done the work.
* **Don't worry about polish.** Rudy rewrites your context into the briefing and intro drafts — you're giving it raw material, not the final copy. Bullet points, fragments, and shorthand are fine.
When you're done, click **Continue**.
***
## Step 2: Choose your options
Step 2 lets you flag urgency and, optionally, choose a preferred connector.
### Time sensitivity
Check **Is this time sensitive?** if there's a genuine deadline driving the ask — a deal closing, a board meeting, a conference, or a window that closes soon. This flag shows up on the connector's request to help them prioritize.
{% hint style="warning" %}
Use the time-sensitive flag sparingly. If every request is marked urgent, none of them actually are. Save it for requests that truly can't wait.
{% endhint %}
### Preferred Super Connector
Below the time-sensitive toggle is a list of the Super Connectors who have paths to the target, each labelled with their strength (Strong, Likely, or Long Shot). **You choose which connector you want to route the request through.**
* **Select the connector you want to ask.** This is your decision to make based on the strength of the path, your read of each connector's relationship with the target, and which of your connectors is the right voice for this particular ask.
* **You can select more than one** if multiple connectors make sense for the same request.
* **When you select a connector, a text field appears** asking you to specify why you're prioritizing them. This helps the connector understand the ask and reduces any awkwardness about being singled out.
When you're done, click **Generate Draft**.
***
## Step 3: Review the Rudy-generated drafts
Rudy now composes both messages. You'll see a brief processing view showing what it's doing — reading CRM context, drafting the briefing, drafting the intro, removing sensitive information, applying your organization's guardrails, and running a final compliance scan.
Once done, you're taken to the Draft Review view with two tabs:
{% tabs %}
{% tab title="Request to Connector (briefing card)" %}
This is what the connector sees when they review your request. It includes a "Context of Connection" summary — a concise version of what you entered in Step 1, formatted to help the connector quickly understand the ask.
* **Read it as the connector would.** Does it make the ask clear in 10 seconds? Does it give them enough to decide without overwhelming them?
* **This is the only place deal context lives.** Internal pricing, deal amounts, and competitive notes stay on this tab — they do not appear in the intro draft.
* **Edit inline if needed.** You can tweak wording directly in the text box.
{% endtab %}
{% tab title="Draft for Target (the intro)" %}
This is the email (and text message) the connector will forward. It comes in two formats:
* **Email** — for a more formal intro, typically longer.
* **Text** — for a quick messaging-style intro.
* **Read it as the target would.** Would you respond if you received this? Does it respect the target's time?
* **Check for anything that shouldn't be public.** Rudy redacts internal information by default, but a final human review is always worth doing.
* **Edit inline** if you want a specific phrase, tone shift, or opening line.
{% endtab %}
{% endtabs %}
### If you need to change more than wording
If the draft is off in a structural way — wrong angle, missing an important point, too pushy — click **Update context & regenerate** to go back to Step 1, revise your context, and have Rudy draft again. This is faster than trying to fix the output.
***
## Submit
When you're happy with both drafts, click **Submit →**. Your request is routed to the connector (or connectors) selected, and they receive a notification to review.
The contact's **Action** column on the account page now shows **Modify Request or Withdraw Request** instead of **Ask for Intro**. You can track the status of the request from your requests view — see *Understanding your request status*.
***
## Best-practice checklist
Before hitting submit, a quick mental check:
1. **Context specific enough** that a connector who doesn't know the deal can still decide in under a minute?
2. **"Why now"** clear in both the context and (by extension) the drafts?
3. **Time-sensitive flag used honestly** — or left off if there's no real deadline?
4. **Preferred connector choice intentional** — the right person for this particular ask?
5. **Target-facing draft** free of anything internal or sensitive?
6. **Tone matches** the target's seniority and likely context?
Requests that pass all six of these almost always get approved.
---
# 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/requesters/requesting-an-introduction.md?ask=
```
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.