# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Test ad hooks taken from how customers praise you on social.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/test-ad-hooks-taken-from-how-customers-praise-you-on-social
Page: https://www.roadwayai.com/workflows/test-ad-hooks-taken-from-how-customers-praise-you-on-social
Library index: https://www.roadwayai.com/automation-library
---
name: test-ad-hooks-taken-from-how-customers-praise-you-on-social
description: >-
Pulls the phrases customers use when they recommend you on X, Reddit and LinkedIn, found with web search, and tests the strongest as hooks in paid social ads, checked against your approved claims.
---
# Test ad hooks taken from how customers praise you on social
Source: https://www.roadwayai.com/workflows/test-ad-hooks-taken-from-how-customers-praise-you-on-social
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
Pulls the phrases customers use when they recommend you on X, Reddit and LinkedIn, found with web search, and tests the strongest as hooks in paid social ads, checked against your approved claims.
Each run, it uses web search, or a social listening MCP if you have one, to read what customers say when they recommend you on X, Reddit and LinkedIn. When several people repeat the same phrase, it writes hook variants from it, checks them against your approved claims, and tests them in paid social. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
approved_claims, auto_approve, brand_voice, creative_library, experiment_budget_pct, funnel_metrics, goal_metric, linkedin_mentions, max_change_pct, min_sample_size, monthly_budget_cap, social_mentions, task_history
## Prompt
Test ad hooks taken from how customers praise you on social
Read [set this to your own social mentions] and [set this to your own linkedin mentions] for the phrases customers use when they recommend us on X, Reddit and LinkedIn, and decide for each repeated praise theme:
1. Test as a hook
2. Watch for more mentions
3. Skip
Context and defaults (use these; don't ask):
- Social mentions: [set this to your own social mentions]. If it isn't available, say so and skip the rules that depend on it. Source: public posts the agent can read with the web search tool, or a connected social listening MCP. Roadway has no native Meta, X or Reddit mention feed, so web search can miss posts; say how many you could read.
- LinkedIn mentions: [set this to your own linkedin mentions]. If it isn't available, say so and skip the rules that depend on it. Source: public LinkedIn posts the agent can read with the web search tool. Roadway has no native LinkedIn mention feed.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The brand voice: [set this to your own brand voice]. If not set, match the tone visible on the coworker's landing pages and ads, and mark anything beyond that Unverified.
- The creative library: [set this to your own creative library]. If not set, use the ad platform's asset performance and Task History.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- A praise theme qualifies when several different people used the same phrase or idea since the last run. Count people, not posts.
- Test as a hook: write hook variants from those phrases, checked against [set this to your own approved claims] so no ad makes a claim you haven't approved, and run them as a copy iteration test against the current best hook at [set this to your own experiment budget percent].
- Don't quote anyone by name or handle, and don't reuse their posts. Use the idea in your own words.
- Watch for more mentions when only one or two people said it.
- Judge on [set this to your own funnel metrics], not engagement, with at least [set this to your own min sample size] goal events per variant.
- Turning buyer problem language into search keywords belongs to the Reddit language workflow. This one turns praise into social hooks.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that already hurt performance. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Customer praise hook report
Summary:
The praise themes found, how many posts web search could read, and the hooks tested.
Test as a hook:
- [praise theme] - [reason]
Watch for more mentions:
- [praise theme] - [reason]
Skip:
- [praise theme] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/test-ad-hooks-taken-from-how-customers-praise-you-on-social
Test ad hooks taken from how customers praise you on social
Test ad hooks taken from how customers praise you on social
Pulls the phrases customers use when they recommend you on X, Reddit and LinkedIn, found with web search, and tests the strongest as hooks in paid social ads, checked against your approved claims.
Each run, it uses web search, or a social listening MCP if you have one, to read what customers say when they recommend you on X, Reddit and LinkedIn. When several people repeat the same phrase, it writes hook variants from it, checks them against your approved claims, and tests them in paid social. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.