A one-page account brief in Slack before every call
A rep types the account name and the flow writes a brief from your CRM notes: who you’re meeting, what they bought, what went wrong and what they asked for last time. It posts to your deal channel in Slack.
Sales · Someone asks · 6 steps · Reads your documents · Slack
QuestionQuestion
RetrieveRetrieve
AnswerWrite the digest
For eachFor each recipient
ActionPost to Slack
Answer shownDigest
6 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
Reps prepare for calls by scrolling through months of CRM notes, or they skip it and learn about last quarter’s outage from the customer. The context exists; it just isn’t in front of the rep when it matters.
How it is governed
- Every claim in the brief is cited to a CRM note.
- Retrieval respects each source’s own permissions for the rep asking.
- Testing in the builder describes the Slack post without sending it.
- Each post and each run is kept in the run history.
- Who runs it
- Account executives; Account managers; Sales managers.
- What you supply
- CRM notes as a knowledge source; Slack or email connected.
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Add channels to the recipient list, or post to one rep’s channel; Change the brief’s sections to fit your sales methodology; Add call notes or support summaries as further knowledge sources.
Questions buyers ask
- Does it read our CRM live?
- It reads CRM notes once they are loaded as a knowledge source, not the CRM itself at the moment the rep asks. The brief is as current as that source.
- Where does the brief go?
- To every Slack channel on the recipient list, which starts as your deal-room channel, and back to the rep on screen. A post that fails is recorded and the rest still go out.
- Does anyone approve it before it posts?
- No; it is an internal brief, and the template posts without an approval step. You can add one in the builder if a channel needs it.
Related templates
All 60 templates- RFP answer drafterAnswers a security or procurement questionnaire from what you have already written, with the source for every claim.SalesA document or recording is attached4 steps
- Competitor battlecardAnswers "how do we compare to X" from your own positioning, and refuses to invent a competitor claim.SalesSomeone asks4 steps
- Lead scorerScores an inbound lead against your qualification criteria so the pipeline is ordered by something other than arrival time.SalesA document or recording is attached5 stepsa person approves
- Call notes to actionsTranscribes a call, pulls out what was decided and promised, and has someone check the actions before any are raised.SalesA document or recording is attached5 stepsa person approves
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.