Try it in Gainsight Copilot today. Copy the prompt, paste it in, and type the customer's name. It reads Gainsight, and Staircase when that is connected.
Try it first on an account you know well. If the answer and your instinct disagree, check the dates.
No ARR on the record? The prompt asks Copilot to say so instead of guessing.
Renewal, last activity, and due dates sit next to each risk, so a stale flag is easy to spot.
Sentiment and what the customer said come from Staircase. If it isn't connected, Copilot says so.
It asks for a summary. It doesn't ask Copilot to post to Timeline or update a CTA.
Gainsight Copilot works with what's in Gainsight, plus Staircase when your admin has connected it. In the AI agent of your choice, that same data sits next to the calendar, email, and chat tool your company has connected, so a skill can do more of the job.
Copy a prompt, paste it in, add the customer name.
Add a skill once, then ask in plain words, like "prep my week."
Seventeen prompts, built from the Agentic and headless use cases in the enablement hub and the published Customer Success library. Most need only a customer name. The handoff prompt also takes your notes, and the capacity plan takes your hours. The same text lives in the prompts folder.
Each skill installs on its own. Every card says what it reads, what it writes, and what it needs. Download all four skills.
A Monday-to-Friday view of your external calls. Each one opens into a brief, talking points, a draft agenda, and exec email options.
Seven sections: executive summary, why this call, how they make money, objectives, contacts, risks, and maturity.
Reads your recent calls, checks what Timeline already says, and adds only what's missing to each open risk task.
Fourteen fixed layouts, from account summary to portfolio health. A missing value shows a dash, never a made-up number.
Every prompt and skill says to label missing values. Verify high-stakes numbers in Gainsight.
Emails land as drafts. Nothing sends until you send it.
Exec prep posts automatically. Risk updates post to task Timelines. Weekly briefs write only when you click.
These recipes don't widen what the connector can see. If a result looks wrong, stop and tell your admin.
No. Copy a prompt, paste it into Gainsight Copilot, and add the customer name. Staircase is included when it is already connected.
Yes. Claude, ChatGPT, and other agents that read a skill can run these once Gainsight is connected. Calendar, email, and search come from the tools that agent already has.
No. When a prompt or skill needs an account, you give the customer name. The skills find the Gainsight records for you.
Check the date next to it. Stale or noisy signals are worth flagging to CS Ops.
Copy the prompt, paste it in, add the customer name. When you want your whole week prepped, add the skills to the AI agent you already use.
Prep me for my next call with [customer name]. Tell me where the account stands (health, renewal, ARR, stage), who I should talk to, the open risks and CTAs, what happened recently on the timeline, the landmines to avoid, and 3 questions I should ask. If Staircase is connected, include sentiment and what the customer said on recent calls. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
How is [customer name] doing? Show health, the trend, renewal, stage, and what moved health. If Staircase is connected, include sentiment and what the customer said on recent calls. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
Summarize the last 30 days on [customer name]. Give the highlights, open issues, decisions still waiting, and the next meeting if one is scheduled. If Staircase is connected, include sentiment and what the customer said. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
Tell me the full customer story for [customer name] ahead of a business review. Write one narrative: where the relationship stands, what they are trying to achieve, what has landed, and what is stuck. Use Gainsight for health, renewal, CTAs, the success plan, and the timeline. If Gainsight PX, Skilljar, Community, or Support is connected, fold in product adoption, certification, community engagement, and support, and name the source. If one is not connected, say so and leave it out. If Staircase is connected, add sentiment and what the customer has said. If it is not connected, say so. Then give a short exec briefing: what leadership will ask, and the talking points. Then outline the QBR or EBR deck from that narrative, slide by slide, using PX adoption and Skilljar certification numbers where they exist. Do not change anything in Gainsight. If a value is missing, say so. Do not invent numbers.
Help me prepare for [customer name]'s renewal. Summarize relationship health and the trend, value delivered (wins they have acknowledged), open concerns to handle before renewal, risk factors, and any expansion signals. Give talking points for each. If Staircase is connected, include sentiment, competitor mentions, and quotes I can use. If it is not connected, say so. Do not post or change anything in Gainsight. If a value is missing, say so. Do not invent numbers.
Who matters at [customer name]? For each person, give their role, last engagement date, recent topics, and whether they look active or quiet. Call out a single-threaded relationship if you see one. If Staircase is connected, include sentiment. If it is not connected, say so. If a value is missing, say so. Do not invent names.
What is the success plan on [customer name]? Show the current objectives, status, and what recent timeline activity says about each one. If there is no plan, propose 3 to 5 objectives from the open CTAs, risks, and recent activity, and name which template fits. Do not create or update anything. If Staircase is connected, include what the customer said they want. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
I'm taking over [customer name]. Give me a briefing: where the account stands (health, renewal, ARR, stage), the people who matter and who has gone quiet, recent wins and open issues, red flags, and what I should do in the first 30 days. If Staircase is connected, include sentiment and what the customer said on recent calls. If it is not connected, say so. Do not change anything in Gainsight. If a value is missing, say so. Do not invent numbers.
Draft a follow-up email after my last call with [customer name]. Use recent timeline and call context. Reference one specific thing they said or we agreed, state the next step, and keep it short. If Staircase is connected, use what the customer actually said. If it is not connected, say so and draft from Gainsight only. Do not send the email. If a value is missing, say so. Do not invent numbers.
Brief me for an exec meeting with [customer name]. Cover sentiment and what is behind any recent drop, product usage, open support issues, the renewal date and ARR, and the stakeholders in the room and where each one stands. Tell me what their leadership will push on, and give me the talking points. Keep it to one screen. If Staircase is connected, use sentiment and what the customer said on recent calls. If it is not connected, say so. Do not post or change anything in Gainsight. If a value is missing, say so. Do not invent numbers.
[customer name] needs an escalation and save plan. Tell me why it is at risk, who we need in the room and where each person stands, and the next three moves. Draft the timeline entry and the CTAs I would open in Gainsight. Do not post or create anything until I approve. If Staircase is connected, use what the customer said and how sentiment has moved. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
Here are the post-sales handoff notes for [customer name]: [paste notes]. Write a one-page exec briefing handoff readout: what we sold, who owns the relationship, the outcomes they expect, the risks, and the open questions. Then propose a 90-day handoff success plan: objectives, owners, and the first milestones. If a success plan already exists, add to it instead of starting a second one. Do not create or update anything in Gainsight until I approve. If Staircase is connected, use the post-sales conversation. If it is not connected, use only the notes I pasted and say so. If a value is missing, say so. Do not invent numbers.
Build my command center for today across my book. Today's actions: rank the signals and to-dos in one list. For each, say whether a CTA is already in play or nobody is on it, and give the one next step. Churn radar: accounts renewing in the next 90 days, with renewal date, ARR, and health side by side. Top account: for the account at the top, say why it surfaced, who is in the buying group and where each person stands, a suggested next step, and a comparable win from another account if one exists. If Staircase is connected, use it to explain why an account surfaced, and move an account up when recent calls sound worse than the health score. If it is not connected, say so. Do not send email or create, close, or update a CTA until I approve. If a value is missing, say so. Do not invent numbers.
Where are the expansion opportunities across my book? For each account with a signal, put community interest, course completions, usage, and sentiment side by side, and label it a product or services opportunity. Name the source of each signal. For the top account, brief me on health, usage, and stakeholders. If a competitor has come up, show the customer's own adoption data I can use to answer it. For each account, propose one next step: a CTA, an email draft, or a CSQL for the account manager. If Staircase shows what worked for similar accounts, say so. If Staircase is connected, include sentiment and quotes. If it is not connected, say so. Do not create a CTA or a CSQL, or send an email, until I approve. If a value is missing, say so. Do not invent numbers.
List my open CTAs. For each, give the customer, ARR if it is on the account, CTA type, priority, how long it has been open, and days since the last update. Compare them with recent timeline activity. Flag any that look already done, and any with no update for about 60 days. Recommend which to close and which still need action. Do not close, edit, or reassign anything. If Staircase is connected, use what the customer said when deciding whether the work is already done. If it is not connected, say so. If a value is missing, say so. Do not invent numbers.
Show me the risk and expansion radar for my book. If I lead a team, use the team's book. Split ARR into three groups: safe, at risk, and expansion still on the table. Use the health labels and risk CTAs configured in Gainsight, not fixed cutoffs, and say which rule you used. For each group, give the total ARR, the account count, and the accounts that matter most, with the reason. If Staircase is connected, use sentiment and recent conversations, and flag accounts where sentiment disagrees with health. If it is not connected, say so. Do not change anything in Gainsight. If a value is missing, say so. Do not invent numbers.
Build a capacity plan for the CS team from Gainsight. Use these inputs: hours per CSM per week [hours], buffer [percent], and hours per relationship by segment [segment hours]. If one is missing, ask me for it. Do not assume a value. Weight each account's complexity by health, sentiment, and effort signals such as open risk CTAs, and say how you weighted them. Show where the work is: hours, accounts, and CSMs needed by region, against current headcount. Show CSMs needed versus on hand after expected churn and growth, if those are in Gainsight. Recommend books that balance complexity and ARR and keep current owners where possible. Flag any CSM whose renewals stack up in the same quarter. If Staircase is connected, use sentiment in the complexity weight. If it is not connected, say so. Do not reassign anything in Gainsight. If a value is missing, say so. Do not invent numbers.