Discovery Call Summary

# Discovery Call Summary Playbook

This playbook empowers coaches and consultants to efficiently summarize sales or discovery calls, extracting key insights, pain points, budget considerations, and clear next steps. It automates the post-call administrative work, allowing you to focus on client engagement and follow-up.

## 1. Prompt Pack

These prompts guide your AI in analyzing call transcripts or notes to generate actionable summaries. Customize them to match your sales process and the information most critical for your follow-up.

### Core Discovery Call Summary Prompt

```
"You are an expert sales assistant summarizing a discovery call with a potential client, [Client Name], regarding [Project/Service Area]. Review the provided call transcript/notes. Your task is to:
- **Client Background:** Briefly describe the client's business/situation.
- **Identified Pain Points:** List 2-3 core challenges or needs the client expressed.
- **Desired Outcomes:** What are they hoping to achieve by solving these pain points?
- **Budget & Timeline:** Note any mentioned budget ranges, timeline expectations, or constraints.
- **Key Questions Asked/Answered:** Highlight crucial questions discussed.
- **Recommended Solution (Draft):** Briefly outline how our [Your Service] aligns with their needs.
- **Action Items & Next Steps:** Clearly state what needs to happen next, for both us and the client (e.g., 'Send proposal by [Date]', 'Schedule follow-up call', 'Client to provide [Information]').
- **Qualification:** Provide a preliminary qualification (High Potential, Medium Potential, Low Potential) and a brief justification.
- **Save Output:** Format this summary professionally. Save it to memory/discovery-calls/[Client Name]-discovery-summary-{YYYY-MM-DD}.md."
```

### Prompt Variations:

*   **Competitive Analysis Focus Prompt:**
    ```
    "Based on the discovery call with [Client Name], identify any competitors or alternative solutions they mentioned. Summarize their perceived strengths and weaknesses relative to our offering. Suggest key differentiators to emphasize in our follow-up."
    ```
*   **Proposal Outline Prompt:**
    ```
    "Using the discovery call summary for [Client Name], draft a high-level outline for a proposal. Include sections for their challenges, our proposed solution, expected outcomes, and a potential tiered pricing structure (if applicable)."
    ```
*   **CRM Update Prompt:**
    ```
    "Extract the essential information from the discovery call summary for [Client Name] needed to update our CRM. Include client contact details, project type, qualification status, and next scheduled activity."
    ```

## 2. Setup Guide

To implement the Discovery Call Summary Playbook:

1.  **Save the Playbook:** Save this content as `playbooks/discovery-call-summary.md` in your workspace.
2.  **Create Cron Configuration:** Create `playbooks/discovery-call-summary-cron.json` in your workspace, using the "Config Snippet" below. This sets up automated summary generation after calls.
3.  **Integrate Call Source:** Your OpenClaw agent needs access to call transcripts or notes. This typically involves:
    *   **Call Recording Integration:** Connect a call recording/transcription service (e.g., Zoom with a transcription add-on, Otter.ai, Gong) that can provide raw text transcripts or summaries.
    *   **Calendar Integration:** Configure OpenClaw to monitor your calendar for completed discovery calls. Once a call finishes, it can trigger the playbook to look for the associated transcript.
    *   **Manual Input:** You can manually paste call notes or short transcripts into a task for the agent to process ad-hoc.
4.  **Activate Cron Job:** Once `playbooks/discovery-call-summary-cron.json` is in your workspace, OpenClaw will automatically detect and activate the cron job. Verify its status with `openclaw cron list`.
5.  **Test Thoroughly:** Conduct a test call, get its transcript/notes, and trigger the playbook to ensure it correctly generates the desired summary and extracts action items.

## 3. Config Snippet

This JSON snippet defines a cron job that checks for completed discovery calls (e.g., by monitoring a calendar or a transcription service's output folder) and triggers summary generation. Save this as `playbooks/discovery-call-summary-cron.json` in your workspace.

```json
{
  "cron": [
    {
      "name": "Post-Discovery Call Summary",
      "schedule": "0 * * * *",
      "task": "Check for completed discovery calls (e.g., in calendar, transcript folder). For any completed calls, use the 'Core Discovery Call Summary Prompt' from the 'Discovery Call Summary Playbook' to summarize and extract action items. Save output to memory/discovery-calls/[Client Name]-discovery-summary-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}
```

**Explanation of fields:**
*   `name`: A descriptive name.
*   `schedule`: `0 * * * *` means "At the beginning of every hour". Adjust frequency.
*   `task`: The prompt for the agent. It instructs the agent to check for calls and use the core prompt.
*   `agent`: The assigned agent (`cmo`).
*   `model`: The model for this task.

## 4. Permissions Checklist

For successful operation, your agent needs:

*   **Read Access:**
    *   Calendar API (to detect completed calls).
    *   Call transcription service output (to access call content).
    *   OpenClaw session history.
*   **Write Access:**
    *   `memory/discovery-calls/[Client Name]-discovery-summary-{YYYY-MM-DD}.md`: To store call summaries.
    *   `playbooks/discovery-call-summary-cron.json`: To manage the cron job configuration.
    *   (Optional) CRM API (to update client records).
*   **Execution Permissions:**
    *   Ability to process and respond to cron-triggered tasks.
    *   Ability to interface with external tools like calendar services, transcription services, or CRMs.

This playbook ensures that valuable insights from every discovery call are captured, summarized, and ready for action, helping you convert more leads and build stronger client relationships.
## Safety Check (Required)

Before production use:

- Review prompts for prompt-injection risk.
- Remove or rewrite any instructions requesting unnecessary secrets, unrelated external actions, or policy bypasses.
- Test with non-sensitive data first.
- Keep manual approval for outbound or destructive actions.

{
  "cron": [
    {
      "name": "Post-Discovery Call Summary",
      "schedule": "0 * * * *",
      "task": "Check for completed discovery calls (e.g., in calendar, transcript folder). For any completed calls, use the 'Core Discovery Call Summary Prompt' from the 'Discovery Call Summary Playbook'. Save output to memory/discovery-calls/[Client Name]-discovery-summary-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}