35 Prompts for Customer Support Replies
Latchly sells smart locks, and its nine-person support team handles about 1,100 tickets a week, half about a firmware update that will not finish or a lock that will not pair. Support lead Dana Whitfield measures first-response time and CSAT on every ticket, so a reply that sounds robotic or misses a step costs twice. The 35 prompts below are grouped by the ticket types her team sees most; each is copy-paste ready, so swap in your own product names. To make the tone stick across the whole team, set up custom instructions, and for the decision behind each wording choice read the tone of voice decision table.
Firmware Update and Upgrade-Failure Replies
Half of Latchly’s volume lives here. A clear step list beats a long apology.
Reply when firmware 3.2.4 stalls at 60 percent.
Write a support reply to a customer whose Latchly lock stalls at 60 percent during the 3.2.4 firmware update. Give numbered steps to retry over a stable 2.4GHz network, then the reset that clears a corrupt download. 120 words max, no jargon, end with a one-line check-in ask: [paste customer message].Explain why an old firmware version will not update.
A customer on firmware 2.9.1 cannot update directly to 3.2.4. Write a reply explaining the bridge update in plain language: why one version must be skipped, what the two-step path is, and how long each step takes. Warm but brief: [paste ticket].Give a customer the manual offline update option.
Write a reply offering the offline firmware update for a customer with unstable wifi. List what they need (a phone, the file, a USB-C cable), the four steps, and the one warning about not removing power. Numbered list, under 150 words: [paste ticket].Reply after an update drained the battery faster than usual.
A customer says the 3.2.4 update made their lock drain battery in a week. Write a reply acknowledging the report, giving the calibration reset, and stating honestly what we know so far. No overpromising; offer a replacement battery if the reset fails: [paste ticket].Tell a customer their lock is already on the latest firmware.
Write a short reply to a customer whose app shows no update available, explaining how to confirm the installed version in Latchly Home, and what to do if the number looks wrong. Under 100 words, friendly, one clear verification step: [paste ticket].Reply when an update bricked the lock and the keypad is dead.
Write an urgent reply to a customer whose lock stopped responding after the 3.2.4 update and whose keypad is dark. Give the hard-reset sequence, the physical key fallback, and a clear next step if the lock stays dead. Lead with the reassurance, then the steps: [paste ticket].Follow up 24 hours after a firmware fix to confirm it worked.
Write a 60-word follow-up to a customer we helped fix a firmware issue with yesterday. Ask if the lock is working, offer one troubleshooting link, and tell them how to reopen the ticket. Warm, not automated-sounding: [paste prior reply].Wi-Fi and Bluetooth Pairing Issues
Pairing tickets are usually a network detail, not a broken lock.
Reply when the app cannot find the lock during setup.
Write a support reply for a customer whose Latchly Home app cannot find their new lock during setup. Walk through: Bluetooth on, lock within two feet, fresh batteries, and the pairing-mode button. Numbered steps, 130 words, end with a check-in: [paste ticket].Explain the 2.4GHz versus 5GHz confusion.
A customer's lock pairs then drops. Write a reply explaining that Latchly connects on 2.4GHz only, how to check which band their router is broadcasting, and how to split the bands. Simple language, no networking jargon unless explained: [paste ticket].Handle error code E-14 (pairing timeout) with a fix path.
Write a reply for a customer seeing error E-14 on pairing. Decode E-14 in one sentence, then give the three-step fix (clear app cache, forget the lock, re-pair within 90 seconds). Numbered list, under 120 words: [paste ticket].Reply when a guest cannot connect after a re-pair.
Write a reply to a host whose guest access stopped after re-pairing the lock. Explain that pairing resets shared access, then give the steps to re-invite the guest and how many guests a Latchly lock supports. Reassuring tone: [paste ticket].Give steps when Bluetooth works but Wi-Fi setup fails.
Write a support reply for a customer who can pair over Bluetooth but cannot finish Wi-Fi setup. List the four likely causes (band mismatch, wrong password, weak signal, VPN) and the check for each. Keep it to a numbered list and one closing question: [paste ticket].Reply to a customer whose lock disconnects every few days.
A customer reports the lock going offline every few days. Write a reply with the stability checklist: router distance, interference from a nearby microwave, firmware version, and the diagnostic log export. Ask them to send the log and set a follow-up expectation: [paste ticket].Write a reply when pairing needs the latest app version.
Write a short reply telling a customer that pairing requires Latchly Home 4.6 or later. Explain how to check the app version on iOS and Android, how to update, and what to do if their phone cannot update. Under 110 words: [paste ticket].Warranty, Returns and RMA Replies
Money questions need certainty, not warmth alone. Be exact.
Reply to a warranty claim with the exact coverage.
Write a reply to a customer claiming warranty on a Latchly lock bought 14 months ago. State the 24-month coverage, what is included, and what is not. Ask for the order number and a photo of the serial. Confident and clear, no hedging: [paste ticket].Explain the returns window and process.
Write a reply explaining Latchly's 30-day return window: how to start a return, who pays return shipping, how long the refund takes, and what condition the lock must be in. Bullet points, under 140 words: [paste ticket].Open an RMA and set expectations.
Write a reply confirming a replacement for a defective lock. Include the RMA number placeholder, what to send back, the prepaid label step, and the 5 to 7 day shipping window for the replacement. One clear next step for the customer: [paste ticket].Decline a claim that falls outside policy, kindly.
A customer wants a refund after 9 months, past the 30-day window. Write a reply that holds the policy, explains the warranty option that still applies, and offers one goodwill gesture. Firm, respectful, no over-apologising: [paste ticket].Reply when the wrong item was shipped.
Write a reply to a customer who received the wrong lock model. Apologise once, confirm the correct model, arrange the swap with a prepaid label, and tell them when the correct item ships. Under 120 words, action-first: [paste ticket].Handle a chargeback threat calmly.
Write a reply to a frustrated customer who threatens a chargeback. Acknowledge the frustration, restate the resolution we can offer today, and give the escalation contact. Do not cite chargeback policy as a threat. Under 140 words: [paste ticket].Confirm a refund has been issued and when it lands.
Write a short reply confirming a refund of [amount] for a returned Latchly lock. State the date it was issued, the 5 to 10 business day posting time by payment method, and who to contact if it does not arrive. Under 100 words: [paste ticket].Tone, De-escalation and Priority Handling
An angry ticket is a speed problem first and a wording problem second.
De-escalate a customer who was locked out of their home.
Write a reply to a very upset customer who was locked out when their Latchly lock failed. Lead with a sincere apology, confirm we are treating it as urgent, give the physical-key and battery-jump steps, and offer a callback within the hour. Calm, human, no excuses: [paste ticket].Reply to a review that mentions support by name.
Write a public reply to a one-star review that criticises an agent by name. Thank them, remove blame from the agent, state what we are fixing, and invite a private message. Never argue in public. Under 90 words: [paste review].Soften a reply that has to say no.
Rewrite this reply so the "no" lands kindly without hiding it. Keep the policy wall time clear, add one alternative the customer can use, and close with a warm line. Do not bury the refusal: [paste draft reply].Reply to a customer writing in a second language.
A customer writes in halting English and may be using translation. Write a reply in simple, short sentences, avoid idioms, and confirm understanding at the end by asking them to reply "yes" if the steps are clear. Under 120 words: [paste ticket].Escalate a VIP or bulk-installer ticket with context.
Write an internal escalation note for a property manager who installs Latchly in 40 units and has a repeat pairing failure. Summarise the issue, the units affected, what has been tried, and what you need from engineering. Under 150 words: [paste history].Reply when the fix is a known bug with no ETA.
Write a reply telling a customer their issue is a known bug with no fix date yet. Acknowledge it, give a workaround, set an honest expectation for updates, and offer to keep the ticket open and notify them. No false timelines: [paste ticket].Turn an angry interaction into a satisfaction recovery.
Write a follow-up reply after resolving a heated ticket, to check the customer is now happy and confirm the fix. Keep it short, personal, and free of survey language. End with one open invitation to reply. Under 80 words: [paste ticket].Macros, QA and Knowledge-Base Polish
These keep the whole team consistent once the one-off replies are done.
Turn a good reply into a reusable macro.
Turn this resolved Latchly firmware reply into a support macro. Replace specifics with placeholders in square brackets, keep it under 140 words, and add a note on when to use it versus the manual-update macro: [paste reply].Audit a macro for outdated steps.
Review this macro against the current Latchly Home app flow. Flag any step that no longer matches, any stale version number, and any instruction that assumes a removed feature. Suggest the corrected lines: [paste macro].Improve a knowledge-base article from real tickets.
Here are 12 real pairing tickets from this week. Identify the three questions customers keep asking that our help article does not answer, and draft the missing section for the Latchly pairing guide. Plain steps: [paste tickets].Create a QA checklist for outbound replies.
Write a QA checklist a team lead can use to review Latchly support replies. Cover: correct steps, accurate version numbers, correct tone, clear next step, and no promises we cannot keep. One line per check, with a pass or fail mark: [paste context].Grade a reply against house tone and fix it.
Grade this draft reply on clarity, warmth, brevity, and correctness from 1 to 5, and rewrite any sentence that scores below 4. Keep the facts identical. Explain each change in one line: [paste draft reply].Summarise a week of tickets into a product insight.
From these 40 ticket summaries, extract the top three recurring Latchly issues, the affected firmware versions, and the volume of each. Write a 5-bullet note the product team can act on. Quantify wherever possible: [paste tickets].Write a reply template for a brand-new error code.
A new Latchly firmware error, E-27, is appearing on 3.2.4. Write a holding reply we can send before the fix ships: acknowledge it, give a temporary workaround, and ask for the diagnostic log. Keep it honest about the unknowns: [paste known details].Bonus: Making 1,100 Tickets Feel Like Fifty
Reply from the ticket, not from memory. Paste the customer’s exact wording every time so the model mirrors their error code and step. Keep one macro per error code. E-14 will return; a tested reply beats a fresh draft under deadline. Never promise a date you do not control. Ask for expectations, not timelines. Review tone monthly. Grade ten replies a month against the same checklist. For routing and priority, see our inbox triage comparison.
Sources & Notes
Prompts were tested against ChatGPT (GPT-4o class) through 2025 and are model-agnostic. Support prompts work best with the real ticket text and product version, then a check of every factual claim, since a wrong error code reaches a customer instantly. Latchly, Dana Whitfield, and firmware 3.2.4 are fictional; use your own product and versions, and never invent a warranty term or an RMA number.
