Explain a prorated bill or plan change clearly
Turn confusing mid-cycle invoice numbers into a calm, line-by-line explanation a customer can read in two minutes. Perfect for diffuse billing tickets.
You getDirect Greeting, summary in 1-2 sentences and line-by-Line Breakdown
Prompt
Act as a senior customer support specialist. Write a clear, empathetic customer reply explaining the prorated charge or mid-cycle plan adjustment from the raw details provided below.
Rules:
- Break down the math into simple plain English without accounting jargon.
- Show the exact dates of the billing cycle, the credit for unused time, and the charge for the new tier or seats.
- Keep the tone calm, polite, and reassuring without over-apologizing.
- State clearly what the customer's next regular invoice amount will be.
Output format:
- Direct Greeting
- Summary in 1-2 sentences
- Line-by-Line Breakdown (bullet points with dates and dollar amounts)
- What to Expect on Next Bill
- Closing Line
The customer ticket and invoice details are below:Example output
Paste the customer inquiry along with the invoice line items into ChatGPT, Claude, or Gemini. Ask the model to recalculate the daily rate if your billing software uses a specific 30-day or calendar-day rule.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Analyze Customer Cancellation Reasons to Surface Preventable Churn Fixes
Get a structured churn analysis table separating controllable from uncontrollable cancellations, with exact counts, root causes, and one retention fix per category.
Analyze customer sentiment beneath translated tickets
Reveal hidden frustration, urgency, and underlying demands that machine translation tools flatten or misinterpret in foreign-language tickets.
Explain browser console logs to everyday users
Get step-by-step, non-intimidating email templates that guide non-technical customers through capturing console logs and screen recordings.
Turn vague feature requests into actionable workflow feedback
Extract underlying user problems, manual workarounds, and workflow impact from brief customer feature requests.
Turn customer call notes into action items
Convert raw customer support or onboarding call notes into a structured follow-up summary with clear owners, deadlines, and next steps.
Turn messy account metrics into a QBR summary
Convert unorganized support ticket history and platform telemetry into an executive-ready quarterly account briefing with clear action items.
- Turn technical release notes into plain customer updates
- Write a post-purchase email that cuts support tickets
- Write an honest shipping delay update
- Turn a Customer Bug Report into an Engineering Ticket
- Draft a Feature Deprecation Notice for Your Customers
- Decline an Off-Roadmap Feature Request with Workarounds