Best Practices

A playbook is the brain of your campaign. It defines strategy, messaging, sequencing, and how the AI agent behaves when prospects reply. The agent behind each campaign reads the playbook as its operating guide—so clarity in the playbook directly shapes outreach quality and reply handling.

Use this guide when creating or refining playbooks, whether you start with Generate with AI or Build Manually.

Quick Start: Generate with AI

Generate with AI is the fastest way to get a complete starting playbook. Ragworks researches your business and drafts sequences, value proposition, and response guidelines automatically.

→ Follow step-by-step instructions in Generate with AI.

After generation, do not publish blindly. The two areas that matter most for live performance are:

1. Outreach sequence — cadence, channel steps, and message templates
2. Response guidelines — how the agent replies when prospects are interested, not interested, or ready to book

After AI Generation: What to Review First

Priority	Section	Why it matters
1	Outreach sequence	Controls connection requests, follow-ups, and email touches
2	Response guidelines	Controls live reply behavior when prospects engage
3	Target audience & value proposition	Fine-tune if personas or positioning are off
4	Signatures	Email and LinkedIn sign-off rules

Read the full playbook end-to-end as if you were a prospect before publishing.

Outreach Sequence: Cadence and Scripts

If you have working examples of cadence scripts, paste or adapt them on the appropriate steps rather than leaving generic AI placeholders.

Step type	What to configure
Connection request message	Short, human invite—no pitch wall
Initial outreach	First message after connect or first email touch
Follow-up 1, 2, 3	Escalating value or angle; stay brief
Additional steps	Persona tone, word limits, channel-specific rules

You can add more steps beyond the default cadence to give the agent persona and style rules—for example:

• Use minimal words; avoid robotic phrasing
• No exclamation-heavy sales tone
• One clear CTA per message
• Match formality to persona (executive vs practitioner)

tip

Connection request message: keep it simple

Hi {{Name}}, I'm the Co-founder at Ragworks AI, connecting with leaders scaling outbound. 
Thought it makes sense to connect.

Connection requests should feel like a natural LinkedIn invite, not a mini sales deck.

Research Depth and Hooks

Every Agentic step has a Research depth (Basic, Standard or Deep) and an Advanced section with hooks, tone and a never-mention list. A few habits that pay off:

• Start at Standard. Funding, hiring and what a company's website says give most messages a real reason to write. Move to Basic for high-volume lists, and to Deep only for small lists where one very specific opener is worth the price.
• Research once, use it everywhere. Every step reuses a lead's research, so adding a follow-up does not add research cost.
• Give later steps a new angle. Ragworks avoids repeating a hook it already used on that lead. Say in the step's instructions what the follow-up should add, so the agent has somewhere to go.
• Use Never mention. Add competitor names, layoffs or anything else your team would not want a message to bring up.
• Check before you launch. Run Preview 3 leads to see a message at each depth, then Simulate for a whole conversation.

→ Full guide: Research depth and hooks

Persona and Agent Behavior Blocks

Response quality often comes from explicit blocks in the playbook, not only from the base model.

Add dedicated steps or guideline blocks when you need the agent to:

• Sound like a specific role (founder, AE, SDR)
• Enforce brevity or tone (conversational, direct, no jargon)
• Handle one objection angle per reply
• Avoid stacking multiple arguments in a single message

If you need a specific block or step for persona rules, add it—the playbook editor supports extra steps for exactly this purpose.

Out of Scope Exit (When to Stop Engaging)

Do not dictate that the agent should exit at the first objection. The default behavior should be objection handling through the not-interested guidelines until clear resistance appears.

Exit the conversation only when:

• A clear "no" with no intention to continue, or "rejected" at least twice
• Multiple low-effort replies and clear disinterest
• Wrong contact with no referral path
• Hostility or annoyance signals

When exiting, leave a soft re-entry—do not burn the bridge.

Exit example:

Completely understand and appreciate the reply.
Door's open if anything changes or you want to ask about any of the other services we offer.

warning

Avoid playbook rules that say "exit on first objection." That short-circuits qualification and hurts reply rates.

Response Guidelines

Response guidelines tell the agent how to behave after the prospect replies. Configure each subsection in the playbook editor.

Interested

When a lead shows interest, decide how aggressively you want to push for a meeting.

Option A — Push immediately to a meeting

Thank the prospect for their interest and immediately push towards bringing them to a 30 mins meeting.

Option B — Confirm slots + Calendly

Use when you offer specific times and a booking link:

Confirm their availability from the times already offered - Tuesday or Wednesday at 10am or 11am PST and their best email to send the invite as well. Also give the option of a direct meeting link: https://calendly.com/d/<id>, allowing them to book directly.

Replace <id> with your real Calendly path.

Option C — Qualify before booking

Thank them for their interest and offer a relevant resource (e.g., a link to the 'Campaign Playground' or a specific success story).
Ask a qualifying question to understand their specific challenges or goals (e.g., 'What's your biggest challenge with pipeline generation right now?').
[Email] Provide a direct link to a relevant page on ragworks.ai for more information.

Pick one primary path per playbook so the agent does not mix conflicting CTAs.

Not Interested (Objection Handling)

Use not interested guidelines to enforce structured objection handling—not instant exit.

DO's (objection handling enforcement):

• Start with clarify → ask what is behind the objection (do not assume)
• Then explore context (timing, priority, current solution)
• Challenge lightly with a relevant angle (ROI, missed opportunity, or alternative view)
• Extract one useful data point (e.g., "when would this be relevant?")
• Keep each step short (1–2 sentences)—no long persuasion
• Stay calm and neutral, never defensive or pushy
• Handle one angle per reply (do not stack arguments)
• Exit only after clear resistance (repeated "no", no replies, firm disengagement)
• If exiting, leave a soft re-entry (future timing or open loop)

This pairs with the Out of scope exit rules above - handle objections first, exit only when criteria are met.

Calendar Message

Configure how the agent proposes meetings:

Propose 2-3 specific time slots for a brief discussion.
Include the Calendly link: https://calendly.com/d/, allowing them to book directly.
If Calendly is not used, your email/calendar integration will be used automatically.
Follow up once if there is no response to the proposed times; then cease further scheduling attempts for this outreach cycle.

Adjust slots and links to match your timezone and booking setup.

Email Signature

Ragworks adds no closing line of its own to an email (no "Best regards,") and no sender name. The message is followed by the signature set on the connected email account, as-is.

Scenario	What is sent
Signature configured on the account	The message, then the signature as-is. No closing line is added in between.
No signature configured	The message only. Nothing is added after it.

To close with a line such as "Best regards,", end the message with it or put it at the top of the signature.

LinkedIn Signature

Message type	Rule
Initial outreach	Follow configured LinkedIn signature / sign-off settings
All other LinkedIn messages	Ignore signatures—do not append sign-off blocks to follow-ups or thread replies

This keeps LinkedIn threads readable and avoids repetitive footer text on every touch.

Pre-Launch Checklist

• Playbook objectives and audience match the campaign ICP
• Outreach sequence steps map to your real cadence (connection → initial → follow-ups)
• Connection request is short and non-salesy
• Interested / not interested guidelines match your GTM motion
• Exit rules require clear resistance—not first objection
• Calendar message includes correct slots and Calendly (if used)
• Email signature rules match your template setup
• LinkedIn signature rule: only initial outreach (if applicable)
• Full read-through completed before Publish

Related Documentation

• Best Practices for Creating Playbooks
• Playbook overview
• Generate with AI faster alternative for first-time setup
• Create a Campaign