ISP AI Campaign · Sonar Software

50 AI Prompts Built for Broadband Operators

Ready-to-use templates for back-office teams. Copy any prompt, fill in the variables in brackets, and review every output before sending. Works with ChatGPT, Claude, Gemini, and most general-purpose AI tools.

50 Ready Prompts
9 Categories
Free To Use & Share
01
Category 1 of 9

Outage and Maintenance Communications

Keep subscribers informed at every stage of an outage or maintenance window -- from the first alert to the final resolution notice.

1
Prompt 1

Unplanned Outage: Initial Customer Notification

I manage a [fiber/cable/wireless] ISP. We have an unplanned service outage affecting approximately [number] subscribers in [service area]. Outage started at [time]. Cause: [known cause or "unknown, investigating"]. No confirmed restoration time yet. Write a customer email (under 150 words), SMS (under 70 characters), and Facebook post (under 100 words). Tone: factual, apologetic, not defensive. No credit offers. Sign off: [company name].
2
Prompt 2

Planned Maintenance: Advance Notice

I manage a fiber ISP. Planned maintenance on [date] from [start time] to [end time] will affect [description of affected service/area]. Purpose: [brief description]. Write an advance notice email (under 120 words) and SMS reminder (under 60 characters). Tone: proactive and reassuring. Include follow-up notification promise. Sign off: [company name].
3
Prompt 3

Outage Resolution: Restoration Notice

Outage in [service area] starting at [start time] is now resolved as of [restoration time]. Cause was [cause]. Total downtime: [duration]. Write a restoration notification email (under 100 words) and SMS (under 60 characters). Acknowledge disruption without over-apologizing. Warm, direct tone. Sign off: [company name].
4
Prompt 4

Maintenance Running Long: Update

Our planned maintenance window scheduled to end at [original end time] is running longer than expected. New estimated restoration time: [new time]. Work is [status, e.g., "80% complete"]. Write an update email (under 80 words) and SMS (under 60 characters). Transparent and direct. Thank customers for patience. Use "we expect" language, not "service will be restored at." Sign off: [company name].
5
Prompt 5

Major Outage: Multi-Update Sequence

We have a major outage affecting [number] subscribers in [area]. It has been ongoing for [duration]. Write three update messages (each under 80 words) for email/social updates to be sent at [time 1], [time 2], and [time 3] as we work through the issue. Each should feel like a new update, not a repeat. Show forward progress even if issue is unresolved. Tone: steady and transparent.
6
Prompt 6

Post-Outage Apology / Make-Good

We had an extended outage [duration] in [service area] last [timeframe] that affected [number] customers. We want to send a post-incident message that goes beyond the restoration notice -- something that rebuilds trust and acknowledges the impact honestly. We plan to offer [credit/no credit]. Write a personal-feeling message from our GM ([name]) that is genuine, not corporate. Under 200 words.
7
Prompt 7

Emergency Network Alert (Severe Weather)

We are issuing a proactive customer alert because [severe weather event, e.g., "a winter storm"] is forecast to hit [service area] on [date]. This may cause service disruptions. We want customers to know what to expect and how to contact us. Write a proactive alert email (under 120 words) and social post (under 80 words). Tone: helpful and preparatory, not alarmist.
8
Prompt 8

Maintenance Schedule: Quarterly Summary

I need to notify customers that we have [number] scheduled maintenance windows coming up over the next [timeframe]. Dates and times: [list]. Each will affect a different area of our network. Write a general maintenance schedule notice (under 200 words) that covers all windows and directs customers to [URL or contact] to find out if their address is affected. Professional tone.
02
Category 2 of 9

Documentation and Runbooks

Turn rough notes, tribal knowledge, and support tickets into structured runbooks, SOPs, and knowledge base articles your team can actually use.

9
Prompt 9

Rough Notes to Structured Runbook

Convert the following rough notes into a structured runbook for a new field technician at our ISP. Format: clear section headers, numbered steps, plain language. Include a "Before You Start" section (prerequisites and tools) and a "Verify Success" section. Flag any steps requiring escalation or judgment. Here are the notes: [paste notes]
10
Prompt 10

SOP from Process Description

Create a standard operating procedure (SOP) for: [task name]. Here is how we currently do it: [description]. Format: 1) Purpose, 2) Scope, 3) Prerequisites, 4) Procedure (numbered steps), 5) Exception handling, 6) Escalation path, 7) Last updated: [date]. Audience: Tier 1 support and new field techs. Clear and direct language.
11
Prompt 11

Troubleshooting FAQ from Ticket Notes

Turn the following support ticket summaries into a Tier 1 Troubleshooting FAQ. For each issue type: 1) Symptom (as customer would describe it), 2) Likely cause(s), 3) Step-by-step resolution, 4) Escalation criteria, 5) Customer communication guidance. Here are the ticket summaries: [paste summaries]
12
Prompt 12

Policy Documentation

I need to write a formal policy document for: [policy topic, e.g., "acceptable use" or "payment and late fees" or "service disconnection"]. Key points to include: [list]. Format as a professional policy document with numbered sections. Tone: clear and professional. Audience: customers and staff. Company name: [name].
13
Prompt 13

Field Guide: Equipment Reference Sheet

Create a one-page quick reference field guide for [equipment type or task]. Key information to include: [list specifications, steps, or reference data]. Format as a condensed, easy-to-scan reference card. Use bullet points and short sentences. Designed to be used in the field, not at a desk.
14
Prompt 14

Knowledge Base Article from Support Notes

Convert the following support notes into a customer-facing knowledge base article. Audience: non-technical subscriber. Topic: [topic]. Notes: [paste]. Format: brief intro, step-by-step instructions (numbered, plain language), one FAQ entry at the end. Under 300 words. Avoid jargon.
15
Prompt 15

Update Existing Documentation

Here is an existing runbook/SOP/guide: [paste document]. The following things have changed: [list changes]. Please update the document to reflect these changes while keeping the structure and formatting consistent. Highlight (with [UPDATED] tags) which sections you modified.
03
Category 3 of 9

Board and Executive Reporting

Draft structured board reports, executive summaries, and investor updates from your raw data and notes -- in a fraction of the time.

16
Prompt 16

Full Board Report from Metrics

Draft a structured board report for our quarterly meeting. Performance data: subscribers [current] vs. [prior quarter], net adds [number], churn [%], ARPU $[amount], revenue $[amount] vs. budget $[amount], EBITDA $[amount]. Key project updates: [list]. Notable events: [list]. Structure: 1) Executive Summary, 2) Financial Performance, 3) Operational Highlights, 4) Strategic Priorities, 5) Items Requiring Board Input. Direct, professional tone. Board is financially sophisticated.
17
Prompt 17

Executive Summary for Data-Heavy Report

Here is a data-heavy operational report: [paste report or data]. Please write a 3-4 sentence executive summary that captures the most important takeaways for a senior executive who will not read the full report. Lead with performance vs. goals. Flag any significant risks or decisions required.
18
Prompt 18

Board Meeting Talking Points

I have a board meeting on [date]. Key topics: [list with brief context for each]. Draft concise talking points: 3-5 bullets per topic for verbal presentation (not written document). One to two sentences per bullet. Flag where board discussion or questions are likely.
19
Prompt 19

Investor Update / Shareholder Letter

Write an investor/shareholder update letter for [period]. Key highlights: [list]. Challenges: [list]. Looking ahead: [priorities]. Tone: transparent and confident, not promotional. Appropriate for owners, board members, or equity stakeholders who follow the business closely. Under 400 words. From: [GM or CEO name], [company name].
20
Prompt 20

BEAD Progress Report Narrative

Draft a BEAD progress report narrative for submission to [state broadband office or NTIA]. Grant: $[amount]. Scope: [locations in area]. Progress: [locations passed], [locations connected], [% complete]. Budget spent: $[amount] ([%] of total). Milestones completed: [list]. In progress: [list]. Issues/delays: [description or "none"]. Projected completion: [date]. Format: 400-600 words, formal government report language. Include executive summary paragraph and challenges/mitigation section.
21
Prompt 21

Annual Report Summary

Help me write the narrative sections of our annual report. Key data from the year: [list major metrics and milestones]. This was a year defined by: [brief characterization]. Format: 1) Year in Review (2-3 paragraphs), 2) By the Numbers (bullets summarizing key metrics in plain language), 3) What We Built (operational/infrastructure milestones), 4) Looking Ahead (2-3 strategic priorities for next year). Tone: proud but grounded. From our company.
04
Category 4 of 9

Hyperlocal Marketing Copy

Launch new markets, run referral programs, and reach move-in audiences with community-focused copy that feels local -- not corporate.

22
Prompt 22

Subdivision Launch: Postcard and Door Hanger

We are launching fiber in [neighborhood], [city]. Current incumbent: [name]. Our differentiators: [list]. Starting price: $[amount]/month. Write: 1) Postcard (front headline + hook, back 3-4 benefits + CTA, under 80 words total), 2) Door hanger headline and subhead (under 25 words). Tone: conversational, community-focused, local pride. Not corporate.
23
Prompt 23

Launch Announcement Email

Fiber service is now available in [neighborhood], [city]. Write a launch announcement email to interested residents. Subject line (under 50 characters), preview text (under 100 characters), body (under 200 words). Key messages: local provider, [differentiators], sign up at [URL] or call [phone]. Tone: friendly invitation, not an ad.
24
Prompt 24

Social Ad Copy Variations

Write 3 variations of a Facebook/Instagram ad for our fiber launch in [city/neighborhood]. Each variation under 80 words. Target: homeowners currently using [incumbent]. Our advantages: [list]. Variation 1: lead with reliability/frustration, Variation 2: lead with local ownership, Variation 3: lead with speed/value. Each needs a headline (under 10 words) and body copy.
25
Prompt 25

Nextdoor Post

Write a Nextdoor community post announcing that fiber internet is now available in [neighborhood]. Tone: genuine neighbor, not ad copy. Mention we are a local company (not [national incumbent]). Include specific street boundaries or landmarks if helpful: [details]. CTA: visit [URL] or call [phone]. Under 120 words.
26
Prompt 26

Event / Trade Show Flyer

Write copy for a trade show booth / community event flyer for our ISP. Event: [name, city, date]. Our elevator pitch: [2-3 sentences about your company]. Special offer if applicable: [offer or "none"]. Format: headline (punchy, under 10 words), 3-4 benefit bullets, one clear CTA. Tone: direct and confident.
27
Prompt 27

Referral Program Announcement

We are launching a referral program. Reward: [reward for referrer] and [reward for new customer, if any]. Write an announcement for: 1) Email to current customers (under 150 words), 2) SMS (under 70 characters), 3) Social post (under 80 words). Tone: warm and enthusiastic. Make it easy to understand: "Tell a neighbor, get [reward]."
28
Prompt 28

Conquest Campaign: Move-In Audience

We want to reach new residents who recently moved into our service area. They are currently without a provider or setting up new service. Write three short ad copy variations (each under 60 words) for digital targeting. Messages should feel welcoming to new residents, emphasize local ownership, and create urgency to set up service before they default to the incumbent. CTA: [URL or phone].
05
Category 5 of 9

Competitive Intelligence and Research

Build overbuild threat assessments, M&A research lists, and competitive positioning briefs with structured prompts designed for ISP market dynamics.

29
Prompt 29

Overbuild Threat Assessment Brief

Help me research [competitor name] for overbuild threat analysis in [region]. Search and summarize: 1) Recent expansion news (last 18 months), 2) Job postings suggesting infrastructure buildout in [state], 3) Any franchise/permit filings mentioned publicly, 4) Current coverage vs. announced expansion, 5) Pricing if available, 6) PE/investor backing. Present as a one-page competitive brief. Note source and date for each significant finding.
30
Prompt 30

Competitive Positioning Analysis

Analyze [competitor name]'s public positioning. Review their website, press coverage, and customer reviews. Summarize: 1) Primary marketing message, 2) Pricing strategy, 3) Stated differentiators, 4) Common customer complaints, 5) Gaps a local operator could exploit. End with a "Key Takeaways for Competitive Response" section.
31
Prompt 31

M&A Target Research List

I am evaluating acquisition targets in [region/state]. Target profile: ISPs in [X,000-Y,000] subscriber range. Please help compile a research list. For each potential target: approximate service area, technology type, ownership structure (private/co-op/municipal), recent news, and any signals of acquisition readiness. Present as a structured table.
32
Prompt 32

Due Diligence Research Summary

We are in early-stage M&A exploration of [target company]. Help me summarize publicly available information: 1) Company overview and service area, 2) Technology infrastructure (fiber/cable/wireless), 3) Approximate customer count and geography, 4) Recent news, leadership changes, or financial signals, 5) Regulatory filings or grant awards. Flag information gaps. This is preliminary research only.
33
Prompt 33

BEAD Competitive Landscape

We are competing for BEAD funding in [state]. Help me understand the competitive landscape for this funding round: 1) Which providers are likely to apply based on their RDOF/EBB participation and service area filings, 2) Any publicly available state broadband office guidance on priority areas, 3) What factors typically differentiate winning BEAD applications. Summarize as a brief strategic overview.
06
Category 6 of 9

Customer Support and Retention

Build response template libraries, churn save guides, and billing dispute workflows that help your team handle tough conversations with consistency.

34
Prompt 34

Response Template Library

Build a Tier 1 customer response template for each of the following issue types: [list 5-8 issue types]. Each template: open with empathetic acknowledgment, clear next steps, timeline expectations, placeholder for [agent name] and [ticket number], under 150 words, professional close. Company name: [name].
35
Prompt 35

Churn Save Response Guide

Create a response guide for handling customer cancellation requests. Cover: 1) Opening approach (acknowledge, seek context), 2) Most common cancellation reasons (moving, price, competitor, quality, no longer needed) and retention response for each, 3) When to escalate to a retention specialist, 4) How to complete cancellation professionally if customer insists. Not a script -- a structured guide. Our goal is genuine helpfulness, not pressure.
36
Prompt 36

Billing Dispute Response

A customer is disputing their bill for [reason]. The facts are: [your explanation]. Write a customer response that: explains the charge clearly in plain language, acknowledges any confusion even if the charge is correct, offers a specific path to resolution, and is professional but human. Under 150 words.
37
Prompt 37

Service Quality Complaint Response

A customer has complained about [service issue, e.g., "repeated intermittent outages over the past two weeks"]. Our response: [what we are doing to investigate/fix]. Write a response that: takes the issue seriously, explains what we are doing, sets realistic expectations, and does not over-promise. Tone: accountable and direct, not defensive. Under 150 words.
38
Prompt 38

Win-Back Campaign Email

A customer cancelled [timeframe] ago. Reason: [reason if known]. We want to reach out and invite them back. We now offer: [any improvements or changes]. Write a win-back email (under 150 words) that acknowledges they left, mentions what has changed, and makes a specific offer: [offer]. Tone: genuine and low-pressure. Not desperate.
07
Category 7 of 9

Internal Communications and HR

Write company announcements, job postings, performance review templates, and meeting agendas -- in plain language that your team will actually read.

39
Prompt 39

Company-Wide Announcement

Write a company-wide announcement for: [topic, e.g., "new HR policy / new hire / system change / reorg"]. Key information: [list]. Tone: direct and human, not corporate. Under 200 words. From: [name, title]. Include any action items or questions employees should direct to: [contact].
40
Prompt 40

Job Posting

Write a job posting for a [job title] at our fiber ISP. Key responsibilities: [list]. Required skills: [list]. Nice-to-have: [list]. Location: [city/state], [remote/hybrid/in-person]. About our company: [2-3 sentences]. Tone: welcoming and direct. Avoid buzzwords. We want candidates who understand what the role actually involves. Under 350 words.
41
Prompt 41

Performance Review Template

Create a performance review template for [role] at a fiber ISP. Include: 1) Performance against key responsibilities, 2) Communication and teamwork, 3) Problem-solving and initiative, 4) Development goals for next period, 5) Manager overall assessment. Format as a structured form with rating criteria and space for comments. Professional tone.
42
Prompt 42

Team Meeting Agenda

Create an agenda for a [type, e.g., "weekly ops meeting / quarterly all-hands / incident debrief"] at our ISP. Duration: [time]. Topics to cover: [list]. Format: time-boxed agenda with owner for each item and desired outcome. Include time for open questions. Professional but efficient.
08
Category 8 of 9

Grant and Regulatory Documentation

Draft BEAD narratives, respond to coverage challenges, and write correspondence to state broadband offices with structured prompts built for regulatory context.

43
Prompt 43

Grant Narrative Section

Draft the [section name] section of our [program name] grant application. Project details: [list]. Section requirements from NOFO: [paste requirements]. Draft in formal federal grant language. Ground all claims in the data I provided -- do not add unsupported claims. Flag where you need more information from me.
44
Prompt 44

Public Comment Response

Draft a formal response to a challenge to our [BEAD/FCC/state program] filing. The challenge claims: [summary]. Our facts in response: [your evidence]. Response should: acknowledge respectfully, present evidence clearly and sequentially, reference applicable rules, request appropriate disposition. Formal regulatory language for submission to [agency].
45
Prompt 45

State Broadband Office Correspondence

Help me draft a formal letter to [state broadband office] regarding: [topic, e.g., "correction to our broadband map submission" / "request for clarification on BEAD application requirements" / "response to coverage challenge"]. Key points to make: [list]. Tone: professional and cooperative. Format as a formal business letter. From: [name, title, company].
46
Prompt 46

FCC Form Narrative

Help me draft the narrative section for [FCC form or filing, e.g., "Form 477 narrative" or "RDOF challenge response"]. My service area details: [describe]. Key facts to include: [list]. Regulatory context: [brief description]. Use plain, factual language appropriate for FCC submission. Flag any claims that need supporting documentation.
09
Category 9 of 9

Strategic Planning and Brainstorming

Structure SWOT analyses, evaluate pricing strategy options, and outline go-to-market plans with prompts that bring analytical rigor to operator strategy sessions.

47
Prompt 47

SWOT Analysis Framework

Help me structure a SWOT analysis for our fiber ISP. Context: [describe your company, market, and current situation]. For each quadrant (Strengths, Weaknesses, Opportunities, Threats), suggest 4-6 items based on what I have described. I will review and edit -- this is a starting framework, not a final analysis. Format as a clean 2x2 structure.
48
Prompt 48

Pricing Strategy Options

I am evaluating pricing strategy changes for our ISP. Current structure: [describe]. Market context: [competitor pricing, market pressures]. Goals: [e.g., "increase ARPU, reduce churn, attract higher-value customers"]. Present 3 pricing strategy options with pros and cons for each. Not a recommendation -- a structured options analysis I can evaluate with my team.
49
Prompt 49

Go-to-Market Plan Outline

Help me outline a go-to-market plan for [initiative, e.g., "fiber launch in a new market" or "business services expansion"]. Key inputs: target market [description], competitive landscape [brief], our strengths [list], timeline [target]. Create a structured plan outline covering: 1) Market entry strategy, 2) Customer acquisition approach, 3) Pricing and packaging, 4) Channel strategy, 5) Launch milestones. This is an outline -- not a final plan.
50
Prompt 50

Post-Mortem Analysis

Help me structure a post-mortem analysis for: [incident or project, e.g., "extended outage on [date]" or "failed market entry in [area]"]. Format: 1) What happened (timeline), 2) Root cause analysis, 3) What we did well, 4) What we would do differently, 5) Action items with owners and deadlines. Objective tone. The goal is learning, not blame.
Getting the Most Out of AI

Tips for Best Results

These prompts get you to 80 percent of a great draft quickly. Here is how to close the gap.

Add context to every prompt

"I manage a 25,000-subscriber fiber ISP in rural Nebraska" produces better output than "I manage an ISP." The more specific your context, the more useful the draft.

Specify the audience

"Write for a non-technical subscriber" vs. "write for our board" produces very different documents. Always tell the AI who will read the output.

Use as first drafts

Review every output before using it externally. AI gets you to 80 percent quickly. The remaining 20 percent comes from your knowledge of your company and customers.

Verify every number

AI uses the numbers you give it -- but double-check that they are correctly represented in the output before sending to customers, boards, or regulators.

Iterate the prompt, not the output

If results are off, adjust the prompt rather than manually editing the output repeatedly. A better prompt produces a better draft from the start.

Save your best prompts

Build a team prompt library with your most useful customized versions. Share them across your support, ops, and marketing teams to save time on repeat tasks.

Powered by Sonar Software

See AI in Your Back Office

Sonar is the unified OSS/BSS platform that helps broadband operators simplify operations, improve billing accuracy, and grow without adding complexity. See how it works.

Explore Sonar