Pi works best with concrete prompts that name the customer, the timeframe, or the artifact you want. Vague prompts get vague answers. The ones below are real prompts in use across CSM teams. Save any of them as a quick prompt from the composer (the bookmark icon next to the send button).
Prompt: “Catch me up on Acme since my last comment.” Good for Monday morning when you’ve been off a customer for a week.
Prompt: “Summarize the last 30 days for customer #42 in five bullets.” Good for handoffs and account reviews.
Prompt: “Who at Globex hasn’t responded in 7 days?” Good for finding stalled threads before a status meeting.
Prompt: “What changed across my customers since yesterday?” Good for the first five minutes of the day.
Prompt: “Which of my onboardings are likely to slip past their target launch?” Good for Friday triage. Pulls from Forecast launches.
Prompt: “List every customer-facing task due this week, grouped by customer.” Good for scoping a week before standup.
Prompt: “Draft a check-in email to every primary contact in UAT this week. Keep it under 80 words.” Good for batch outreach. Pi uses your voice profile.
Prompt: “Write a comment on Acme’s onboarding flagging the integration test failure from yesterday.” Good for closing the loop after a Slack thread.
Prompt: “Draft an apology to the primary contact at customer #88 for missing the kickoff.” Good when you need to set tone but don’t want to start from a blank page.
Prompt: “Why is Acme flagged at-risk?” Good for prepping a save call. Returns the signals Pi used.
Prompt: “Forecast launch for Globex with the contributing factors.” Good for putting numbers behind a gut feel.
Prompt: “Compare Acme’s onboarding velocity to similar customers.” Good for executive updates.
#42) or domain (acme.com) when more than one match is possible.Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.