How to Ask Claude Which Deals Are Hot
Dashboards answer the questions you ask them, one document at a time. But the morning question isn't about one document — it's “across everything I've sent, where should my attention go first?” Answering that by hand means opening every analytics tab and doing the triage yourself.
With your Apdf workspace connected to Claude over MCP, the triage is the agent's job: it sweeps the sessions on every tracked document, weighs the signals — re-opens beat deep reads beat skims — and hands you a call list with reasons attached.
Prerequisite: a connected workspace
One OAuth sign-in connects Claude Desktop or Claude Code to your workspace — the setup tutorial walks through it. In Claude Code it's:
claude mcp add --transport http apdf https://apdf.io/mcp/mainAsk the triage question
1. Familie Arslan re-opened the Lindenstraße exposé two days after their first read — and this time went straight to the floor plan (95s) and the price page (2m). Re-open + money page = call today.
2. Sandra Okafor read the July investor update cover to cover for 3m 51s — her third straight update, and her deepest.
3. Alex Moreau stalled on the Q3 proposal's pricing page. Worth a look before you call — want the session detail?
The ranking logic is the agent's, and it's sound because the data is explicit: every session carries who, which pages, and for how long — so “came back and camped on the price page” is arithmetic, not vibes.
Drill into one signal before you dial
{
"recipient": {
"name": "Alex Moreau",
"email": "alex@clientco.example"
},
"metrics": {
"total_duration_ms": 59000,
"pages_viewed": 2,
"total_pages": 3,
"completion_pct": 67,
"downloads": 0,
"prints": 0
},
"pages": [
{ "page": 1, "views": 1, "duration_ms": 12000, "viewed": true },
{ "page": 2, "views": 0, "duration_ms": 0, "viewed": false },
{ "page": 3, "views": 1, "duration_ms": 47000, "viewed": true }
]
}Now the call opens with the right sentence — something about payment options, nothing about “did you get a chance to look at it?”
Decide what stays conversational
The question-answer loop shines for triage and one-off digging — but signals you check every day deserve standing infrastructure. The split that works:
- Ask Claude for the cross-document sweep, the “why is this account quiet?” dig, the pre-call briefing.
- Wire an automation for the moments that can't wait a question — the re-open alert and the pricing-stall trigger.
- Schedule the digest so the whole team sees yesterday's reading without anyone asking — the daily digest is one cron away.
Where to go from here
Three builds that pair naturally with the conversational layer.
Related tutorials
Build a Morning Briefing Agent for Your Documents
A digest lists what happened; a briefing arrives with the thinking done. One standing prompt over the MCP-connected workspace and Claude sweeps every document's sessions on a headless cron — call-first with evidence and a suggested opener, the next tier in one line each, and the silence flagged.
Connect Claude Desktop to Your Document Workspace
One OAuth sign-in and your tracked documents become something you ask: 'who read the July update?' comes back with names, pages and minutes; 'share the pricing guide with Elif' mints her tracked link — no dashboard trip, no API keys, and the same conversation can transform the PDF itself.
Mint PDF Tracking Links from ChatGPT
The share decision happens mid-conversation, not in a dashboard tab. The MCP server speaks to any client — including ChatGPT — so 'share the pricing guide with Elif' mints her tracked link inside the draft you were writing, and the same chat checks who read and kills a leaver's old link.