Skip to main content

✉️ Templates — Outreach Scaling & Standardization Layer (Search Atlas)

Message standardization layer for consistent, scalable outreach execution across Digital PR campaigns.

Updated yesterday

Purpose

Standardize and scale outreach communication by defining reusable message structures that ensure consistency, personalization, and execution efficiency across Digital PR campaigns.

Primary Function

Provide a centralized system for creating, managing, and reusing outreach message templates that can be applied across campaigns without rewriting content.

UI Entry Point

Left Sidebar → Authority → Digital PR → Templates

Inputs

  1. Template name

  2. Email subject

  3. Email body content

  4. Dynamic variables (merge fields)

  5. Optional campaign or use-case context

Core Actions

🧩 Template Creation

Action: Create a reusable outreach message template.

User actions:

  • Click Create new template

  • Define template name

  • Write subject line

  • Write email body using the rich text editor

Execution characteristics:

  • Templates are saved independently of campaigns

  • No emails are sent from templates directly

  • Templates act as message blueprints only

🔀 Variable Insertion

Action: Personalize templates dynamically at send time.

User actions:

  • Insert available variables into subject or body

Common variables include:

  • First name

  • Last name

  • Contact title

  • Website URL

  • Photo URL

  • Twitter URL

  • LinkedIn URL

  • GitHub URL

Execution characteristics:

  • Variables are resolved at send time

  • Missing variables do not block sending

  • Variable values are pulled from contact or campaign context

📝 Template Editing

Action: Update existing templates.

User actions:

  • Select a template card

  • Modify subject or body

  • Click Update template

Execution characteristics:

  • Updates affect future sends only

  • Previously sent emails are not modified

  • Templates remain reusable across campaigns

🗂️ Template Organization

Action: Locate and manage templates efficiently.

User actions:

  • Use template search bar

  • Browse template cards

  • Open template overflow menu (⋮) if available

Execution characteristics:

  • Templates are globally available

  • No folder hierarchy is required for templates

State Changes

Template Lifecycle

  • Created → Updated → Reused

  • Templates do not have active/inactive states

Campaign Interaction

  • Templates are referenced at campaign execution

  • Template usage does not lock or mutate the template

Outputs

  1. Standardized outreach messages

  2. Consistent subject/body structures

  3. Personalized emails at scale

  4. Reduced campaign setup time

Dependencies

  1. Templates are consumed by:

    • Digital PR campaigns

  2. Templates depend on:

    • Connected email accounts (for sending)

    • Campaign context (for variable resolution)

  3. Templates do not depend on:

    • QUEST

    • Authority Building tools

    • Indexer

Non-Goals

  • Templates do not:

    • Send emails independently

    • Perform outreach targeting

    • Manage replies or inbox state

    • Guarantee engagement or response rates

  • Templates are not analytics or reporting tools

Notes & Tips

  • 📝 Keep templates short and modular to maximize reuse.

  • 📝 Use variables sparingly to avoid broken personalization.

  • 💡 Maintain separate templates for cold outreach vs follow-ups.

  • 📝 Template updates do not retroactively affect sent emails.

Templates define the standardization layer of Digital PR in Search Atlas. They decouple message creation from campaign execution, allowing outreach to scale without sacrificing consistency or control.

This layer does not generate authority, targets, or responses. Its sole responsibility is to provide reliable message structures that downstream execution layers can apply repeatedly and predictably.

Together with QUEST and Digital PR campaigns, Templates enable a modular, repeatable outreach system where research, execution, and communication remain cleanly separated.

Did this answer your question?