AI prompts for self-storage customer service representatives

I work in self-storage facility customer service. Help me create one customer issue summary that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Create a clear customer issue summary the billing team can act on without calling the customer back.

Source material:
"Hey it's Dana again, this is the third time reaching out about order #48211 -- when I called Tuesday your rep Marcus told me the replacement charger would ship free since the first one arrived broken, but I just got billed $34.99 for it AND a $12 restocking fee I never agreed to. I have the return tracking number if you need it: 1Z-9F8-2201. I need this sorted before my card statement closes on the 24th or I'm disputing the whole thing with my bank. Can someone actually call me back today?"

Return only the finished work:
1. customer issue summary
2. known facts
3. missing info

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one reusable answer to the refund-timing question that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Write one clear, reusable answer to the refund-timing question above, plus a short note on what to double check before sending it to a customer.

Source material:
"Third time today someone's asked about this -- can you get me a ready-to-go answer for 'How long do refunds take?' I keep giving slightly different answers and it's making us look disorganized. Here's what's actually true: once a refund is approved, it hits the customer's account in 5 to 7 business days. Approval itself can take anywhere from same-day to 3 business days depending on the item, and we send an automatic email the second it goes out. I don't want anything in there that promises a specific date -- I got burned promising Naomi in billing a refund would land by Friday, and it didn't clear until the following Tuesday."

Return only the finished work:
1. reusable answer to the refund-timing question
2. short note on what to verify before sending it
3. guidance on when to escalate instead

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one customer response draft that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Draft a customer response for a refund status question you cannot fully confirm yet.

Source material:
"Ticket #51906 came in overnight -- Renata Solis is asking about her refund for order #A-77209, submitted August 12. She says she called Tuesday and was told 5-7 business days, but it has been over a week now and she wants to know exactly when the money hits her account. I checked and the refund request shows as submitted but I can't see whether finance actually approved it yet -- that field's blank on our end. She's messaged twice today already and says she'll rebook with a competitor if she doesn't hear back by end of day. Can you get her a reply?"

Return only the finished work:
1. customer response draft
2. facts to verify
3. internal note

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one complaint action plan with response draft that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Create a complaint action plan and a response draft the customer can act on today.

Source material:
"This is the third time I've called about order #63042 and I'm getting a different story every time. On Monday Wanda told me the replacement router shipped Tuesday. Today Tyrell told me it hasn't shipped at all because the address needs verification -- nobody told me that. My home office has been down for eight days. I want someone to call me back today, not another email, and I want to know exactly what's happening and when it'll actually show up. My number's on the account, use it." -- voicemail from Dara Okonkwo, left at 9:14 this morning on the support line.

Return only the finished work:
1. complaint action plan with response draft
2. named owner for the callback
3. a follow-up timeline with a check-in date

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one sales/support handoff brief that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Turn a rep's raw call notes into a sales handoff brief the next person can act on without re-running discovery.

Source material:
"Just wrapped the discovery call with Priya Chandrasekaran, ops director at Bellwether Logistics -- she's ready to move but her CFO Doug Feldman won't sign off without pricing broken out by driver headcount, and he wants it by Thursday the 27th before their board meeting. Twice she asked about our cancellation terms because their last vendor, Farlow Systems, auto-renewed their contract on them and it took six weeks of calls to get out of it. She's also nervous about onboarding -- she's moving 40 drivers over in October, right before peak season, and doesn't want a repeat of the two-week blackout Farlow put them through last time. She's talking to two other vendors too, so whoever picks up the follow-up needs to move on this fast. Put together something the next person can run with instead of starting the discovery over."

Return only the finished work:
1. sales/support handoff brief
2. needs
3. objections

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one response QA checklist that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Turn this weak reply into a reusable QA checklist you can run any customer response through before it goes out.

Source material:
"Hi Julian, so sorry about that! I'm sure it's just a glitch on our end -- the double charge on invoice INV-20458 will be refunded by tomorrow for sure. I already flagged it to billing and they'll take care of everything, no need to worry about a thing. Let me know if you need anything else!"

Return only the finished work:
1. response QA checklist
2. flagged issues
3. improved response

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one account note standard with sample note that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Create an account note standard and sample note.

Source material:
"Hey, can you look at how we're logging account notes? I pulled up the Bramble account (acct #70558-B) from yesterday and the notes are all over the place -- one rep wrote 'cust annoyed, cb tues,' another wrote three paragraphs about the whole call including her kid's soccer game. Neither one tells the next person what actually happened. Here's what I know actually went down: Denise Ruiz called in on 8/17 because onboarding got delayed twice, she was told Tuesday 8/19 by 2pm someone would call her back, and billing still hasn't confirmed whether her first invoice went out correct. Felix in billing already knows about it. I need a standard for how we write these notes -- what goes in every one -- plus you write it up as an actual note for the Ruiz account so I can see it in practice."

Return only the finished work:
1. account note standard with sample note
2. missing-info prompts
3. privacy caution

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one repaired customer response prompt that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Inspect the weak customer response prompt provided. Identify what is missing, use AI to repair that prompt, then review and edit the AI-repaired prompt. You are not creating a brand-new prompt from scratch. You are repairing the weak prompt provided. The repaired prompt must include role, workplace context, task, boundaries, output format, completion criteria, review rules, and a "STOP FOR NOW" escape phrase (a line that tells the AI when to stop and summarize instead of continuing).

Source material:
Marisol emailed twice about a duplicate charge on order #48821 -- just write her back saying we're crediting it right away and she doesn't need to call in.

Return only the finished work:
repaired customer response prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one reusable account-support prompt that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Create a reusable account-support prompt that turns a messy shift-handoff note like this into a clear customer reply plus a short internal summary of what still needs verifying.

Source material:
"Heads up before you take the chat queue -- Deb Ashworth on acct #88214-C has messaged three times since Tuesday about her invoice jumping from $340 to $610, and the notes say Ingrid promised her a callback yesterday that never happened. She messaged again this morning and said she'll cancel by Friday if nobody explains the charge. I can't find anything on our end showing a plan change, so I don't know if this is proration or a billing error. Can you get me something I can send her today that doesn't promise a refund I can't confirm?"

Return only the finished work:
reusable account-support prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one service recovery standard that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Build a service recovery standard from Grant's recap that reps can actually follow.

Source material:
"Recap from last week, need this turned into something reps can actually use -- ticket 59204, Beatriz Cho, we promised her a callback twice, Tuesday and again Thursday, and neither happened, now she's cc'ing corporate. Account 30412, Rosa Delgado got charged twice for the same install and sat on hold twenty minutes before anyone caught it. The tech no-showed on the Álvarez account for the second time and whoever answered that call logged it as a one-off instead of flagging the pattern. Ticket 51103 got passed from Danny to me to overnight support, and each of us assumed someone else had already called the customer back, so nobody did for four days. And on the other side, Trevor Nguyen swapped out a defective router for the Whitfield account so cleanly the customer emailed to say thanks -- worth building the standard around what he did right. I want a manager callback request to mean something specific instead of just 'the customer is mad,' and I want us catching a repeat miss like Álvarez before the customer has to point it out. Grant"

Return only the finished work:
1. standard
2. response stages
3. escalation triggers

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one safer revised customer response draft that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Review an AI-generated customer response draft for accuracy, missing context, unsafe assumptions, unsupported promises, and human review needs. Then produce a safer revised version. As a Lead deliverable, also write a short review standard your team can reuse: what to always check, what to never accept, and who signs off.

Source material:
You asked your AI tool to draft a reply after a customer named Tasha emailed about a double charge on her account. Here is what it wrote: "Hi Tasha, I've confirmed the $89.50 duplicate charge on invoice #4417 was a billing error on our end, and I've already issued the refund -- it will post to your card within 24 hours. I've also added a 10% credit to your next invoice as an apology for the trouble. I promise this kind of duplicate billing won't happen again, and please don't hesitate to reach out if anything else comes up!"

Return only the finished work:
safer revised customer response draft

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in self-storage facility customer service. Help me create one support quality scorecard that I can review and edit before use.

Relevant context:
- Role: Self-Storage Customer Service Representative
- Work context: You handle unit rentals over the phone, chase down customers behind on payments before a lien sale, and explain a gate-access problem to someone locked out after hours.

Task:
Build a support quality scorecard the team can use in coaching reviews.

Source material:
"Hey — pulled last week's tickets for Thursday's coaching session. Ticket 4482: Nadia took 40 minutes for first reply and the customer's billing question never actually got answered, just an apology. Ticket 4510: Sanjay caught that the account had already been downgraded twice before he said anything to the customer — that's the one I want to hold up as the standard. Ticket 4527: whoever answered told the customer 'you'll have your refund by Friday,' and refunds take five to seven business days minimum, so now I've got an angry callback booked for Monday. I want something I can put in front of the team Thursday that scores these consistently — not just who replied fastest, but who actually solved the problem versus who was just being nice and vague."

Return only the finished work:
1. scorecard
2. metric definitions
3. worked ticket examples

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.