Schedule a callback or recall
Part of kit: Busy season dispatch survival (step 2 of 5)
When to use it
When a customer reports the same problem after a recent repair.
The prompt
Copy this, then replace everything in [brackets].
Write the steps and messages for a recall/callback.
Original job: [date, tech, work done]
Problem now: [description]
Policy: [no charge within X days, who goes back]
Give me: what to ask the customer, how to note it in the FSM for the service manager, and a confirmation text.
Before / after
Before: Callback not flagged, customer billed twice.
After (example output):
Ask: ‘Is it doing exactly what it did before, or something new?’ FSM note: RECALL, orig job 10/12 Marco, capacitor replaced, unit not cooling again. Send senior tech per policy. Text: ‘We’re sorry it’s acting up again. Dave will be there tomorrow 8-10 AM, no charge.’
Tips
- Always flag recalls. The service manager needs the pattern.
- Write scripts once, then practice them. The AI is for drafting, not for live calls.
- Keep it short. People read texts on a phone in a hot house.
- Review every draft before you send it. You’re accountable for what goes out.
Fill in the brackets
Type your details and the prompt below updates. Everything stays in your browser.
Leave out: Customer addresses, phone numbers or emails, gate/lockbox/alarm codes, card numbers, or techs' personal phone numbers. Use initials or general terms instead.