The ISP back-office
AI playbook.

I manage a fiber/cable/wireless ISP. We have an unplanned service outage currently affecting approximately [number] subscribers in [service area or neighborhood]. The outage started at approximately [time]. We believe the cause is [cause or "unknown, we are investigating"]. We do not yet have a confirmed restoration time.

Write a customer notification for:
1. Email (under 150 words)
2. SMS (under 70 characters)
3. Social media post (Facebook/Instagram, under 100 words)

Tone should be factual and apologetic without being defensive. Do not offer account credits or compensation in this message, we will handle those individually. Use plain language. Avoid technical jargon. Sign off with our company name: [company name].

I manage a fiber ISP. We have a planned maintenance window scheduled for [date] from [start time] to [end time]. This will affect [service description]. The purpose is [brief description, e.g., "firmware upgrades to improve network stability"].

Write an advance notice for customers covering:
1. Email notification (under 120 words)
2. SMS reminder (under 60 characters)

Tone should be proactive and reassuring. Emphasize that this is planned maintenance to improve service. Include the outage window and a note that we will send a follow-up when work is complete. Sign off with: [company name], [contact information or website].

I manage a fiber ISP. The outage affecting [service area] that began at [start time] has been resolved as of [restoration time]. The cause was [cause]. Total downtime was approximately [duration].

Write a service restoration notification for:
1. Email (under 100 words)
2. SMS (under 60 characters)

Acknowledge the disruption without over-apologizing. Keep the tone warm and direct. If relevant, mention: [any service improvement or follow-up action]. Sign off with: [company name].

I manage a fiber ISP. Our planned maintenance window that was scheduled to end at [original end time] is running longer than expected. We are now estimating restoration by [new estimated time]. The work is [status description, e.g., "more than 80 percent complete"].

Write an update notification for customers for:
1. Email (under 80 words)
2. SMS (under 60 characters)

Tone should be transparent and direct. Thank customers for their patience. Do not overpromise on the new timeline, use language like "we expect to have service restored by" rather than "service will be restored at." Sign off with: [company name].

I need to create a technical runbook for our ISP operations team. Below are rough notes from our network engineer. Please convert these into a structured, readable runbook formatted for a new field technician.

Format requirements:
- Use clear section headers
- Number all sequential steps
- Use plain language, minimize jargon where possible, define it where necessary
- Include a "Before You Start" section listing prerequisites and tools needed
- Include a "Verify Success" section at the end so the technician knows when the task is complete
- Flag any steps where judgment or escalation may be required

Here are the rough notes:
[Paste notes here]

I am the operations manager at a fiber ISP. I need to create a standard operating procedure (SOP) for the following task: [task name and brief description].

Here is how we currently do this process (rough description):
[Paste description]

Please structure this into a formal SOP with:
1. Purpose (one sentence)
2. Scope (who this SOP applies to)
3. Prerequisites and required access
4. Step-by-step procedure (numbered)
5. Exception handling (what to do if something goes wrong)
6. Escalation path
7. Last updated date: [today's date]

Audience is Tier 1 support staff and new field technicians. Keep language clear and direct.

I am creating an onboarding guide for new hires at our ISP. I have gathered the following materials:
[Paste notes, documents, or descriptions]

Please organize this into a structured 30-day onboarding guide that covers:
- Week 1: Tools, access, orientation
- Week 2: Core processes and workflows
- Week 3: Customer-facing responsibilities
- Week 4: Independent work with check-ins

For each week, provide a daily or weekly structure with clear goals and checkpoints. Include a section on who to contact for each function. Keep the tone welcoming but practical.

Below are notes and summaries from our most common support ticket types over the past quarter. Please turn this into a structured Tier 1 Troubleshooting FAQ.

For each issue type:
1. Symptom description (as the customer would describe it)
2. Most likely cause(s)
3. Step-by-step resolution process
4. Escalation criteria (when to escalate to Tier 2)
5. Customer communication during the process

Here are the ticket summaries:
[Paste ticket notes or summaries]

I am the GM/CFO of a fiber ISP. Please help me draft a structured board report for our quarterly board meeting.

Here is our performance data for the quarter:
- Subscribers: [current] (vs. [prior quarter] and [prior year])
- Net subscriber adds: [number]
- Churn rate: [%]
- ARPU: $[amount]
- Revenue: $[amount] (vs. budget of $[budget])
- EBITDA: $[amount] (vs. budget)
- Key project updates: [list]
- Notable customer or operational events: [list]

Please structure this into a board report with:
1. Executive Summary (3-4 sentences, highlight wins and challenges)
2. Financial Performance (narrative summary of numbers above, flag material variances)
3. Operational Highlights (key milestones and challenges)
4. Strategic Priorities for Next Quarter (3-5 bullets)
5. Items Requiring Board Input (if any)

Tone should be direct and professional. Assume the board is financially sophisticated but not involved in day-to-day operations.

I am preparing a progress report for our BEAD funding grant administrator. Here is our project status:
- Grant award: $[amount]
- Total project scope: [description]
- Progress to date: [locations passed, locations connected, % complete]
- Budget spent to date: $[amount] ([%] of total)
- Milestones completed this period: [list]
- Milestones in progress: [list]
- Issues or delays: [description or "none"]
- Projected completion: [date]

Please draft a formal progress report narrative (approximately 400-600 words) suitable for submission to a state broadband office or NTIA grant administrator. Use formal government report language. Include an executive summary paragraph and a section on challenges and mitigation strategies (use "none identified at this time" if applicable).

I have a board meeting coming up on [date]. Here are the key topics I need to cover:
[List topics]

Here is relevant context for each:
[Notes]

Please draft concise talking points for each topic, 3-5 bullets per topic, written for a verbal presentation rather than a written document. Keep each bullet to one or two sentences. Flag anywhere I should expect questions or where the board may want to discuss.

We are launching fiber internet service in [neighborhood name], a [description] in [city], [state].

Current provider serving most residents: [incumbent name]
Our key differentiators: [list, e.g., "symmetrical upload/download speeds, local ownership, 24/7 local support, no data caps"]
Price point to feature (if applicable): Starting at $[price]/month

Please write:
1. A postcard message (front and back). Front: headline + brief hook. Back: 3-4 key benefits + call to action. Total under 80 words.
2. A door hanger headline and subhead (under 25 words total)
3. A social media caption for Facebook/Nextdoor (under 80 words)

Tone: conversational, community-focused, confidence-building. Avoid corporate language. We are a local provider and want to sound like one.

We are launching fiber internet in [neighborhood] in [city]. We have collected interest signups from residents who asked to be notified when service is available.

Please write a launch announcement email with:
- Subject line (under 50 characters)
- Preview text (under 100 characters)
- Body (under 200 words)

Key messages to include:
- Service is now available at their address
- We are a local provider (not a national cable company)
- [Key differentiator, e.g., "symmetrical speeds, no data caps, local support"]
- Clear call to action: sign up at [URL] or call [phone]

Tone: excited but not hypey. This is an invitation from a neighbor, not an ad.

We are entering a market currently dominated by [incumbent name]. Our advantages over them are: [list differentiators].

Please write three short copy variations (each under 50 words) that draw a contrast without naming the competitor directly. The goal is to help a potential customer feel the difference between a large national provider and a local operator, without being disparaging.

Approach each variation with a different emotional angle:
1. Reliability / frustration with the status quo
2. Local ownership / community investment
3. Speed/value comparison framing

I am the GM of a fiber ISP operating in [region]. A competitor, [company name], has been expanding in our market area.

Please search for and summarize:
1. Any recent news (last 18 months) about [company name]'s expansion plans, network builds, or market entries
2. Any job postings in [state/region] that suggest infrastructure or sales buildout
3. Any permit filings, CPCN applications, or franchise agreements publicly mentioned
4. Their current coverage area vs. any announced expansion plans
5. Their pricing and service tiers if publicly available
6. Any private equity backing, acquisitions, or funding rounds

Summarize findings as a one-page competitive brief. Note the source and approximate date for each significant finding. Flag any areas where public information is limited or unclear.

We are a fiber/broadband ISP evaluating potential acquisition targets in [region or state]. We are looking for operators in the [X,000 to Y,000] subscriber range.

Please help me compile an initial research list of potential targets by:
1. Identifying ISPs operating in [state or region] that appear to be in our target size range based on publicly available information
2. For each, note: approximate service area, technology type (fiber, cable, wireless), any known ownership structure (private, co-op, municipal), any recent news
3. Flagging any that have been mentioned in industry press as acquisition targets or that have recent leadership changes

Present findings as a structured table with a column for each data point and a notes column for context.

I want to understand how [competitor name] is positioning their broadband service against providers like us.

Please review their public website, any press coverage, and any customer reviews you can find to summarize:
1. Their primary marketing message (what they lead with)
2. Their pricing strategy (promotional vs. standard, contract vs. no-contract)
3. Their stated differentiators
4. Common customer complaints in reviews
5. Any gaps in their positioning that a local operator could exploit

Format as a brief competitive analysis with a "Key Takeaways for Competitive Response" section at the end.

I manage customer support at a fiber ISP. Below are our most common ticket types from last quarter. For each one, please create a Tier 1 response template.

Each template should:
- Open with acknowledgment of the issue (empathetic but not over-apologetic)
- Provide clear next steps
- Set expectations for resolution timeline
- Include a placeholder for [agent name] and [ticket number]
- Be under 150 words
- End with a professional close and our company name: [company name]

Here are the ticket types and brief descriptions:
[Paste ticket summaries or issue types]

I manage a fiber ISP. When a customer issue needs to escalate from Tier 1 to Tier 2 or to our NOC, I want a standard communication template the Tier 1 rep sends to the customer to set expectations.

Please write a template that:
- Acknowledges the issue has been escalated
- Explains what will happen next (without making specific promises about timeline)
- Provides contact information if the customer needs to follow up
- Is warm but professional
- Is under 100 words

There are two versions: one for technical escalations (NOC/field dispatch) and one for billing escalations (billing specialist or manager review).

A customer has requested to cancel their internet service. I want to give my support team a response guide for handling these calls and tickets, not a script, but a structured approach.

Please create a response guide that covers:
1. Opening: acknowledge the request and ask for context (suggested language, not a script)
2. Listen and identify: most common cancellation reasons and how to recognize them (moving, price, competitor offer, service quality, no longer needed)
3. Retention response for each category: what to offer or say for each reason type
4. When to escalate to a retention specialist or supervisor
5. If the customer insists: how to complete the cancellation professionally and leave a positive final impression

Our cancellation rate target is [X]%. Our current rate is [Y]%. We do not want to be pushy, we want to be genuinely helpful and retain customers who have a real alternative.

I am creating a 30-day onboarding plan for a new [role: e.g., "field technician / customer support rep / billing coordinator"] at our fiber ISP.

Key areas to cover during onboarding:
[List the main knowledge areas, systems, and processes you want them to learn]

Tools and systems they will use:
[List your key platforms, e.g., BSS/OSS, ticketing system, communication tools]

Who they will work with most closely:
[List roles or names]

Please structure a 30-day onboarding plan that includes:
- Week-by-week focus areas
- Specific learning goals per week
- Suggested shadowing activities
- Checkpoints or milestones for each week
- A simple 30-day self-assessment prompt to review with their manager

Please write a welcome message for new employees at our fiber ISP. This will go in a welcome packet or onboarding email.

About our company: [2-3 sentences about your ISP, your mission, your service area]
Company size: approximately [number] employees
Culture notes: [e.g., "lean team, everyone wears multiple hats, we value direct communication and local pride"]

The welcome message should:
- Make the new hire feel genuinely welcomed
- Set honest expectations about the pace and nature of the work
- Express pride in what the company does for the communities it serves
- Be under 300 words
- Sound like it was written by a real person, not HR

I am writing a grant application for [program name, e.g., "BEAD Phase 2" or "USDA ReConnect"]. I need help drafting the [section name, e.g., "Project Narrative" or "Community Impact" or "Financial Sustainability"] section.

Here is the relevant information about our project:
[Paste your project details, service area data, financial information, and community context]

The section requirements (from the NOFO or application guide):
[Paste the specific requirements or prompts for this section]

Please draft this section in the formal language appropriate for a federal grant application. The draft should be factually grounded in the information I provided above, do not add claims that are not supported by the inputs. Flag anywhere you need more information from me to complete the draft.

Our ISP has received a public comment or challenge to our [BEAD / FCC / state program] filing. The comment claims: [summary of the claim].

Here are our facts in response: [your actual data and evidence]

Please help me draft a formal response to this challenge. The response should:
- Acknowledge the comment respectfully
- Present our factual evidence clearly and sequentially
- Reference the applicable program rules or standards where relevant
- Request the appropriate disposition (denial of challenge, approval of our filing)
- Use formal regulatory language appropriate for submission to [agency name]

Do not include any claims not supported by the facts I have provided.