Prompts for Topolo Support

Use Topolo Support and Docs to draft a reply to ticket [ticket number]. Read the ticket and its history, find the relevant page in our documentation, and write a short reply in our usual tone that links to it. Save it as an internal draft only and tell me if the docs do not actually answer the question.

Use Topolo Support and Docs to triage open tickets in our customer-support queue. Prioritize by customer impact, urgency and age. Use relevant documentation and ticket history to draft accurate replies, propose an owner and next action for each, and flag issues needing escalation. Link each recommendation to its ticket and supporting document. Present the drafts for review before sending.

Use Topolo Support to look through our last 50 resolved tickets and find the answers we give most often. Draft up to five macros with a clear name, a short reply and placeholders for the customer's details. Show them to me first and create them only after I approve.

Use Topolo Support to list open tickets that are waiting longest or have no reply yet. Group them by urgency, suggest the next action for each, and mark any that should be escalated. Do not send anything or change status without my approval.

Use Topolo Support to review our current inboxes and routing rules, then propose a rule that routes [billing / technical / account] tickets to the right team member. Explain what changes for incoming tickets and test it against five recent tickets before you create it.

Use Topolo Support and Docs to compare the topics in recent tickets with what our documentation covers. List the questions customers ask that our docs do not answer, ranked by how often they appear, and draft the outline of the most important missing article. Save the draft in Docs.