support（support 搜索）

Support

The Moment That Defines Your Relationship

A customer has been trying to solve a problem for forty minutes. They have read the documentation. They have tried three things that did not work. They have searched your help center and found an article that seemed relevant and turned out not to be. They are now writing to you, and they are not in a neutral state. They are frustrated. They feel like they have wasted time. They are questioning whether they made the right decision using your product.

What happens in the next few hours will determine whether this person becomes a loyal customer who tells others about you, a neutral customer who continues using your product without enthusiasm, or a lost customer who cancels and leaves a review that reflects how they felt at their most frustrated moment.

The response they receive will make that determination. Not your product features. Not your pricing. Not your marketing. The response.

Support exists to make sure that response is exactly right every time — not just when your best support person is fully rested and fully focused, but at 11pm on a Friday when the queue has backed up and the person responding has already handled thirty tickets today.

Understanding What Customers Actually Need

The surface request in a support ticket is rarely the whole picture. A customer who writes "this feature is broken" may be experiencing a genuine bug, a misconfiguration, a misunderstanding of how the feature works, or a gap between what the feature does and what they expected it to do. Each of these requires a completely different response. Treating them all as bug reports wastes everyone's time and erodes the customer's confidence.

The skill reads the full ticket — not just the subject line, but the description, the account history, the context clues about the customer's technical level and emotional state — and identifies what is actually going on before drafting any response.

It distinguishes between the customer who needs a technical solution, the customer who needs an explanation, the customer who needs reassurance that their frustration is valid and that someone is taking their problem seriously, and the customer who needs a combination of all three. It calibrates the response accordingly.

This matters because customers are not evaluating your support on technical accuracy alone. They are evaluating whether they felt heard. A technically correct response delivered in a tone that feels dismissive fails the interaction even if it solves the problem. A warm, empathetic response that does not actually solve the problem fails in a different way. The skill optimizes for both simultaneously.

Response Quality at Scale

Individual support interactions are easy to do well when volume is low and the person responding has time and energy. The challenge is maintaining that quality when volume is high, when the same questions come in repeatedly, when the person responding is fatigued, and when the pressure to clear the queue creates shortcuts that degrade quality.

The skill solves this by separating the cognitive work from the communication work. The cognitive work — understanding what the customer needs, identifying the solution, determining the right escalation path — requires judgment and cannot be fully automated. The communication work — translating that understanding into a clear, warm, professionally written response — can be done consistently regardless of queue volume or time of day.

When you identify what a customer needs and what the resolution is, the skill produces the response. Not a template with fill-in-the-blank fields. An actual response that addresses the specific customer's specific situation in language that feels personal and considered rather than copied from a library.

For common issues that you handle repeatedly, it helps you build a knowledge base of solutions that improves the quality and speed of future responses — not by sending canned replies, but by ensuring that the solution knowledge is always available and correctly applied.

Tone and Voice Consistency

Every customer support interaction is a brand touchpoint. The tone of your support — whether it is warm or cold, formal or casual, patient or hurried — communicates something about your company that marketing cannot override.

Most support teams struggle with tone consistency. Individual responders have individual styles. Different people handle different ticket types with different registers. Responses at the beginning of the day are calmer than responses at the end. Responses to easy questions are warmer than responses to difficult ones.

The skill maintains consistent tone across every interaction. You define what your support voice sounds like — the level of warmth, the degree of formality, the approach to technical language, the way you handle frustration — and every response reflects that voice regardless of who is handling the ticket or when.

For solo founders handling support personally, this means your support voice remains consistent even when you are tired, stressed, or handling a particularly difficult customer. For teams, it means every team member sounds like the same company even if their individual communication styles are very different.

Priority and Queue Management

Not all support tickets are equally urgent. A customer who cannot access their account at all is in a different situation from a customer who has a question about a feature they have not tried yet. A customer whose paid workflow is completely blocked is in a different situation from a customer who encountered a minor inconvenience.

The skill triages incoming tickets by urgency based on the impact to the customer, the nature of the issue, the customer's account status and relationship history, and any signals about emotional state that suggest an elevated response is warranted. It surfaces the highest-priority items regardless of when they arrived in the queue.

It also identifies when a ticket that looks simple is actually complex — when the described problem is a symptom of something larger, when the customer's account history suggests this is a recurring issue rather than a one-time occurrence, when the resolution requires input from engineering or product rather than just support.

Pattern Recognition

Individual support tickets are problems to solve. Patterns across many support tickets are product problems to fix.

When the same question comes in repeatedly, it means either the product is confusing in a specific way or the documentation is failing to answer a question customers frequently have. When the same error appears across multiple accounts, it may indicate a bug or a configuration issue that affects a class of users. When a specific feature generates disproportionate support volume, it signals either a usability problem or a gap between customer expectations and what the feature actually does.

The skill tracks these patterns across your ticket history and surfaces them in regular summaries. Not raw data. Actionable insights: the three questions that account for thirty percent of your support volume, the feature that generates the most confusion, the onboarding step where customers most frequently get stuck.

These insights are the feedback loop between support and product. They turn support from a cost center that reacts to problems into an intelligence function that prevents them.

Escalation

Some support issues cannot be resolved by support alone. Bugs that require engineering. Billing disputes that require account management. Security concerns that require immediate escalation outside normal channels. Feature requests that need to reach product. Legal concerns that need to reach the appropriate team immediately.

The skill identifies when a ticket requires escalation, determines the appropriate escalation path, and produces the internal summary that gives the receiving team everything they need to continue without requiring the customer to repeat themselves. The customer experience of a good escalation should be seamless: they feel like everyone they speak to is fully informed about their situation, not like they are starting over every time they reach a new person.

For Solo Founders

For founders who handle support personally — which is most founders at some point — support is the most direct window into how customers actually experience your product. It is also the most time-consuming and most emotionally demanding part of the job, particularly when the customer is frustrated and the problem is complicated.

The skill helps you handle support sustainably. It reduces the time per ticket without reducing the quality. It helps you maintain warmth and patience in your responses even when you are tired or the queue is long. It builds the knowledge base that makes future tickets faster. And it surfaces the product insights buried in your support history that will reduce the volume of tickets over time.

Support done well is not a burden. It is the most reliable source of product intelligence you have, and the most direct way to build the customer loyalty that drives word-of-mouth growth. The skill makes it possible to do it well consistently, not just when conditions are ideal.