# FollowDeck Playbook AI Creation Guide

Product: FollowDeck  
Audience: FollowDeck users and AI assistants  
Status: Current  
Purpose: Help anyone use an AI assistant to create a FollowDeck-ready Playbook Markdown file and import it into FollowDeck.

---

# What This File Is For

Upload this file to an AI assistant such as ChatGPT, Gemini, Claude, Grok, Copilot, or another AI tool.

Then ask something simple, such as:

> I need a FollowDeck Playbook for onboarding new customers.

or:

> I need a Playbook for following up after I give someone an estimate.

or:

> I run a plumbing company. Make me a FollowDeck Playbook for taking a new service call.

The AI should help create a finished Markdown Playbook that can be saved as a `.md` file and imported into FollowDeck.

The AI must also explain, in simple steps, how to save and import the Playbook.

---

# What a FollowDeck Playbook Is

A FollowDeck Playbook is a practical procedure guide for a repeatable business process.

Examples include:

- Sales follow-up
- Customer onboarding
- Technical support
- Estimate follow-up
- Church outreach
- Service calls
- Lead qualification
- Customer retention
- Appointment preparation
- Job intake
- Billing follow-up
- Past-customer re-engagement
- Employee procedures
- Escalation procedures

A good Playbook should help answer:

- What should I do first?
- What questions should I ask?
- What information do I need?
- What should I say?
- What should I avoid saying?
- When should I schedule the next step?
- When should I escalate something?
- What should I record in FollowDeck afterward?

---

# FollowDeck Markdown Import Rules

The AI MUST follow these rules.

## File type

The finished file must be a Markdown file:

```text
.md
```

Example:

```text
Customer-Onboarding-Playbook.md
```

Do not create the import file as a PDF, Word document, DOCX, RTF, image, or spreadsheet.

## File size

Keep the Markdown file below 1 MB.

## First H1 = Playbook name

The first top-level heading must be the Playbook name:

```markdown
# Customer Onboarding Playbook
```

FollowDeck uses the first H1 as the Playbook name.

## Intro paragraph = description

Immediately below the H1, include a short plain-language description:

```markdown
# Customer Onboarding Playbook

Use this Playbook to guide staff through welcoming a new customer, gathering required information, setting expectations, and scheduling the next step.
```

## H2 headings = FollowDeck sections

Each main Playbook section must use an H2:

```markdown
## Before the First Call
```

```markdown
## Discovery Questions
```

```markdown
## Schedule the Next Step
```

Each H2 becomes a separate section in FollowDeck.

## H3 and deeper headings stay inside the H2 section

Use H3 for subsections:

```markdown
### Questions to Ask
```

```markdown
### Warning Signs
```

H3 headings stay inside the current H2 section.

## Normal Markdown formatting is allowed

The AI may use:

```markdown
- Bullet lists
1. Numbered steps
- [ ] Checklists
**Bold text**
*Italic text*
> Important notes or callouts
```

---

# Recommended Playbook Structure

Use this as a starting point and remove anything that does not apply.

```markdown
# [Playbook Name]

[One short paragraph explaining what this Playbook is for and when to use it.]

## Purpose

Explain the goal.

## Before You Start

List what the employee should review or prepare.

## Opening / First Step

Explain how to begin.

## Information to Gather

List required information.

## Questions to Ask

Provide useful questions in a logical order.

## Process / Procedure

Give the main step-by-step process.

## Common Situations

Explain common variations.

## Problems / Warning Signs

Explain what to watch for.

## Escalation Rules

Explain when to ask an Owner, Admin, manager, technician, or other authorized person for help.

## What Not to Do

State important boundaries.

## Schedule the Next Step

Explain when and how to schedule the next follow-up, appointment, call, email, or task.

## What to Record in FollowDeck

Explain what notes, activities, status changes, or follow-ups should be recorded.

## Completion Checklist

Give a short checklist.

## Quick Reference

Provide a short condensed version of the process.
```

Do not add filler just to make the Playbook longer.

---

# Instructions for the AI Assistant

When this file is uploaded, follow these instructions.

## Your job

1. Understand what process the person wants documented.
2. Ask only the questions necessary to make the Playbook useful.
3. Organize the procedure into FollowDeck-compatible Markdown.
4. Write for the employee who will actually use it.
5. Produce a finished `.md` file or complete Markdown that can be saved as a `.md` file.
6. Give simple FollowDeck import instructions at the end.

## Questions to ask when needed

Ask only what is necessary, such as:

- What is this Playbook for?
- Who will use it?
- What should they accomplish?
- Are there required steps that must always be followed?
- Are there prices, policies, promises, legal/security rules, or approval rules that must be exact?
- When should the employee escalate?
- What should be recorded in FollowDeck afterward?

If the user already gave enough information, do not ask unnecessary questions.

## Do not invent official company information

Never invent:

- prices
- guarantees
- legal terms
- warranties
- response times
- discounts
- company policies
- security promises
- contract terms

Ask for those details or use a placeholder, for example:

```text
[Insert approved service rate here]
```

---

# Writing Style

The Playbook should be:

- practical
- clear
- easy to scan
- plain language
- organized in the order the work happens
- specific enough to be useful
- concise enough to use while working

Prefer:

```markdown
- Confirm the customer's name.
- Verify the best callback number.
- Ask what changed since the last visit.
- Record the result in FollowDeck.
```

Avoid long, vague corporate language.

---

# Useful Content Types

The AI may include:

## Suggested scripts

```markdown
### Suggested Opening

"Hello, this is [Name] with [Company]. I'm following up about [reason]. Is now a good time for a quick conversation?"
```

## Discovery questions

```markdown
### Questions to Ask

- What are you trying to accomplish?
- When did the issue begin?
- Has anything changed recently?
- Who is affected?
- Is there a deadline?
```

## Checklists

```markdown
### Before Ending the Call

- [ ] Confirm the next step.
- [ ] Confirm the best contact method.
- [ ] Create the next Follow-Up.
- [ ] Record useful notes.
- [ ] Update the lead/customer status if appropriate.
```

## Decision guidance

```markdown
### If the Customer Is Ready

1. Confirm what they want.
2. Schedule the next step.
3. Record the result in FollowDeck.

### If the Customer Is Not Ready

1. Ask when to follow up.
2. Create a Follow-Up for that date.
3. Record the reason.
```

## Escalation guidance

```markdown
### Escalate When

- The customer requests something outside the employee's authority.
- Pricing or contract terms are unclear.
- The situation involves a security concern.
- The employee is unsure what promise can be made.
```

---

# Protect Sensitive Information

A FollowDeck Playbook is not a password vault.

Do NOT place these in a Playbook:

- passwords
- API keys
- MFA backup codes
- private encryption keys
- credit card information
- bank credentials
- recovery codes
- secret tokens
- SIP passwords
- mailbox passwords
- sensitive customer credentials

Instead write:

```markdown
Use the company's approved password manager for credentials.
```

or:

```markdown
Contact an Owner/Admin if credentials are required.
```

---

# Example FollowDeck-Compatible Playbook

```markdown
# Estimate Follow-Up Playbook

Use this Playbook when following up with a prospect after an estimate has been provided. The goal is to answer questions, determine whether the customer is ready to move forward, and make sure the next action is scheduled.

## Before Contact

- Review the customer record.
- Review the estimate.
- Check the Activity Timeline.
- Review any promised follow-up date.
- Do not change approved pricing or terms without authorization.

## Opening

### Suggested Opening

"Hello, this is [Name] with [Company]. I'm following up on the estimate we sent for [service/project]. I wanted to make sure you received it and see whether you had any questions."

## Questions to Ask

- Did you receive the estimate?
- Have you had a chance to review it?
- Is there anything you would like clarified?
- Has anything about the project changed?
- Is there a timeframe you are working toward?
- Is there anything preventing you from moving forward?

## If the Customer Is Ready

1. Confirm what they want to move forward with.
2. Follow the company's approved scheduling or authorization process.
3. Confirm the next appointment or step.
4. Record the result in FollowDeck.
5. Create any necessary Follow-Up.

## If the Customer Needs More Time

- Ask when they would like to be contacted again.
- Create a Follow-Up for that date.
- Record any concern or reason they mentioned.

## If the Customer Has a Pricing Question

Only explain approved pricing or terms.

Do not invent discounts or promise pricing changes.

If approval is required, say:

"I want to make sure I give you the correct information. Let me confirm that and get back with you."

Then escalate to the appropriate Owner/Admin.

## What Not to Do

- Do not pressure the customer.
- Do not invent discounts.
- Do not change approved terms.
- Do not promise a schedule that has not been confirmed.
- Do not criticize competitors.

## What to Record in FollowDeck

Record:

- whether the customer answered
- major questions or concerns
- whether they are ready to proceed
- agreed next step
- next follow-up date
- important notes

## Completion Checklist

- [ ] Contact attempt recorded
- [ ] Questions documented
- [ ] Status updated if appropriate
- [ ] Next step confirmed
- [ ] Follow-Up created if needed

## Quick Reference

1. Review estimate and history.
2. Confirm they received the estimate.
3. Ask what questions they have.
4. Determine whether they are ready, need more time, or need clarification.
5. Record the result.
6. Schedule the next step.
```

---

# What the AI Must Deliver at the End

## 1. Finished Playbook

Preferably create a downloadable file named something like:

```text
Company-Process-Playbook.md
```

If the AI cannot create a downloadable file, provide the complete Markdown in one fenced code block and tell the user to save it as a `.md` file.

## 2. Review reminder

Tell the user to review any:

- pricing
- company policies
- guarantees
- legal language
- approval rules
- escalation rules
- company-specific facts

before importing.

## 3. FollowDeck import instructions

Always give the instructions below.

---

# How to Import the Playbook Into FollowDeck

1. Save or download the finished file as a Markdown file ending in:

```text
.md
```

Example:

```text
Customer-Onboarding-Playbook.md
```

2. Sign in to the correct FollowDeck organization.

3. Open **Playbooks**.

4. Choose the **Import Markdown** or **Import Playbook** option in the Playbooks area.

5. Select the `.md` file.

6. FollowDeck will show a preview before the Playbook is written.

7. Review the preview carefully.

Make sure:

- the Playbook name is correct
- the description is correct
- each H2 became the expected section
- bullets and formatting look correct
- no passwords, API keys, or other secrets are included
- company pricing and policy information is accurate

8. Complete the import if the preview looks correct.

9. Open the imported Playbook and review it once more before employees begin using it.

10. If desired, link the Playbook to the appropriate Business or Lead and set it as the Primary Playbook.

## Permission note

Current FollowDeck Playbook creation/import is intended for users with appropriate management permissions, normally an **Owner or Admin**.

If the import option is not visible, ask the FollowDeck Owner/Admin to import the file.

---

# Troubleshooting Import Problems

## Wrong Playbook title

The first title should use exactly one `#`:

```markdown
# Playbook Name
```

## Sections did not split correctly

Main sections must use:

```markdown
## Section Name
```

H3 is only a subsection:

```markdown
### Subsection
```

## No description

Put a short paragraph directly under the first H1 and before the first H2.

## File will not upload

Check that:

- the file ends in `.md`
- it is not a PDF, DOCX, or TXT file renamed incorrectly
- it is below 1 MB

## Import option is missing

The user may not have Owner/Admin permission.

Ask the organization's FollowDeck Owner/Admin.

---

# Simple Prompts a User Can Give the AI

After uploading this guide, a user can simply say:

```text
I need a FollowDeck Playbook for onboarding new customers.
```

```text
Make me a FollowDeck Playbook for following up after I give someone an estimate.
```

```text
I run a plumbing company. Help me make a Playbook for an employee taking a new service call.
```

```text
I need a sales Playbook for someone calling leads from our Chamber of Commerce list.
```

```text
I need a Playbook for handling a customer complaint.
```

```text
Create a Playbook for a technician arriving at a customer's business for the first time.
```

---

# Recommended Prompt for Best Results

```text
I use FollowDeck and uploaded the FollowDeck Playbook AI Creation Guide.

Help me create a Playbook for:

[describe the process]

Ask me any important questions you need, but keep them simple.

Then create a finished FollowDeck-compatible Markdown file that I can import.

Do not invent company pricing, guarantees, legal terms, or policies.

At the end, give me simple instructions for importing the Playbook into FollowDeck.
```

---

# Final Instruction to the AI

The finished Playbook should be something an employee can actually use while doing the job.

Do not optimize for length.

Optimize for:

```text
Clear
Practical
Accurate
Easy to scan
Easy to follow
Easy to import into FollowDeck
```

Always finish by helping the user save/download the `.md` file and explaining how to import it into FollowDeck.
