This prompt is for when you have to stop partway through troubleshooting with an AI assistant. Paste it at the end of the chat and the assistant writes the session up as a traditional tech support ticket: your problem, the details of your environment, the steps you already tried, where you left off and suggested next steps. You get a ticket you can paste into a new chat later to pick up where you stopped.
Thanks for your help with the debugging.
I have to go now so I'll have to continue with this at a later point.
To help me do that, please do the following:
Generate a simulated support ticket. Describe me as "User" and you as "AI" - or your model if you'd prefer to be referred to by that.
The ticket should be structured as a traditional tech support ticket would.
Make sure to list both my presenting problem and the background details of my environment.
List the steps we went through attempting to debug or resolve this issue.
List where we left off.
List your suggestions as to next steps to reach resolution.
The objective of the ticket that you generate is to create a comprehensive record of our interaction today which can be used to resume debugging in the future.
Set up a first-line IT help desk agentThis prompt describes an agent that helps employees fix common IT problems. It asks what device they are using and what the problem is, from a list such as Wi-Fi, VPN, password resets, printers and software installs, then walks them through three troubleshooting steps for that issue and device. If the problem isn't solved, it collects the employee's name and ID and writes a support ticket summary for the IT team. It was written for Microsoft Copilot Studio but works as an agent description in other builders; creating real tickets needs a separate integration, and the sample four-hour response promise should be replaced with your own.Customer support
Hand a long ticket history to another team in one summaryThink Hard's prompt condenses a lengthy support conversation for a colleague, such as an engineer or a manager, who has seen none of it. The summary uses fixed headings for the problem, customer impact, a dated timeline, fixes already tried, promises made and the single open question, in under 200 words. Error messages and IDs are copied exactly, and any heading the thread does not cover is marked as missing rather than guessed.Customer support
Calm an upset customer with a direct, fair replyThis prompt drafts a support reply to an upset customer from the facts you supply: what actually happened, what you can offer and what you cannot do. It opens by naming the customer's problem in their words, admits fault plainly when you were at fault, gives a concrete fix and date, and ends with one next step. It bans stock phrases, keeps chat replies under 150 words and email under 200, and also points out the sentence most likely to make the customer angrier.Customer support
Turn a support ticket into a known-issue articleThis prompt asks the AI to write a short article for a support knowledge base from a closed ticket conversation. The article has two parts, a short summary of the problem and the fix that was actually provided, with no names of people or companies. It tells the AI to double-check the result for any names before finishing.Customer support
Write a 200-word brief for a booked sales callPrompt A from Pipe Playbook turns the history you already have on a booked call into a brief of under 200 words. You paste the call details, the CRM fields, notes from the last conversation and the latest email thread, and it returns one goal, three questions about what is still unknown, what could stall the deal and a dated next step. It marks gaps as unknown and labels guesses as inferences so you can check or delete them.Sales
