OpenAI API playbooks
The OpenAI API is the language model step in these playbooks: scoring inbound leads against a written ICP, classifying support tickets for churn risk, extracting fields from receipts, drafting short notes, and categorizing lost-deal reasons. The prompts are written into each playbook so you can adapt them.
- ResearchAdvanced
Analyze Lost Deals with Claygent and OpenAI
Lost deal reasons in CRM are vague ("pricing", "timing"). Reps rarely document specifics.
ClayHubSpotOpenAI API+1Estimate: 5 hrs/week - InboundIntermediate
Qualify Inbound Leads with AI Before Routing
SDRs lose a meaningful share of their day to unqualified inbound leads (students, competitors, wrong market).
ClayOpenAI APIHubSpotEstimate: 9 hrs/week - Finance/FP&AIntermediate
Parse Receipt Emails and Auto-Create Expense Reports
Employees manually forward receipts to finance. Someone re-keys them into expense software.
ZapierGmailGoogle Sheets+1Estimate: 5 hrs/week - ContentIntermediate
Generate Blog Post Ideas from Customer Questions
Support tickets are full of recurring customer questions that would make great blog content, but no one mines them.
ZendeskOpenAI APIGoogle Sheets+1Estimate: 3 hrs/week - RevOpsAdvanced
Score Churn Risk from Support Tickets with an LLM
CS and RevOps find churn late because ticket themes stay buried in Zendesk/Intercom while CRM health scores ignore qualitative signal.
Zendesk or Intercomn8n or MakeClaude or OpenAI API+2Estimate: 5 hrs/week - InboundIntermediate
Automate Inbound Lead Routing with Enrichment and Fit Scoring
Inbound leads wait in a shared queue or get assigned round-robin regardless of fit, so the best leads reach a rep late and poor-fit leads take up AE time.
ClayHubSpot or SalesforceApollo+2Estimate: 4 hrs/week - InboundIntermediate
Route Product-Qualified Leads from Sign-Ups to Sales
Self-serve sign-ups pile up in the product, and sales either ignores them or chases every free account, so the few sign-ups from ICP companies who are actually using the product wait for a rep.
ClaySegment, Amplitude, or MixpanelHubSpot or Salesforce+2Estimate: 4 hrs/week - InboundIntermediate
Rebook Demo No-Shows with a Short Personalized Sequence
Booked demos that end as no-shows usually get one "sorry we missed you" email or nothing at all, so meetings the team already worked to create quietly drop out of the pipeline.
Calendly or Chili PiperHubSpot or SalesforceClay+2Estimate: 2 hrs/week - InboundAdvanced
Answer Demo Requests Within Minutes, Even After Hours
Demo requests that come in at night or over the weekend wait until a rep logs on, so the buyer who was ready to talk on Friday evening gets a first reply on Monday, often after they have booked with someone else.
HubSpot or SalesforceClayOpenAI API+3Estimate: 3 hrs/week - OutboundAdvanced
Build Prospect Lists from Plain-English Requests in Slack
Reps and marketers wait days for RevOps to build a prospect list, or pull their own from Apollo with inconsistent filters, no CRM dedupe, and no check on how many credits the pull will burn.
SlackZapier or MakeOpenAI API+4Estimate: 4 hrs/week
Need help implementing a playbook?
Our team builds custom Clay workflows and AI automations for revenue teams.
Get it built for you