Message templates give your team a starting point for every outreach scenario, so reps spend time personalizing messages rather than writing from scratch. In Signal Ark, templates go beyond simple merge tags — they support signal-aware placeholders that pull live context from an account’s timeline directly into the message body. Sales leaders can draft, review, and approve templates before making them available to the whole team.Documentation Index
Fetch the complete documentation index at: https://docs.signalark.app/llms.txt
Use this file to discover all available pages before exploring further.
Template categories
Templates are organized by channel and sales motion. You can browse all templates from Outreach > Templates in the left sidebar.Email templates
Cold outbound, signal-triggered follow-ups, multi-touch nurture messages, and breakup emails.
LinkedIn templates
Connection request notes (300-character limit) and direct message scripts for existing connections.
Call scripts
Discovery call openers, objection-handling frameworks, and voicemail scripts.
Play-specific templates
Pre-built templates tied to GTME Plays — ready to use when Signal Ark activates a play for an account.
Variables and signal-aware placeholders
Templates support two kinds of dynamic content: Standard variables are replaced with contact or account data at send time:| Variable | Replaced with |
|---|---|
{{first_name}} | Contact’s first name |
{{company}} | Account name |
{{title}} | Contact’s job title |
{{industry}} | Account’s industry |
{{sender_name}} | The sending rep’s name |
| Placeholder | Replaced with |
|---|---|
{{why_now}} | The primary Why Now summary for the account |
{{signal_event}} | The most recent high-intent signal event (for example, “Series B announcement”) |
{{competitor_name}} | The competitor name referenced in a displacement signal |
{{hire_title}} | The title of a recently hired executive |
Signal-aware placeholders only populate when the matching signal data exists on the account. If a placeholder cannot be resolved at send time, Signal Ark highlights it in the composer so you can fill it in manually before sending.
Creating a template
Open the template library
Go to Outreach > Templates and click New Template in the top-right corner.
Choose a category
Select the channel (email, LinkedIn, or call script) and the use case (cold outbound, follow-up, play-specific, and so on).
Write the message
Enter a subject line (for emails) and the message body. Insert variables by typing
{{ — a dropdown suggests available placeholders. Include at least one signal-aware placeholder to give the template context-sensitivity.Tag the template (optional)
Add tags to make the template searchable — for example, “displacement”, “executive hire”, or “Series B”. Tags help reps find the right template quickly when enrolling contacts.
Approval workflow
Signal Ark uses a lightweight approval workflow to ensure consistent messaging quality.Play-specific templates
The highest-converting templates are tied to specific GTME Plays. Signal Ark ships a set of built-in play templates you can use immediately or customize for your team:Competitor Crisis Displacement
Competitor Crisis Displacement
Addresses a recent competitor outage, breach, or public failure. The tone is tactful — acknowledge the situation without being opportunistic — and focuses on stability and support. Use
{{competitor_name}} and {{signal_event}} to tie the message directly to the incident.Executive Change Window
Executive Change Window
Welcomes a newly hired executive (CISO, CRO, VP of Sales, and so on) and asks about their priorities for the first 90 days. Use
{{hire_title}} to address their specific role and make the message feel timely rather than templated.Funding Expansion Blitz
Funding Expansion Blitz
Congratulates a company on a new funding round and highlights how your product scales with headcount and growth. Use
{{signal_event}} to reference the specific round (for example, “Series B”).Support Instability Displacement
Support Instability Displacement
Reaches out to buyers who have publicly complained about a competitor’s support quality. References the
{{why_now}} context to demonstrate that you noticed their frustration and can offer a better experience.