# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Refresh ad copy with new reviews and awards for Microsoft (Bing) Ads.
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/refresh-ad-copy-with-new-reviews-and-awards-for-microsoft-bing-ads
Page: https://www.roadwayai.com/workflows/refresh-ad-copy-with-new-reviews-and-awards-for-microsoft-bing-ads
Library index: https://www.roadwayai.com/automation-library
---
name: refresh-ad-copy-with-new-reviews-and-awards-for-microsoft-bing-ads
description: >-
When new reviews, ratings, awards or customer wins land, works the strongest proof into Microsoft (Bing) ads.
---
# Refresh ad copy with new reviews and awards for Microsoft (Bing) Ads
Source: https://www.roadwayai.com/workflows/refresh-ad-copy-with-new-reviews-and-awards-for-microsoft-bing-ads
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
When new reviews, ratings, awards or customer wins land, works the strongest proof into Microsoft (Bing) ads.
When new reviews, ratings, awards or customer wins land, works the strongest proof into Microsoft (Bing) ads. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
## 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, customer_reviews, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, proof_points, task_history
## Prompt
Refresh ad copy with new reviews and awards for Microsoft (Bing) Ads
Review new items in customer reviews and the proof points since the last run and decide for each:
1. Add to ads now
2. Save for the next copy cycle
3. Not usable
Context and defaults (use these; don't ask):
- Customer reviews: [set this to your own customer reviews]. If it isn't available, say so and skip the rules that depend on it.
- The proof points: [set this to your own proof points]. If not set, use only approved claims.
- 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 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:
- Add to ads now when the proof is specific and verifiable (a rating with review count, a named award, a quantified customer result) and relevant to the campaign's audience. Generic praise is weaker than a number.
- Fit it to Microsoft (Bing): up to 15 headlines and 4 descriptions per RSA, plus sitelinks, callouts, image and multimedia ad assets. Only use quotes and stats that are cleared in the approved claims.
- Not usable: anything unverifiable, outdated (12+ months old), or from a customer who has not approved logo or quote use.
- 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 hurt performance in the last 30 days. 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:
Microsoft (Bing) social proof refresh report
Summary:
The new proof added to which ads, and the proof saved for later.
Add to ads now:
- [proof item] - [reason]
Save for the next copy cycle:
- [proof item] - [reason]
Not usable:
- [proof item] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/refresh-ad-copy-with-new-reviews-and-awards-for-microsoft-bing-ads
When new reviews, ratings, awards or customer wins land, works the strongest proof into Microsoft (Bing) ads. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
