# From a buying signal to a booked meeting

> Five stages, three setup questions and one safety engine. Every message waits for your approval, or your agent’s, until you decide otherwise.

Source: https://pipevoy.com/how-it-works (Markdown: https://pipevoy.com/how-it-works.md)

## Give this to your agent

agent-brief.txt

```text
You can run LinkedIn outreach through Pipevoy, a headless AI SDR. It drafts LinkedIn invites, follow-ups and replies for a workspace and sends them through its own engine, which enforces warm-up, per-sender daily and weekly limits, working hours and approvals. Never send on LinkedIn yourself.

REST API  https://pipevoy.com/api/v1
MCP       https://pipevoy.com/api/mcp
Docs      https://pipevoy.com/docs/api
OpenAPI   https://pipevoy.com/api/v1/openapi.json
llms.txt  https://pipevoy.com/llms.txt
Auth      Authorization: Bearer <api key> (same key for REST and MCP)

No key yet: POST /api/v1/signup with {"email", "company_name"}, no auth. Then poll GET /api/v1/signup/{id} with header X-Claim-Token until api_key appears. It is returned once; store it.

Start each session with GET /api/v1/me. Its setup.next_step says what to do next. Approving a draft only queues it; the engine decides when it is safe to send. Every error has error.hint with the next step.

Ask your human for exactly three things:
1. Open the confirmation email Pipevoy sends after signup.
2. Open each sender's connect_url and log in to LinkedIn once.
3. Pay the Stripe Checkout link before the 14-day trial ends.
```

## Facts

| What | Value |
| --- | --- |
| REST base URL | `https://pipevoy.com/api/v1` |
| MCP server | `https://pipevoy.com/api/mcp` (Streamable HTTP, JSON responses) |
| Auth header | `Authorization: Bearer pv_…` (same key for REST and MCP) |
| Signup | `POST /api/v1/signup` (no key) → a person confirms the email → `GET /api/v1/signup/{id}` with `X-Claim-Token` returns `api_key` once |
| API index | [https://pipevoy.com/api/v1](https://pipevoy.com/api/v1) |
| OpenAPI 3.1 | [https://pipevoy.com/api/v1/openapi.json](https://pipevoy.com/api/v1/openapi.json) |
| MCP server card | [https://pipevoy.com/api/mcp/server-card](https://pipevoy.com/api/mcp/server-card) |
| llms.txt | [https://pipevoy.com/llms.txt](https://pipevoy.com/llms.txt) |
| Docs | [https://pipevoy.com/docs/api](https://pipevoy.com/docs/api) (Markdown: [/docs/api.md](https://pipevoy.com/docs/api.md)) |
| Trial | 14 days, no card, API and MCP included |
| Human steps | Confirm the signup email; log in to LinkedIn once per sender; pay |
| Product | Pipevoy, a headless AI SDR for LinkedIn |

## The five stages

### 1. Watch for signals

Tell it what a good moment to reach out looks like. It checks for those moments every day.

- Job changes, hiring, funding and expansion, from LinkedIn searches and company websites, checked daily.
- Your own sources through the API, an inbound webhook, CSV, Zapier or Clay.
- Each signal scored 0 to 100; each account ranked by fit plus fresh signals.

### 2. Find the stakeholders

A signal is about a company or a person. Outreach needs the right person.

- People at the account are matched to your personas and ranked.
- Current role, tenure and recent posts are added, so drafts reference something real.
- Signal campaigns enroll matching people automatically, up to a daily cap you set.

### 3. Draft, approve, send

Every draft is written for one person, about one reason.

- The opener uses the signal naturally, never like surveillance.
- Drafts wait in an approval queue with the prospect’s context. Approve, edit or skip, in the app or over the API.
- Approved messages go out in working hours, at uneven intervals, under limits. Follow-ups stop the moment someone replies.

### 4. Handle replies

Replies are read and sorted so you only spend time where it counts.

- Every reply is classified into one of eight intents, from interested to opt-out.
- Interested replies get a suggested answer with your booking link, for approval.
- An opt-out ends every sequence for that person. Anything uncertain goes to a human.

### 5. Book and follow through

The meeting is the goal, so the work continues until it actually happens.

- Bookings through your calendar link are matched to the conversation and fire meeting.booked.
- Mark meetings held, no-show or qualified. Contacts, companies and meetings sync to HubSpot.
- A no-show gets a short rebook note, drafted for approval, at most twice.