Testimonial Collection

# Testimonial Collection Playbook

This playbook automates the strategic collection of testimonials and reviews from happy clients. It helps service businesses consistently gather social proof at opportune moments (e.g., after project completion), enhancing credibility and supporting marketing efforts without manual outreach.

## 1. Prompt Pack

These prompts guide your AI in crafting polite and effective requests for client testimonials. Customize them to match your brand voice and project milestones.

### Core Testimonial Request Prompt (Post-Project Completion)

```
"You are a client success assistant. The project for [Client Name] (for [Service/Project]) has just been successfully completed. Draft a polite and appreciative email requesting a testimonial or review. Include:
- A brief thank you for their business and positive collaboration.
- A specific request for a testimonial or review (e.g., 'a short statement about their experience', 'a Google review').
- A clear, easy way for them to provide it (e.g., 'a direct link to our review page: [Review Link]', 'reply to this email').
- Reassure them that their feedback is valuable and helps other clients.
- Save this draft to memory/testimonials/[Client Name]-testimonial-request-{YYYY-MM-DD}.md."
```

### Prompt Variations:

*   **Mid-Project Check-in & Feedback Prompt:**
    ```
    "Mid-way through the project for [Client Name], draft an email checking in on their satisfaction and asking for any initial feedback. If feedback is positive, gently hint at the value of a future testimonial after completion."
    ```
*   **Specific Platform Request Prompt:**
    ```
    "Draft an email for [Client Name] requesting a review specifically on [Platform, e.g., Clutch, G2, your website]. Provide a direct link to the review page and briefly explain why their feedback on that platform is particularly helpful."
    ```
*   **Video Testimonial Outreach Prompt:**
    ```
    "For a highly satisfied client, [Client Name], draft a personalized email gently proposing a short video testimonial. Explain the impact of video, offer to guide them through the process, and provide options for how they can record it."
    ```

## 2. Setup Guide

To implement the Testimonial Collection Playbook:

1.  **Save the Playbook:** Save this content as `playbooks/testimonial-collection.md` in your workspace.
2.  **Create Cron Configuration:** Create `playbooks/testimonial-collection-cron.json` in your workspace, using the "Config Snippet" below. This sets up automated checks for project completion and triggers testimonial requests.
3.  **Integrate Project Tracking/Completion:** Your OpenClaw agent needs a way to know when a project or service phase is completed and deemed successful. This typically involves:
    *   **Project Management Tool Integration:** Connect to your PM tool (e.g., Asana, Trello, Jira) to monitor project status (e.g., 'Done', 'Completed').
    *   **CRM Integration:** Monitor client records for project completion dates or satisfaction markers.
    *   **Manual Trigger:** You can manually notify the agent that a project for a specific client is complete.
4.  **Define Timing Rules:** Determine the optimal timing for testimonial requests (e.g., 3 days after project completion, 1 week after final deliverable). Configure the cron job and task prompts accordingly.
5.  **Customize Request Template:** Adapt the `Core Testimonial Request Prompt` and its variations to include your specific review links, brand tone, and any incentives (if offered).
6.  **Activate Cron Job:** Once `playbooks/testimonial-collection-cron.json` is in your workspace, OpenClaw will automatically detect and activate the cron job. Verify its status with `openclaw cron list`.
7.  **Test Thoroughly:** Use a test project completion to ensure the AI drafts the request correctly and at the right time.

## 3. Config Snippet

This JSON snippet defines a cron job that periodically checks for completed projects and initiates testimonial requests. Save this as `playbooks/testimonial-collection-cron.json` in your workspace.

```json
{
  "cron": [
    {
      "name": "Daily Testimonial Request Check",
      "schedule": "0 9 * * *",
      "task": "Check connected project management tools/CRMs for projects completed within the last 3 days. For each, use the 'Core Testimonial Request Prompt (Post-Project Completion)' from the 'Testimonial Collection Playbook' to draft a testimonial request. Save to memory/testimonials/[Client Name]-testimonial-request-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}
```

**Explanation of fields:**
*   `name`: A descriptive name.
*   `schedule`: `0 9 * * *` means "At 09:00 every day".
*   `task`: The prompt for the agent. It instructs the agent to check for completed projects and draft testimonial requests.
*   `agent`: The assigned agent (`cmo`).
*   `model`: The model for this task.

## 4. Permissions Checklist

For successful operation, your agent needs:

*   **Read Access:**
    *   Project management system API (to fetch project completion status).
    *   CRM API (to fetch client details and project satisfaction).
    *   OpenClaw session history.
*   **Write Access:**
    *   `memory/testimonials/[Client Name]-testimonial-request-{YYYY-MM-DD}.md`: To save drafted testimonial requests.
    *   `playbooks/testimonial-collection-cron.json`: To manage the cron configuration.
    *   Ability to send emails (if integrated for automated sending of requests).
*   **Execution Permissions:**
    *   Ability to process and respond to cron-triggered tasks.
    *   Ability to make API calls to project management tools or CRMs.
    *   Ability to interact with an email sending service (if automated email sending is desired).

This playbook ensures you consistently build a strong portfolio of client testimonials, boosting your social proof and marketing effectiveness.
## 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": "Daily Testimonial Request Check",
      "schedule": "0 9 * * *",
      "task": "Check connected project management tools/CRMs for projects completed within the last 3 days. For each, use the 'Core Testimonial Request Prompt (Post-Project Completion)' from the 'Testimonial Collection Playbook' to draft a testimonial request. Save to memory/testimonials/[Client Name]-testimonial-request-{YYYY-MM-DD}.md.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}