> ## Documentation Index
> Fetch the complete documentation index at: https://hc.starbridge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Generate personalized outbound

> A deep dive on the Personalized Outbound Email column — configure ready-to-send, personalized outreach at scale, with best practices and example use cases.

The **Personalized Outbound Email column** turns signal context into ready-to-send outreach, right inside your Bridge. You write the template and messaging once; AI generates the personalized hooks for each row.

This column is available for **all Bridge types**.

## What you can build

Every email combines three kinds of content, mixed however you like:

<CardGroup cols={3}>
  <Card title="Static text" icon="font">
    Your own copy that appears as typed in every email. Good for value props, CTAs, and signatures.
  </Card>

  <Card title="Dynamic Variables" icon="at">
    Personalized data pulled from the signal or Bridge (e.g. contact name, buyer name) Inserted with `@`.
  </Card>

  <Card title="AI snippets" icon="wand-magic-sparkles">
    Personalized content generated for each row based on the signal. Inserted with `@`, configured via a prompt you control.
  </Card>
</CardGroup>

## How to add and configure the column

<Steps>
  <Step title="Add the column">
    Open your Bridge, click **Add enrichment**, and select **Create Personalized Outreach → Create Personalized Outbound Email**.
  </Step>

  <Step title="Generate your email">
    You can either describe the email you want to write in plain language and have AI generate the draft, or configure your email from scratch. 
  </Step>

  <Step title="Write your subject line and body">
    You'll see two fields to configure — **Subject Line** and **Email Body**. Compose each using any mix of static text, variables, and AI snippets (below).
  </Step>

  <Step title="Preview on the first 5 rows">
    Run the column on the first 5 rows to check the output and snippet quality before committing. Edit your prompts and rerun until you're satisfied with the output. 
  </Step>

  <Step title="Run all rows">
    Once the drafts look right, run the column across the whole Bridge.
  </Step>
</Steps>

## Building your email

<Frame>
  <img src="https://mintcdn.com/starbridge/ZGPvWytbCD0spbBC/em.png?fit=max&auto=format&n=ZGPvWytbCD0spbBC&q=85&s=9690fe29c6966d69f36ceb0622620c19" alt="Em" width="1488" height="1114" data-path="em.png" />
</Frame>

### Static text

Type your copy directly. This text appears exactly as written in every email.

> I wanted to reach out to see if you'd be open to connecting.

### Variables (`@`)

Insert dynamic data from your Bridge or signal attributes — these change for each row. Type `@` and select from the suggested attributes. Common examples:

* `@First Name` — the contact's first name
* `@Buyer Common Name` — the buyer / account common name
* `@Conference` — conference name
* `@Due Date` — an RFP's due date

> Hi @First Name,

### AI snippets (`@`)

Add AI-generated content that writes a personalized snippet for each row based on the signal. To add one: type `@` in the subject line or body, select **AI Snippet**, give it a name, and write a prompt describing what the snippet should pull from each signal.

<Tip>
  You can directly reference other Bridge columns inside a snippet prompt — for example, *"Based on `@Summarized Relevance`, write a 1–2 sentence opening."* Starbridge pre-generates snippet prompts for certain Bridge types; edit them to fit your use case.
</Tip>

### Let AI draft the whole email

You don't have to compose every piece by hand. Tell Starbridge the **goal** of the email (e.g. book a meeting, reactivate a closed-lost account, follow up after a conference), plus any guidance, and it generates a draft with static copy, variables, and AI snippets already included. Edit from there.

### Rich text formatting

The email editor supports rich text — apply **bold**, *italic*, underline, bulleted lists, and hyperlinks to keep your outreach on-brand and readable.

## AI snippet best practices

Strong prompts are specific and bounded:

* **Be specific**: "Write one sentence mentioning the budget challenges discussed," not "Personalize this."
* **Set length guidelines**: "Keep under 50 words" or "Write 1–2 sentences."
* **Define tone**: "Write conversationally" or "Keep it professional."
* **Reference the signal or a column**: point the prompt at `@Summarized Relevance`, `@Job Change`, `@RFP`, etc., so it grounds in real context.
* **Avoid vague prompts** — "Make it good" produces generic output.

<Note>
  Test on the first 5 rows and iterate before running the whole Bridge. You can edit any snippet later via the gear icon on the column.
</Note>

## Outputting and sending

### Choose how the column outputs

By default the column produces three columns: a **consolidated email** (subject, body, and snippets together), the **subject line**, and the **email body**. You can optionally output individual AI snippets as their own columns, or show only the consolidated email — configured in the **Add Email Fields as Columns** section of the column editor.

### Send with one click — Open in mail

Every Starbridge-generated email has an **Open in mail** button that drops the email — recipient, subject, and body pre-populated — straight into Gmail, Outlook, or your default mail app. The first time a rep clicks it, they pick their preferred client; after that every email opens there by default. The button appears everywhere reps work with generated emails: in Ask Starbridge, on signal cards in the Feed, and inside Bridges.

### Export to your CRM or sequencer

When the column has fully generated, export the subject line, body, and/or individual snippets to your CRM or outbound sequencer via the CRM integration or a CSV export.

## Example emails by Bridge type

<Tabs>
  <Tab title="Meetings">
    **Subject:** `@[AI Snippet: "Write a 3–5 word subject line referencing the main topic discussed in the meeting from @Summarized Relevance"]`

    > Hi `@First Name`,
    >
    > `@[AI Snippet: "Write 2–3 sentences referencing specific challenges or initiatives mentioned in the meeting from @Summarized Relevance and position them as something we can help with"]`
    >
    > I'd love to share how we've helped organizations like `@Buyer Common Name` tackle similar challenges. Would you be open to a brief conversation?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Purchases / Contracts">
    **Subject:** Your `@Seller Name` contract

    > Hi `@First Name`,
    >
    > I noticed your contract with `@Seller Name` is ending soon.
    >
    > `@[AI Snippet: "Ask conversationally if the buyer has started looking at alternatives for @Purchase, and mention the upcoming expiration if @Contract End Date is soon. Use information from @Summary."]`
    >
    > We've helped organizations like `@Buyer Common Name` optimize costs and improve outcomes. Happy to share more if you're evaluating options.
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="RFPs">
    **Subject:** Re: Your Posted RFP

    > Hi `@First Name`,
    >
    > I saw that `@Buyer Common Name` recently posted an RFP with a due date of `@Due Date`. `@[AI Snippet: "Write 1–2 sentences explaining how our solution aligns with the specific requirements in @RFP @Summary"]`
    >
    > I'd love to schedule a brief call to discuss how we can support your goals. Would you have 15 minutes this week?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Job Changes">
    **Subject:** Congrats on the new role at `@Buyer Common Name`

    > Hi `@First Name`,
    >
    > `@[AI Snippet: "Write one sentence congratulating this person on their new role based on @Job Change."]`
    >
    > I'd love to share how we're helping other leaders in similar roles. Open to a quick conversation?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Conferences">
    **Subject:** Following up from `@Conference`

    > Hi `@First Name`,
    >
    > I saw that you'll be at `@Conference Name` in `@City`. `@[AI Snippet: "Explain in one sentence why @Conference @Conference Description is relevant to their work based on the conference focus areas"]`
    >
    > I'd love to connect while you're there to discuss how we're helping similar organizations. Would you have 15 minutes for a quick coffee?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Custom Web Signals">
    **Subject:** `@[AI Snippet: "Write a 3–5 word subject line referencing the most relevant finding in @Signal Finding"]`

    > Hi `@First Name`,
    >
    > `@[AI Snippet: "Write 2 sentences referencing @Signal Finding and why it's relevant to them. Be conversational and show you've done your research."]`
    >
    > I'd love to connect and share how we've helped organizations like `@Buyer Common Name` with similar initiatives. Would you be open to a brief chat?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Buyers">
    **Subject:** Thought of `@Buyer Common Name`

    > Hi `@First Name`,
    >
    > `@[AI Snippet: "Write 2–3 sentences explaining why we're reaching out to this specific @Buyer based on their profile, industry, or recent activity. Reference relevant buyer attributes or signals from cross-referenced bridges."]`
    >
    > We work with organizations like `@Buyer Common Name` to \[your value proposition]. Would you be interested in learning more?
    >
    > Best, \[Your name]
  </Tab>

  <Tab title="Contacts">
    **Subject:** Quick question for `@Buyer Name`

    > Hi `@First Name`,
    >
    > I'm reaching out because of your role as `@Job Title` at `@Buyer Common Name`.
    >
    > `@[AI Snippet: "Write 1–2 sentences about why this person's @Job Title makes them a good fit for our solution"]`
    >
    > Would you have a few minutes to connect?
    >
    > Best, \[Your name]
  </Tab>
</Tabs>

## Related

<CardGroup cols={2}>
  <Card title="Enriching Bridges with Data" icon="layer-group" href="/builders/enriching-bridges-with-data">
    The overview of all enrichment column types.
  </Card>

  <Card title="Syncing to Your CRM" icon="arrows-rotate" href="/crm-integration">
    Push generated emails to Salesforce or HubSpot.
  </Card>
</CardGroup>