Customer work rarely lives in one ticket. The answer may depend on a help article, an account promise, a product issue, a recent meeting, or a message from the team. The same context matters after the ticket closes, when Customer Success needs to know whether the customer is getting value.

Strawberry can work across those sources in the browser and apps your team already uses. Your companion can open the current records, follow the history across logged-in tools, and carry the account goals, terminology, and response preferences your team agrees on into the next customer interaction.

What Strawberry can help you do

Not sure where to begin? Your companion can look at the customer work you have open and suggest a useful Support or Success skill to try first. See the skill

Understand the customer

A ticket, usage report, CRM record, and meeting note can each tell a different story. Strawberry can bring the useful pieces together, show where they agree or conflict, and keep the sources close enough to inspect. That gives Support better context for the current request and Success a clearer view of whether the customer is getting value.

See whether the customer is getting value

Compare goals, product use, support experience, relationships, and open commitments without hiding uncertainty behind a score.

Skill Review customer health

Carry the conversation into follow-through

Turn reliable notes or a transcript into decisions, commitments, customer follow-up, and the next internal actions.

Skill Debrief a Meeting

Respond and resolve

Good Support work starts with the customer's impact and the team's real policy. Strawberry can read the full thread, check support history and known issues, search current product and help content, and prepare the route or answer with the sources and dates still visible.

Coordinate and escalate

When another team needs to act, Strawberry can turn the customer history into a concise escalation with the impact, timeline, work already tried, current communication, and exact ask. The handoff keeps the customer relationship with Support or Success while the specialist team owns its part of the investigation.

Give the next team an actionable brief

Package the customer impact and the specific investigation, decision, or exception the receiving team needs to own.

Skill Escalate a customer issue

Help customers reach value

Customer Success begins with the outcome the customer expects, not a generic product tour. Strawberry can reconcile the signed scope, sales notes, meetings, account records, setup dependencies, stakeholders, and success measures into a practical path to first value.

Skill

Onboard a customer

Turn agreed goals and commitments into an owned path to first value.

Learn and improve

A verified resolution can improve the help center; a pattern across tickets and conversations can become product insight. These are different jobs. One helps the next customer solve the problem. The other helps Product see recurring themes, tensions, examples, and gaps without automatically deciding the roadmap.

Make customer work repeatable

A useful Support or Success method should not live with one person. Once the team trusts a workflow, Strawberry can preserve the sources, customer context, tone, routing, ownership, and review points behind it.

Skill

Set Up a Shared Team Workflow

Turn a trusted customer workflow into a shared team method with clear context, ownership, review points, and stop conditions.

Share the reviewed result when teammates only need the answer, brief, or account plan. Save the method as a team skill when they should follow the same process. Add a Routine only after the trigger, owner, review behavior, and stop conditions are stable.

Ship what customers actually asked forCarry recurring feedback and customer-reported problems into product insight, flow testing, and grounded bug reports. Automate your sales pipelineSee how account research, meetings, commitments, and customer context can carry into a cleaner handoff. Run an AI-native ops teamConnect customer work with meetings, open loops, status updates, and shared team workflows.
Official Strawberry skill
Copy skill file Download skill file
name
getting-started-with-customer-support-and-success-in-strawberry
description
Help Customer Support and Customer Success teams get started in Strawberry across customer context, request handling, escalation, onboarding, health, and learning. Use when someone asks what Strawberry can do for Support or Success or has a broad customer request without a clear starting workflow.

Getting Started with Customer Support and Success in Strawberry

Help the user see how their companion can support the connected work of helping customers, then complete one useful piece of it. Keep reactive Support work and proactive Success work equally visible without pretending they follow one sequence.

Paint the customer system

Explain briefly that Strawberry can work across the support desk, CRM, account notes, product docs, help center, email, team messages, meetings, project tracker, product, files, and the visible browser. The companion can bring together the context that changes the response, keep sources beside claims, and carry accepted account goals, tone, and review rules into the next interaction.

Show the system through five connected lanes:

  • Understand the customer: bring together goals, history, product context, health signals, prior commitments, and the current question.
  • Respond and resolve: triage requests, research grounded answers, communicate clearly, and keep the next owner and follow-through visible.
  • Coordinate and escalate: package customer impact, route bugs and sensitive cases, and maintain the customer relationship while specialist work continues.
  • Help customers reach value: turn accepted goals into onboarding, progress reviews, useful customer conversations, and clear next actions.
  • Learn and improve: turn verified resolutions into better help content and recurring customer feedback into source-linked product insight.

Support often moves from request to context, response or escalation, resolution, and learning. Success may begin with onboarding, a health review, or a planned conversation. Enter where the customer work needs attention now.

Choose a useful first result

Understand the customer or account, current request or goal, decision due, channel, deadline, and available evidence. Use approved context already available before asking the user to repeat it.

If the user is unsure where to begin, recommend a small, situational set such as:

  • triage the next customer request and prepare the right first response;
  • research a question the team cannot answer confidently;
  • review one customer account for progress, risk, and next steps; or
  • turn a confirmed new customer into an owned onboarding plan.

Explain why the options fit. Suggest another connection only when it materially improves the chosen result; do not require the entire customer stack before helping.

Route each job to its owner

  • Triage a request: read strawberry/customer-support-success/triage-a-customer-request.
  • Research and answer a question: read strawberry/customer-support-success/research-and-answer-a-customer-question.
  • Package a customer escalation: read strawberry/customer-support-success/escalate-a-customer-issue.
  • Create or update customer documentation: read strawberry/customer-support-success/create-or-update-a-help-center-article.
  • Onboard a customer: read strawberry/customer-support-success/onboard-a-customer.
  • Review customer health: read strawberry/customer-support-success/review-customer-health.
  • Research, reproduce, and report a product bug: use strawberry/product-engineering/research-and-report-a-bug. Support owns customer impact and communication; Product and Engineering owns product evidence and the issue record.
  • Synthesize recurring feedback for Product: use strawberry/product-engineering/synthesize-customer-feedback.
  • Prepare for or debrief a customer conversation: use strawberry/operations/prepare-for-meetings or strawberry/operations/debrief-a-meeting, bringing the relevant account goals, health, history, and commitments.
  • Coordinate ownership and updates: use strawberry/operations/close-open-loops or strawberry/operations/prepare-a-status-update when that horizontal result is primary.

If no focused skill fits, help normally rather than forcing the work into the closest package.

Learn without leaking customer context

When tone, priority, routing, or health rules are new, calibrate with a small, varied set before scaling. Preserve accepted sources, tone, definitions, ownership, and review rules after they prove durable. Keep customer-specific private context out of broad trend reports and reusable methods.

Share an approved artifact when teammates only need the result. Save a team skill when the group should use the same method. Share the full companion when they need the same ongoing customer context across several workflows. Offer a Routine only after a workflow has a real trigger, named sources, output, destination, approval behavior, and stop conditions.

Keep judgment and actions clear

Use the team's actual priority, SLA, health, ownership, and escalation rules; do not invent a universal severity or churn score. Drafting, sending, refunding, changing an account, granting access, updating a ticket, filing an issue, publishing help content, and making a product commitment are different actions.

Follow Strawberry's active scoped permission for the exact account, destination, and action. Draft or ask when permission is insufficient; stop when identity, scope, impact, or sensitive-data handling changes; verify completed external actions. Suspected security, privacy, data-loss, legal, regulated, or active incident cases go immediately to the team's accepted specialist path.