# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Suppress upsell ads for accounts with open support issues.
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/suppress-upsell-ads-for-accounts-with-open-support-issues
Page: https://www.roadwayai.com/workflows/suppress-upsell-ads-for-accounts-with-open-support-issues
Library index: https://www.roadwayai.com/automation-library
---
name: suppress-upsell-ads-for-accounts-with-open-support-issues
description: >-
Reads support and churn-risk signals by segment and pulls upsell and renewal ads from customers who are having a bad time, then restores them when it clears.
---
# Suppress upsell ads for accounts with open support issues
Source: https://www.roadwayai.com/workflows/suppress-upsell-ads-for-accounts-with-open-support-issues
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
Reads support and churn-risk signals by segment and pulls upsell and renewal ads from customers who are having a bad time, then restores them when it clears.
Reads support and churn-risk signals by segment and pulls upsell and renewal ads from customers who are having a bad time, then restores them when it clears. When a customer segment has a spike in tickets, an open outage or a churn-risk flag, it will exclude them from upsell and expansion ads until it is fixed. It keeps watching for this trigger, so you can respond 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
auto_approve, customer_audiences, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, support_signals, task_history
## Prompt
Suppress upsell ads for accounts with open support issues
Read [set this to your own support signals] with [set this to your own customer audiences], and decide the treatment for each customer segment:
1. Exclude from upsell ads
2. Switch to support messaging
3. Restore ads
4. No action
Context and defaults (use these; don't ask):
- Support ticket and churn-risk signals by customer segment: [set this to your own support signals]. If it isn't available, say so and skip the rules that depend on it. Source: an Intercom or other support-desk MCP connected in Roadway. Roadway has no native support-conversation data.
- Customer and open-opportunity audiences already on each platform (synced by the CRM or CDP's native ad-audience sync), applied as exclusions or seeds: [set this to your own customer audiences]. If it isn't available, say so and skip the rules that depend on it.
- 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:
- Use segment-level data only (plan, size, region, product), through the native audience sync. Do not use or ask for individual contacts.
- Exclude from upsell ads when a segment has an open P1 incident, a 2x ticket spike over 7 days, or a churn-risk score above your threshold.
- Switch to support messaging (status updates, fix announcements) only when the support team agrees, and keep it plain and apologetic.
- Restore ads 7 days after the issue clears, and check with [set this to your own task history] that exclusions are not left on.
- Report the spend saved and any renewal or expansion effect compared with similar unaffected segments.
- 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:
Upsell suppression report
Summary:
The segments excluded, the reasons, the spend saved, and restored segments.
Exclude from upsell ads:
- [segment] - [reason]
Switch to support messaging:
- [segment] - [reason]
Restore ads:
- [segment] - [reason]
No action:
- [segment] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/suppress-upsell-ads-for-accounts-with-open-support-issues
Suppress upsell ads for accounts with open support issues
Suppress upsell ads for accounts with open support issues
Reads support and churn-risk signals by segment and pulls upsell and renewal ads from customers who are having a bad time, then restores them when it clears.
Reads support and churn-risk signals by segment and pulls upsell and renewal ads from customers who are having a bad time, then restores them when it clears. When a customer segment has a spike in tickets, an open outage or a churn-risk flag, it will exclude them from upsell and expansion ads until it is fixed. It keeps watching for this trigger, so you can respond 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.
