# The angle for first contact

The angle is the reason this message is arriving at this business rather than at a thousand others. It is built from claims already on the record, each carrying the source it came from, so nothing in the opening is a flourish nobody can check. Anything that would need an invented fact, a price or a promise is refused and left for a person.

- **Status:** Available
- **Audience:** both
- **In the app:** #/prospects, #/needs-you
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/prospects/personalised-angle/

## Where the opening comes from

It is assembled from the fit reason and the claims underneath it — not from a template with slots. That difference is visible to the recipient. A templated line names the company and the industry; a grounded one names the thing about this business that made it worth writing to, and it can only do that because somebody read something specific.

| Material | Makes a good angle when | Reads badly when |
|---|---|---|
| A dated public announcement | It is recent and the business chose to publish it | It is years old and everyone has moved on |
| What the business says it does | It is specific — a service, a region, a method | It is generic marketing copy |
| A published operating detail | It connects to what you actually sell | It is repeated back with no point attached |
| A named person's own words | They said it publicly and it is current | It was a quote in an article about something else |
| Nothing sourced | — | Always: no angle is written rather than a hollow one |

The last row is the useful one. Where the record is thin the opening is plain rather than falsely familiar, because a fabricated observation about a business is more damaging than a straightforward introduction.

## What the angle is refused

Three refusals apply, and they are the same ones that govern every sales conversation Connect has.

1. **No commercial terms Knowledge does not carry.** A price, a discount, an SLA or a warranty that the workspace's Knowledge does not support is escalated to a person rather than improvised. Refusing is the correct behaviour, not a gap.
2. **No claim without a source.** The opening can only quote what the record holds, and the record only holds what came with backing.
3. **No instruction taken from the prospect's own material.** Text fetched during research is data to summarise, never direction to follow — the reasoning is at [Prompt injection arrives as ordinary business mail](/research/prompt-injection-in-business-mail/).

> **Note** A refusal is recorded as a decision, not swallowed. The audit trail keeps what was decided, under which rule, and what happened — including the times Connect declined to say something.

## The things that make an opening read as automated

**A stale detail** — Quoting an announcement the business made two years ago tells the reader that whoever wrote this has not looked recently. Freshness exists partly for this.
**A compliment with no content** — "I was impressed by your work in the sector" is what a template produces when the record is empty. A plain introduction is better.
**A wrong inference about authority** — Addressing somebody as the person who decides, when public material only showed a title, invites a correction instead of a reply.
**A detail the business did not publish** — Nothing reaches the opening that was not sourced, so this should not occur — if it does, the claim behind it is the bug, not the sentence.

None of these is fixed by better phrasing. Each is a research problem surfacing as a writing problem, which is why the fix is upstream: correct the claim, re-read the record, or accept a plainer opening.

## Before it is sent

The angle is written before the gates, not after. It still has to pass [sender readiness](/docs/prospects/sender-readiness/) and [the compliance check](/docs/prospects/compliance-check/), and then the channel's autonomy rule decides whether it goes or waits. In `ask_before_send` the whole message, angle included, sits in Needs You with the record it was drawn from, so the claims and the sentence can be read together.

Editing it there is expected. Your edit is what gets sent — nothing rewrites over a person's text — and an edit that removes a claim you know to be wrong is worth making on the record too, so the next message does not repeat it.

## Questions

### Can I supply my own opening for a whole search?

You can write the framing you want, and it is used as direction. What it cannot do is authorise a claim about a specific business that the record does not carry, or a commercial term Knowledge does not support.

### Why is the opening so plain on some prospects?

Because the record was thin. A plain opening on a business that publishes little is the honest output; the alternative would be an observation nobody could point at a source for.

### Does the same angle get reused across a list?

Not by design — each is built from that prospect's own claims. If several read alike it is because the underlying research found the same generic material at each business, which is a signal about the population you are writing to.

## Related

- [Why this prospect](https://connectbyjbrh.com/docs/prospects/fit-reason/)
- [First outreach](https://connectbyjbrh.com/docs/prospects/first-outreach/)
- [Sender readiness](https://connectbyjbrh.com/docs/prospects/sender-readiness/)
- [Evidence on a prospect](https://connectbyjbrh.com/docs/prospects/evidence/)
- [Why a sales agent should refuse to answer](https://connectbyjbrh.com/research/safe-refusals-in-sales/)
- [Knowledge in Connect](https://connectbyjbrh.com/docs/knowledge/)

## What this page is based on

- docs-source/sources/CHANNELS.md §4 — evidence-first prospecting and outreach
- docs-source/sources/CHANNELS.md §6 — safe_sales.py and refused commercial terms
- docs-source/sources/GENERAL.md §5 — autonomy modes and the audit trail
