# Understanding your request status

After you submit an introduction request, it moves through a few stages as the connector reviews it and (if approved) the intro goes out. This article explains each status, what it means, and what — if anything — you should do at each stage.

## Where to find the status of your requests

You can see the status of every request you've submitted in the **My Requests** view in the Boomerang web app.

> **\[Screenshot placeholder]** The **My Requests** view showing a list of submitted requests with their current status, target contact, connector, and submission date.

Each row represents a single request and shows the target contact, the connector it was routed to, when you submitted it, and its current status.

## The lifecycle of a request

Every request goes through a similar path from submission to resolution:

```liquid
  Submitted → Pending with Connector → Approved → Intro Sent → Completed
                          │
                          └─→ Declined
```

At any given moment, a request is in one of the statuses below.

## What each status means

### Pending with Connector

**What it means:** Your request has been submitted and is in the connector's queue. They haven't responded yet.

**What to do:**

* **Be patient.** Connectors are typically busy executives, investors, or advisors. Most requests are reviewed within a few business days.
* **Don't nudge directly.** Reaching out to the connector outside of Boomerang ("did you see my request?") is counterproductive — it bypasses the workflow they've agreed to and creates friction.
* If the request is genuinely urgent and you didn't mark it time-sensitive at submission, talk to your Super Connector Admin about escalation norms for your team.

### Approved

**What it means:** The connector reviewed your request and agreed to make the intro. Boomerang is preparing the intro email (or the connector is composing it if that's how your organization has set things up).

**What to do:**

* **Prepare for the target to respond.** Once the intro lands, the target may respond within hours. Have your follow-up ready — a short value-focused message, a calendar link, or whatever fits your typical motion.
* **Don't reach out to the target yet.** Let the intro land first. Cold-emailing them the moment you see "Approved" undermines the value of the warm intro.

### Intro Sent

**What it means:** The introduction email has been sent from the connector to the target. The ball is now in the target's court.

**What to do:**

* **Watch your inbox.** The connector will typically cc you (or forward the intro) so you can reply directly. Check your email and any threads the connector may have started.
* **Reply promptly when the target responds.** A fast, thoughtful reply is the single biggest predictor of whether a warm intro converts into a meeting.

For what to do after the intro lands, see *What happens after your request is approved*.

### Declined

**What it means:** The connector decided not to make the intro. They may have left a short reason.

**What to do:**

* **Read the reason if provided.** Common reasons include: the connector doesn't know the target well enough to vouch, the relationship isn't recent, or the connector is saving their intro capital for the target.
* **Try an alternative path.** If multiple paths exist to the same contact, submit a new request through a different connector. "Already Requested" is lifted once a request is declined, so the contact becomes requestable again.
* **Don't take it personally.** A decline is about the specific relationship, not your request.

### Completed

**What it means:** The intro has landed and either the target has engaged, a meeting was booked, or the connector has marked the request as closed.

**What to do:**

* **Report back.** If the intro led to a meeting or a deal, let the connector know. A two-line "update on the intro you made" note goes a long way toward keeping connectors willing to help next time.

## Why "Already Requested" blocks new requests

While a request is in any non-resolved state — Pending, Approved, or Intro Sent — the contact's **Action** column on the account page shows **Already Requested** instead of **Ask for Intro**. You can't submit a second request for the same contact while one is in flight.

This is deliberate: it prevents your network from being pinged more than once about the same person, and it prevents the target from receiving duplicate intros.

Once a request is **Declined** (or, depending on how your organization has configured things, after a request is Completed), the contact becomes requestable again.

## Common questions

<details>

<summary>How long does a request typically stay Pending?</summary>

Most connectors review requests within a few business days. If a request has been Pending for more than a week, talk to your admin — they may want to reach out to the connector separately.

</details>

<details>

<summary>Will I be notified when the status changes?</summary>

Yes. Boomerang sends email notifications when a request is approved, declined, or the intro is sent. Make sure your notification preferences are enabled so you don't miss them.

</details>

<details>

<summary>Can I cancel a request?</summary>

If your team has enabled request cancellation, you can withdraw a Pending request from the My Requests view. Once a request is Approved or Intro Sent, it cannot be cancelled.

</details>

<details>

<summary>What if I think a request was declined in error?</summary>

Reach out to your Super Connector Admin. They can help you decide whether to try a different connector or approach the target another way.

</details>


---

# 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/understanding-your-request-status.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.