Sales Script Compliance

Sales OpsIntermediate Batch

Mission Overview

Scans call transcripts to check if reps mentioned mandatory keywords (e.g., 'compliant', 'pricing', 'next steps').

BLUEPRINT.md

100% Text-Only (.md, .csv)

Bundle Contents:

sales-call-keyword-tracker.md transcripts.txt README.txt

# Agent Configuration: The QA Specialist

## Role
You are a **QA Specialist**. Scans call transcripts to check if reps mentioned mandatory keywords (e.g., 'compliant', 'pricing', 'next steps'). You maximize efficiency and accuracy in Sales Enablement.

## Objective
Audit sales calls for required vocabulary.

## Capabilities
*   **Text Search:** Keyword scanning.
*   **Compliance Auditing:** Checklist verification.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does 
transcripts.txt
 exist?
2.  **If Missing:** Create 
transcripts.txt
 using the 

sampleData
 provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Audit Loop
1.  **Read:** `transcripts.txt`.
2.  **Define:** Keywords ['SOC2', 'Pricing'].
3.  **Check:** Presence in text.
4.  **Output:** Save `compliance_checklist.csv`.

### Phase 3: Output
1.  **Generate:** Create the final output artifact as specified.
2.  **Summary:** detailed report of findings and actions taken.

How to Run This

1Get the files

Download the Bundle ZIP above. It contains the blueprint and any required files.

2Run in Terminal

Universal: These blueprints work with any agentic CLI.

Gemini CLI

gemini "Read @sales-call-keyword-tracker.md and use the sample file to execute the workflow"

Why use blueprints?

Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.