The fastest support answer is not useful if it relies on an outdated help article, ignores what the customer was promised, or turns an internal discussion into a product commitment. Reliable answers often require several sources and a clear view of which one is authoritative.

Strawberry can search product docs, help content, support history, account notes, messages, project records, and official external sources without asking you to copy each result into a new chat. Your companion keeps the sources and dates visible, then prepares the answer for the actual customer and channel.

Define the real question

Read the full thread and identify the exact question, account, audience, deadline, and decision the response should support. Flag roadmap, pricing, contracts, security, privacy, compliance, billing, refunds, and custom configurations because they may need a named reviewer even when the likely answer is clear.

Want to try it?

Ask your Strawberry companion: “Research this customer question across our approved sources, reconcile any conflicts, and prepare an accurate response with the evidence and review needs clear.”

Skill

Research and answer a customer question

Find the strongest available answer and prepare a response that fits this customer and channel.

Search in an order that protects accuracy

  1. Check current approved product documentation, policy, help content, and known issues.
  2. Use support history and account context for prior treatment, commitments, and customer-specific facts.
  3. Use team discussions and project records to identify current work without treating informal notes as customer-ready truth.
  4. Use official external documentation when a partner, integration, or current public fact matters.

Keep the source, date, product version, and account scope beside each material finding. A past reply may explain the relationship while still being wrong about current behavior.

Show what is known and what is not

When sources disagree, explain which is more authoritative or recent and what still needs confirmation. Separate verified product behavior, account-specific history, inference, and unknowns. If no reliable source answers the question, identify the smallest useful check rather than filling the gap with a plausible response.

ResultWhat the reviewer should see
Direct answerThe bottom line in the customer's language.
EvidenceCurrent source links, dates, and versions that support it.
CaveatsContradictions, account-specific limits, and questions still open.
Response draftCustomer-ready wording plus internal notes that should not be sent.

Reuse the answer carefully

After the team confirms the answer, Strawberry can remember trusted sources, product terminology, tone, and review rules. Save that method as a team skill when colleagues should research and answer similar questions the same way. A recurring question may deserve a help-center update, but private account history should not become reusable customer guidance.

Skill

Create or update a help center article

Turn a verified recurring answer into current, findable customer documentation.

How to triage customer requests with AIAssess the request and decide whether it needs an answer, escalation, or another route. How to create better help-center articles with AITurn a verified recurring answer into clear, findable customer documentation. How to escalate customer issues with AIPackage the customer impact and exact internal ask when another team needs to act.
Official Strawberry skill
Copy skill file Download skill file
name
research-and-answer-a-customer-question
description
Research a customer question across approved product documentation, help content, account history, prior cases, team discussions, and current external sources; reconcile contradictions and prepare a source-grounded response. Use when Support or Success needs a reliable answer rather than a quick unverified draft.

Research and Answer a Customer Question

Find the most reliable answer available and turn it into a response that fits the customer and channel. Do not invent product behavior, policy, commitments, or account-specific treatment to fill a documentation gap.

1. Clarify the question

Identify the precise question, customer or account, audience, channel, deadline, and decision the answer needs to support. Read the current thread so the response addresses what the customer actually asked and does not repeat questions they have already answered.

Flag questions involving roadmap, pricing, contracts, security, privacy, compliance, billing, refunds, or a custom configuration. These may need a named reviewer even when research produces a likely answer.

2. Search the best sources

Start with current approved product documentation, policies, help-center content, and known-issue records. Then use relevant support history, CRM or account notes, prior communications, meetings, team discussions, project records, and official external documentation.

Prefer authoritative and current evidence. Preserve links, dates, product versions, account scope, and what each source establishes. A prior answer may reveal relationship context without becoming current policy.

3. Resolve conflicts and gaps

Compare the sources instead of stopping at the first plausible result. When they disagree, explain which is more authoritative or recent and what still needs confirmation. Keep verified facts, account-specific history, inference, and unknowns distinct.

If no reliable source answers the question, say so and identify the smallest useful verification: an owner, document, product check, or specialist review. Do not turn an internal roadmap note or informal chat message into a customer commitment.

4. Prepare the response

Lead with the direct answer when the evidence supports one. Match the language and level of detail to the customer and channel, use their terminology, and include only the context they need. Link the relevant customer-facing source or explain the next step and timing when the answer is not yet final.

Deliver:

  • the answer and confidence-driving evidence;
  • source links and important dates or versions;
  • contradictions, caveats, and remaining questions;
  • a customer-ready draft; and
  • internal review or follow-through notes that should not be sent.

Use strawberry/customer-support-success/create-or-update-a-help-center-article when a verified answer should become reusable customer documentation.

5. Keep sending and learning separate

Drafting, sending, updating a ticket, changing account settings, offering a refund, and making a product or commercial commitment are different actions. Follow the active scoped permission for the exact customer, channel, account, and action, and verify any completed change.

After the team confirms the answer, preserve useful source preferences, tone, terminology, and review rules. Keep customer-specific private context out of the reusable method.