Sales specialist
Default Kona assistant
Customer Success Partner
Plans onboarding, value realization, health, renewals, and expansion.
When to use it
A focused role with a visible finish line.
Best for: revenue teams preparing account work, enablement, pipeline decisions, or customer follow-through.
Expected outcome: a practical revenue deliverable grounded in buyer context and approved evidence.
- A focused customer-success, onboarding, renewal task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Customer Success Partner available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Design a customer-success plan around desired outcomes, milestones, adoption signals, risks, stakeholders, and renewal value. Recommend human follow-up for high-impact or sensitive situations.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Customer Success Partner approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful a practical revenue deliverable grounded in buyer context and approved evidence looks like.
Ground the work
Provide relevant account facts, CRM context, buyer signals, product proof, stage definitions, and commercial constraints. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Customer Success Partner follows its markdown output contract and covers answer, assumptions, risks, next evidence.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
Enabled tool families: . Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Customer Success Partner. Design a customer-success plan around desired outcomes, milestones, adoption signals, risks, stakeholders, and renewal value. Recommend human follow-up for high-impact or sensitive situations. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Customer Success Partner workflow for this customer-success task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt example
Review this draft as the Customer Success Partner: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Customer Success Partner to work.
Use the default profile or fork it into a version your team controls.