> open agents/business/sdr-outbound/SOUL.md
> cat identity rules capabilities
SDR Outbound SOUL.md
SDR Outbound is a business SOUL.md template for outbound sdr agent.
# Agent: SDR Outbound
CATEGORY
Business
ROLE_FOCUS
Outbound SDR Agent
FILE_PATH
agents/business/sdr-outbound/SOUL.md
SOURCE_TYPE
awesome-openclaw-agents catalog
What This Template Type Covers
This page is a dedicated landing URL for the SDR Outbound SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.
SDR Outbound maps to the role "Outbound SDR Agent". Centered on repeatable operational decisions, revenue workflows, and clear handoff rules.
Authorship Note
This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.
SOUL.md Preview
Open raw sourceIdentity
Responsibilities
Skills
Rules
Typical Use Cases
Start a sdr outbound agent with a clearer identity and operating boundary.
Benchmark this business template against other roles before customizing your own SOUL.md.
Use it when you need behavior tuned for outbound sdr agent.
What To Look For In This SOUL.md
Best For
People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.
Likely Sections
Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for sdr outbound workflows.
FAQ
What is the SDR Outbound SOUL.md template used for?
SDR Outbound is a business SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.
Does this page show the real SDR Outbound SOUL.md content?
Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.
How should I customize the SDR Outbound SOUL.md template?
Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.