# Set Up the Outbound Email Skill



The **Surface Outbound App** skill guides your AI agent through setting up an
outbound email app on Surface. It uses an app database for campaign records,
focused tasks for research and drafting, and a read-only Overview for progress.

<SkillPackage name="surface-outbound-app" title="Surface Outbound App" />

The skill is designed to take setup through test runs and recurring operation
once the required campaign rules, copy, and connections are ready. Research runs
may consume provider credits. It prepares inactive drafts; it does not enroll
recipients, activate provider campaigns, or send emails.

## What You Will Set Up [#what-you-will-set-up]

| Task               | What It Does                                                                                         | What It Saves                                                          |
| ------------------ | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Manager**        | Checks the pipeline hourly and selects the stage with actionable work, prioritizing downstream work. | Counts and a routing summary.                                          |
| **Prospect**       | Finds companies that match your target segment and checks account fit.                               | Company records, sources, and campaign-specific fit decisions.         |
| **Qualify**        | Checks supporting evidence when your campaign requires a separate qualification gate.                | Decisions, evidence, and pending research.                             |
| **Find Contacts**  | Researches approved personas at eligible companies and looks up emails.                              | Contact records, sourced emails, and company associations.             |
| **Draft Outreach** | Personalizes the approved email sequence for eligible contacts.                                      | Rendered copy and, where supported, verified inactive provider drafts. |

Only the Manager has an hourly schedule. The skill configures stages to run
through follow-ups: continue their own queue, hand work to the next stage, or
return to the Manager. Qualify is optional; without it, Prospect owns the
required outreach evidence checks.

The app database holds accounts, contacts, evidence, provider job IDs, drafts,
holds, and run summaries. The Overview presents those records and task health.
The skill reuses a compatible app for the same seller and email channel, with
separate campaign rules and task sets for each segment.

If the available email tools cannot support inactive drafts, the skill can use
a **database-only** strategy: save and verify rendered copy in the app without
creating provider drafts. It reports that distinction explicitly.

## Before You Start [#before-you-start]

You will need:

* An AI agent connected to Surface MCP. To install the ZIP for repeat use,
  your agent also needs local skill support.
* Access to app, database, scheduled-task, and Overview tools through MCP.
  Ask your agent to verify which tools and connections your environment exposes.
* Connected research providers for the discovery and contact work you want.
  Provider-backed drafting also needs a suitable email connection.
* Your company website, target accounts, contact personas, exclusions, and any
  qualification criteria.
* Approved email copy and a confirmed sender name and mailbox before drafting.

Connect your agent using [Surface MCP Setup](https://www.withsurface.com/docs/mcp-server/setup). The skill checks
the target environment and connected account before creating tasks, and asks
for missing business details or provider connections as needed.

## Choose How to Use It [#choose-how-to-use-it]

**Copy instructions** is the quickest way to start. Paste the combined Markdown
into an agent connected to Surface MCP, then provide your campaign details.
All supporting instructions are included; no local skill files are needed.

**Download skill*&#x2A; is the reusable installation option. Extract the ZIP and place
the entire **`surface-outbound-app` folder** in your agent's skills directory.
Use your agent's installation instructions to choose the location.

Keep all eight files together:

```text
surface-outbound-app/
  SKILL.md
  agents/
    openai.yaml
  references/
    app-setup.md
    database-contract.md
    next-steps.md
    overview-ui.md
    recovery.md
    task-instructions.md
```

`SKILL.md` is the entry point. The references cover app setup, database records,
guided next steps, the Overview, task instructions, and recovery. Copying only
`SKILL.md` leaves the instructions incomplete.

## Set Up Your First Campaign [#set-up-your-first-campaign]

Paste this prompt after the copied instructions, or invoke the installed
`surface-outbound-app` skill with these details:

```text
Use the Surface Outbound App skill to set up my outbound email campaign.

Company: [company name and website]
Surface environment or existing app: [team, environment, or app URL]
Target accounts: [industry, geography, company size]
Target contacts: [roles or personas]
Qualification: [required criteria, or no separate qualification stage]
Offer: [what we can help with]
Exclude: [customers, competitors, domains, or other exclusions]
Preferred providers: [names, or inspect my available Surface connections]
Sender: [confirmed mailbox and first name]
Timezone: [for example, America/Los_Angeles]

Reuse a compatible app or create one, set up its database and campaign rules,
create the Manager and stage tasks, and publish the Overview. Ask me for
missing details and approval of the email copy. Once prerequisites are ready,
test the stages, verify saved results, and enable the Manager and follow-ups.
Keep drafts inactive. Do not enroll recipients or send emails.
```

The agent should guide you through missing decisions one at a time, with a
progress count and a plain-language next step. Its default workflow includes
commissioning and activation of Surface tasks. To limit the work, add:
&#x2A;*"Setup only. Leave all tasks paused; do not run tests or enable recurrence."**

## Review and Verify the Pipeline [#review-and-verify-the-pipeline]

Open the app and task links returned by your agent. Review:

* **Campaign rules:** target accounts, personas, exclusions, qualification,
  and approved copy and sender.
* **Overview:** the campaign's next decision, with companies, contacts, drafts,
  evidence, and operational detail available through focused pages and row drawers.
  A published page is not proof of visual inspection; without a renderer, the
  skill reports "visually unverified". Sidekick review buttons request review,
  never enrollment, campaign activation, or sending.
* **Task configuration:** campaign scope, provider access, timezone, limits,
  and the Manager's schedule and follow-up routing.
* **Saved outcomes:** actual database rows and complete rendered copy; for
  provider drafts, the saved provider ID, content readback, and inactive state.

The skill starts with bounded batches and raises throughput only after runs
consistently save their expected work. Provider results are persisted promptly,
exact jobs are resumed, and the run summary is saved last. A COMPLETED label
alone does not establish that records or drafts were saved.

Activation alone is also not proof that recurrence works. The skill calls for
checking an actual scheduled Manager run and the follow-up it starts. If that
check is still pending, the agent should say so and give you a time to check back.
Sending remains a separate action outside this skill.

## Monitor Progress and Recover [#monitor-progress-and-recover]

Ask your agent to &#x2A;*"Check the pipeline for \[campaign] over \[time window]."**
It should inspect current database records, saved summaries, task activity,
unresolved writes, and follow-up routing. Reports separate actionable work,
waiting retries, and holds that need a person to act. A health check alone
does not authorize edits or extra runs.

If a run fails after a provider change, that change may still exist. The skill
directs the agent to reconcile saved operation IDs and actual provider state
before retrying, so failed runs do not become duplicate research or drafts.
Operational records stay in the app database; this version does not use Vault
files for campaign queues, checkpoints, or task instructions.
