Ask Plum to draft a deal from its notes, suggest what to do next, write a delivery handoff brief, or draft a renewal or expansion follow-up. Each one is a suggestion: nothing changes until you accept it.
Anyone who works accounts can ask and decide. Viewers see suggestions but can't ask for them or decide on them. Needs your workspace's Anthropic key, connected under AI on Integrations.
Plum only asks Claude when you select a button. It never drafts anything on its own. Each answer appears as a suggestion with Accept and Reject. Accepting makes the change the same way you would by hand, in your name, so the change history shows you made it. Rejecting changes nothing. Asking again replaces a suggestion nobody has decided on yet.
Draft from notes
On a deal in an open stage, under Offers. Plum reads the deal's recent activity (notes, logged calls, captured meetings and emails, and transcripts if your workspace keeps them), the offers already on it, and your offer library. Claude proposes offers to add, each with how many, any agreed price or discount, and a quote from the notes that supports it, plus an expected close date and next step.
- Only offers in your library can be suggested. Anything else the notes mention is listed separately, and any line Claude got wrong is left out with the reason.
- Before you accept, you see each line with its price. Untick anything you don't want, and change the close date or next step.
- Accepting adds each line exactly as Add offer does, priced from the library, and the deal's value follows.
What should I do next?
On a deal's Up next. Plum reads the stage and what it is for, its checklist and how to meet each item, the stage's plays and which have been logged, recent activity, how long since anyone touched the deal, and the expected close. Claude recommends one action, with why, and a drafted email or call agenda when it helps. Accepting adds it as a task on the deal, with the title and due date you choose. A drafted email has a Copy button; Plum never sends it.
Handoff brief
On a won deal once what was bought has been recorded, and on the license or item it became. Plum reads the deal's history: activity, how they buy, documents (titles and status only), the offers sold, and what the customer now owns with its delivery steps. Claude writes a brief with the customer's context, what was sold, promises made, risks, who's who and open questions. Accepting saves it, after any edits, as a note called Handoff brief on the deal and its account.
Renewals and room to grow
On Priorities, beside an account with a license ending or a seat true-up due, and under Room to grow for customers without an offer that customers like them commonly add. Plum reads the account, its licenses and what it owns, its contacts (names and titles; whether each has an email address, not the address), open deals and recent activity. Claude recommends an action, drafts an email to the best contact and suggests a task.
- Accepting adds the task for you.
- If Claude suggests opening a renewal or expansion deal, it is only opened if you tick the box. It is created as a deal on the pipeline would be: yours, in the first open stage.
What Claude sees, and what it can't do
Only what you can see in Plum, gathered as you, and only what the suggestion needs. Text in notes and emails is treated as information, never as instructions: if a note says to change a price or ignore the rules, Claude doesn't. Every answer is checked before it is shown, and again when you accept it.
Claude can be wrong. Read a suggestion before accepting it, especially an amount, a quantity or a date.
Owners and admins see how many suggestions of each kind were accepted and rejected over the last 30 and 90 days, under AI on Integrations.