Limitations
What Pi gets wrong, what it refuses to do, and how to work around the gaps.
Pi is a drafting and summarizing assistant. It’s good at the work humans hate (reading a long thread, comparing 30 customers, writing a first draft) and weaker at work that needs precision (counting, citing a number, anything outside Pivotal’s data). The honest list is below so you know when to trust the answer.
Every action lands in your composer as a draft. You confirm. Pi does not have a write path to your records.
Pi reads tables but is not a calculator. Numeric claims (“Acme has 17 open tasks”) are usually right and sometimes off by one or two. Treat numbers as a starting point and click through to the source view if you’re going to act on the figure.
Pi reads up to the most recent 500 events per customer. Customers older than 18 months can have history Pi summarizes incompletely. Ask for sources and you’ll see which window Pi used. For full history, open the customer and use the Customer history tab.
Pi only reads Pivotal’s database. Slack threads Pivotal hasn’t synced, HubSpot fields you haven’t mapped, Stripe invoices you haven’t connected. Pi can’t see them. If a prompt depends on data from a connected system, check Field mapping and confirm the sync is current.
Records created in the last few minutes can lag the data Pi reads from. If you just added a customer and Pi says “I can’t find Acme”, wait two minutes and ask again. The indexer catches up on a short interval.
Pi’s forecast model needs at least four closed tasks to reach high confidence. New onboardings show Confidence: Low on the chip. Read the slippage as directional, not precise, until confidence climbs.
help@pivotal.app with the prompt and what you expected.Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.