Pre-call account brief
A 400-word brief on where an account stands the moment before you dial in.
- Best for
- Before every external call
- Primitives
- AccountsInteractionsCommitmentsSentiment
- Token savings
- 58%
The prompt
You are preparing a colleague for a sales call with {{account_name}}. Using Sentra: 1. Fetch the Account entity for {{account_name}} — open opportunities, current stage, contract dates, owner. 2. Pull the last 8 weeks of Interactions with anyone at this account — meetings, threads, emails. Surface any moment Sentra flagged with negative sentiment, escalation, or unusual silence. 3. List open Commitments where the account is on either side. Include owner, due date, and current status. 4. For each named contact at this account, return their last-known stance on pricing, competitors, and timeline if Sentra has extracted one. 5. Pull the three most recent internal Decisions about this account and the Rationale attached to each. Output a single brief, no longer than 400 words: - One paragraph: where the account stands today. - Three bullets: what's open from our side (commitment · owner · due date). - Three bullets: talking points for the call, each grounded in a Sentra citation. - One line: any landmine to avoid (recent negative moment, unresolved escalation).
See it work
Run it from
How it runs
- 01Copy the prompt into any agent connected to Sentra over MCP.
- 02The agent reads the company memory, scoped to what you are allowed to see.
- 03One grounded answer comes back, with every line traceable to its source.
Or automate it with Actions
The same prompt runs as a Sentra Action: on a schedule, or on a semantic trigger. Output lands in Slack or email, and every send waits for your approval.
Trigger idea: before every external call
Solara · pre-call brief
Where the account stands
CRM + meeting · Sep 2Solara is mid-renewal at $180k ARR, stage 4 of 5, contract ends Oct 31. Tomas Rivera took over procurement in August; Ananya Rao is still the champion.
Open from our side
commitmentsSSO audit logs promised for Sep 12 (Priya, on track). Revised order form owed since Tuesday (Naomi, overdue). Sandbox extension approved internally but never sent.
Talking points
call · Aug 28 · 00:14:32Lead with the audit-log delivery date. Tomas pushed back twice on per-seat pricing and responds to the usage framing. Ananya asked for a migration plan on the Aug 28 call.
Landmine
support thread · Jul 22A P1 ticket sat unanswered for four days in July; Sofia apologized on the Aug 5 call. Do not reopen it unprompted.
The prompt above becomes this. Fictional data, real mechanics: every line cites the meeting, thread, or record it came from.
Without Sentra
- 01Search the CRM for the account. Pull the deal record, contact list, opportunity history — and re-parse the raw fields.
- 02Search Gmail for the account's domain. Skim 60+ thread excerpts to find which are material.
- 03Search Slack for the account name. Sift internal threads, strip out casual mentions.
- 04Search meeting transcripts for any session attended by account contacts. Re-read each one.
- 05For every named contact, re-read their recent emails to infer their stance on pricing, competitors, timeline.
- 06Re-scan internal decision threads. Try to identify what we decided about this account and why.
- 07Stitch every fragment together. Deduplicate the same fact discovered in three different places.
~120,000 tokens
With Sentra
- 01Pull the `Account` entity. Sentra returns stage, contract dates, contacts, open opportunities — already joined.
- 02Pull the last 8 weeks of `Interactions`, pre-filtered to the moments Sentra flagged as material.
- 03Pull open `Commitments` scoped to the account, typed with owner and due date.
- 04Pull each `Actor`'s last-known stance on pricing, competitors, and timeline — already extracted.
- 05Pull recent `Decisions` about the account with `Rationale` attached.
- 06Compose the 400-word brief from the typed responses.
~50,000 tokens