Things to ask Claude using HookDoc reactions

오늘 답장할 제안서, 남은 질문, 제안서 수정 포인트를 상황별로 Claude 에서 바로 물어볼 수 있는 질문 예시입니다.

Most-used questions

  • “Tell me which proposals I should reply to today.”
  • “Group the open questions by pricing, timeline, and scope.”
  • “Draft a reply to this question.”
  • “Update the PowerPoint proposal.”
  • “Update the Word reply and the scope document.”
  • “Put today's proposals into an Excel table.”

All prompts

47 prompts total
  • A0Daily routine🟢 Use today🎯 Occasionally

    Confirm first connection

    When to use
    Right after connecting the HookDoc connector — when you do not yet know what to do.
    HookDoc data needed
    Works with 0 proposals (menu-style); becomes actionable with 1+.
    Prompt body
    Check whether the HookDoc connector is connected properly and recommend the 3 most valuable things I can try right now.
  • A1Daily routine🟢 Use today🔁 Often

    See proposals waiting for a reply at a glance

    When to use
    Start of the day — which proposals need a reply today.
    HookDoc data needed
    1+ proposal with 1+ unanswered comment.
    Prompt body
    Show me which of my HookDoc proposals need a reply, with priority and evidence.
  • A2Daily routine🟡 Within a week🎯 Occasionally

    Stuck-reviewer priority

    When to use
    When you have multiple reviewers and it is unclear who to reply to first.
    HookDoc data needed
    2+ reviewers with unanswered comments.
    Prompt body
    Group proposals with unanswered comments in the last 24 hours by reviewer, and tell me who to reply to first with evidence.
  • A3Daily routine🟢 Use today🔁 Often

    Today's new activity

    When to use
    When you just want to check the new signals from today.
    HookDoc data needed
    1+ new comment or new viewer today.
    Prompt body
    Check whether any proposals received new comments or new viewers today, and surface only the signals that need an immediate response.
  • B1Reply drafting🟡 Within a week🎯 Occasionally

    Gmail follow-up draft

    When to use
    When you want to review a time-sensitive follow-up draft inside Gmail before sending.
    HookDoc data needed
    Requires Gmail to be connected separately.
    Prompt body
    Find the proposal in HookDoc that most needs a reply, look up the recent thread in Gmail, and create a follow-up draft in Gmail for me to review. Stop at draft — do not send.
  • B2Reply drafting🟢 Use today🔁 Often

    Polite, standard-tone reply draft

    When to use
    When you want to reply to a reviewer in a polite, standard tone.
    HookDoc data needed
    1+ unanswered comment.
    Prompt body
    Draft a polite, standard-tone reply to the unanswered questions on [proposal name]. Keep pricing and timeline language non-committal.
  • B3Reply drafting🟢 Use today🔁 Often

    Concise, practical-tone reply draft

    When to use
    When you need a short reply for a quick response.
    HookDoc data needed
    1+ unanswered comment.
    Prompt body
    Draft a concise, practical-tone reply (3–5 lines) to the unanswered questions on [proposal name] for a quick response.
  • B4Reply drafting🟢 Use today🔁 Often

    Safe pricing / scope reply

    When to use
    When answering questions about pricing, timeline, or scope in a safe tone.
    HookDoc data needed
    1+ comment containing pricing or scope keywords.
    Prompt body
    Draft a safe reply for unanswered questions about pricing, timeline, or scope. Use [needs confirmation] / [example] labels and avoid absolute language like "unlimited", "all", or "must".
  • B5Reply drafting🟢 Use today🔁 Often

    Ask back on ambiguous questions

    When to use
    When the reviewer's intent is unclear.
    HookDoc data needed
    1+ ambiguous comment.
    Prompt body
    For unanswered comments whose intent is unclear (e.g. "please confirm"), draft a reply that asks back what specifically should be confirmed.
  • B6Reply drafting🟢 Use today🔁 Often

    Check reply for risky language

    When to use
    Before sending a draft reply, check it for absolute or overstated language.
    HookDoc data needed
    You have a draft reply on hand; 1+ HookDoc record lets the policy context be cited.
    Prompt body
    Find any absolute, definitive, or overstated language in my draft [paste] (unlimited / must / all / 100% / immediately / guaranteed, etc.) and rewrite it in safer language, with the reason for each change.
  • B7Reply drafting🟡 Within a week🔁 Often

    Classify: needs reply / clarify intent / no reply needed

    When to use
    When multiple unanswered comments have piled up and you want to triage them.
    HookDoc data needed
    3+ unanswered comments.
    Prompt body
    Sort my unanswered comments into (a) needs reply now (b) needs intent clarified (c) no reply needed / just a note, and rank within each group. Include the reasoning.
  • B8Reply drafting🟢 Use today🎯 Occasionally

    Pre-flight risk check before sending

    When to use
    Self-check on a proposal, scope document, or reply right before sending to a client.
    HookDoc data needed
    1+ HookDoc record plus 1 piece of outgoing material from you.
    Prompt body
    In what I'm about to send [proposal / scope-document draft / reply draft, pasted], find (a) absolute or overstated pricing, scope, or timeline language (b) sections to soften with [needs confirmation] / [example] labels (c) comparisons with areas that have repeatedly stalled in similar proposals — list pre-send risks, omissions, and structural weaknesses by item.
  • C1Proposal diagnosis🟡 Within a week🎯 Occasionally

    Diagnose why a proposal is stuck

    When to use
    When a specific proposal stalls and you want an evidence-based diagnosis.
    HookDoc data needed
    1+ proposal with some accumulated signals (long-dwell pages, downloads, comments).
    Prompt body
    Diagnose why my [proposal name] stalled using reviewer signals (page dwell, downloads, comments, revisits), and tell me what to do next.
  • C2Proposal diagnosis🟡 Within a week📈 After accumulation

    Identify hot pages

    When to use
    Summarize where reviewers linger and where they drop off.
    HookDoc data needed
    30+ page-enter events recommended.
    Prompt body
    Summarize the pages reviewers lingered on the longest and the pages they left fastest in the last 30 days, and separate which pages are interest signals and which are stuck signals.
  • C3Proposal diagnosis🟡 Within a week🎯 Occasionally

    Silence-after-download diagnosis

    When to use
    Track proposals that were downloaded but had no follow-up reaction.
    HookDoc data needed
    1+ download with a 7-day silence pattern.
    Prompt body
    Find proposals that were downloaded but have been silent (no comments, no replies) for 7+ days, and estimate the likely cause for each (pricing review / internal share / loss of interest) with signal evidence.
  • C4Proposal diagnosis🟠 After data accumulates📈 After accumulation

    Cold-proposal next-action decision

    When to use
    Decide how to handle cold proposals with zero views.
    HookDoc data needed
    2+ cold proposals accumulated.
    Prompt body
    List cold proposals with zero views in the last 7 days and recommend, for each, which action fits best: (a) one more follow-up email, (b) reach a different decision-maker, or (c) drop it.
  • D1Next version🟢 Use today🎯 Occasionally

    Generate PowerPoint revision copy

    When to use
    Claude prepares the revision copy and table layouts for the next version of the slides.
    HookDoc data needed
    1+ unanswered question plus page-reaction data.
    Prompt body
    Based on HookDoc reactions, identify what to fix in the next-version PowerPoint slides of this proposal, and produce revision copy and table layouts ready to apply directly through Claude's PowerPoint feature. Organize as slide number · reviewer-reaction evidence · revised copy · table layout.
  • D2Next version🟠 After data accumulates📈 After accumulation

    Top stuck pages across proposals

    When to use
    Find pages that repeatedly stall reviewers across all proposals.
    HookDoc data needed
    5+ proposals accumulated.
    Prompt body
    Across all my proposals, identify the top-5 pages where reviewers most often get stuck, and suggest how to fix each in the next version.
  • D3Next version🟠 After data accumulates📈 After accumulation

    Recurring questions → root-cause fix

    When to use
    Fix pages where the same question keeps coming from different reviewers.
    HookDoc data needed
    5+ proposals with 10+ questions.
    Prompt body
    Find pages where the same question recurs across proposals, and suggest how to rebuild that page in the next version so the question stops coming up (add an FAQ, restructure the table, add examples).
  • D4Next version🟡 Within a week🎯 Occasionally

    Recommend supplementary assets

    When to use
    Decide which supporting assets (pricing sheet, FAQ, case study) to attach to the next version.
    HookDoc data needed
    5+ questions (enough to classify).
    Prompt body
    Looking at the patterns in unanswered questions on my proposals, recommend supporting assets to attach to the next version (pricing sheet, FAQ, case study, one-page security policy).
  • D5Next version🟡 Within a week🎯 Occasionally

    Reply → next-version improvement points

    When to use
    Find what you keep answering manually so it can be folded into the next version.
    HookDoc data needed
    1 reply with 1 proposal.
    Prompt body
    Looking at the reply I sent to a reviewer (or draft) [paste], suggest where to strengthen the next version of the proposal (which page, what content to add) so I do not have to answer the same thing every time.
  • D6Next version🟢 Use today🎯 Occasionally

    Generate Word reply and scope-document revision copy

    When to use
    Claude rewrites the ambiguous sentences in your Word scope document.
    HookDoc data needed
    1+ unanswered question plus page-reaction data.
    Prompt body
    Based on HookDoc reactions, prepare the revision copy to apply in Word for the next version of this proposal and scope document, plus the spots to mark via tracked changes. Organize as a table: page-or-section · reviewer-reaction evidence · revised copy · tracked-change area.
  • E1Pattern analysis🟡 Within a week📈 After accumulation

    30-day analysis summary

    When to use
    Monthly retro or recurring report.
    HookDoc data needed
    Some activity accumulated over the last 30 days.
    Prompt body
    Summarize the analytics for the last 30 days. Which proposals are stuck, which pages are stalling, and where is data still thin?
  • E2Pattern analysis🟠 After data accumulates📈 After accumulation

    Question-type distribution

    When to use
    Analyze where reviewer interest or concern is concentrated.
    HookDoc data needed
    10+ questions recommended.
    Prompt body
    Classify reviewer questions from the last 30 days into pricing, timeline, scope, legal, and other; if the distribution skews, analyze what that means.
  • E3Pattern analysis🟠 After data accumulates📈 After accumulation

    Reviewer activity time-of-day

    When to use
    Decide when to send follow-up emails.
    HookDoc data needed
    30+ page-enter events recommended.
    Prompt body
    Summarize when reviewers tend to view my proposals (day-of-week, hour) and recommend the time slot most likely to land a follow-up email.
  • E4Pattern analysis🔴 After results accumulate🔒 After results accumulate

    Outcome distribution

    When to use
    Compare won/lost patterns (after outcomes accumulate).
    HookDoc data needed
    After 5+ accepted / rejected outcomes are recorded.
    Prompt body
    Show the outcome distribution (accepted / rejected / blocked / unknown) for the last 30 days of proposals, and tell me whether there are signals (pages, question types, dwell patterns) common to each outcome.
  • F1Collaboration / share🟢 Use today🔁 Often

    One-line internal share summary

    When to use
    When sharing the current state with the team or a co-founder in one line per proposal.
    HookDoc data needed
    1+ proposal.
    Prompt body
    Summarize the current state of my in-flight proposals so I can share with the team. One line per proposal: priority / latest signal / next action.
  • F2Collaboration / share🟡 Within a week🎯 Occasionally

    Sales-team deal status

    When to use
    For use in a weekly sales review.
    HookDoc data needed
    3+ proposals recommended.
    Prompt body
    Lay out all my proposals as a 5-column table (sent-to / outcome / last activity / next action / blocker) suitable for a sales-team weekly review.
  • F3Collaboration / share🟡 Within a week🎯 Occasionally

    Sales meeting agenda

    When to use
    Prepare the agenda for the next 1:1 sales meeting.
    HookDoc data needed
    1+ hot proposal with some comments.
    Prompt body
    Pick the 3 hottest proposals worth covering in my next sales 1:1, and for each lay out where it is stuck right now and what decision I need from the meeting.
  • G1External tool combos🟡 Within a week🎯 Occasionally

    HookDoc + Gmail

    When to use
    A follow-up flow that ends in a Gmail draft.
    HookDoc data needed
    Gmail connected separately.
    Prompt body
    Find the single most urgent proposal in HookDoc, read the latest Gmail thread with that company, and create a Gmail follow-up draft that I just need to review before sending. Do not send.
  • G2External tool combos🟡 Within a week🎯 Occasionally

    Edit PowerPoint slides directly

    When to use
    Claude updates the copy and tables on your PowerPoint proposal slides.
    HookDoc data needed
    PowerPoint file open, with 1+ proposal to revise.
    Prompt body
    Based on HookDoc reactions, pick the slides to fix in the next version of [proposal name], and update the slide copy and tables in the open PowerPoint file. List the changed slides so the user can review them.
  • G3External tool combos🟠 After data accumulates📈 After accumulation

    HookDoc + Calendar

    When to use
    Recommend follow-up meeting times and create tentative calendar slots.
    HookDoc data needed
    Calendar connected, with 30+ events of reviewer time pattern.
    Prompt body
    Based on reviewer activity hours, suggest 3 candidate slots for my next sales follow-up meeting. Create 3 tentative slots in my Calendar — do not send confirmations.
  • G4External tool combos🟡 Within a week📈 After accumulation

    HookDoc + Notion / Linear

    When to use
    Push proposal next-actions into a task system.
    HookDoc data needed
    External tool connected with 3+ proposals.
    Prompt body
    Organize the next actions on my proposals as (deal name / next action / due date / blocker) tasks ready to add to a Notion Sales DB or Linear Sales project. Do not auto-create — I will add them after reviewing.
  • G5External tool combos🟡 Within a week🔁 Often

    Update the Excel pipeline tracker

    When to use
    Claude appends this week’s rows to your ops tracker.
    HookDoc data needed
    Excel file open, with 3+ proposals.
    Prompt body
    Based on HookDoc follow-up priorities and unanswered questions, add this week's rows to the open Excel pipeline tracker. Columns: proposal name · review status · open questions · next action · deadline.
  • H1Recovery / differentiation🟠 After data accumulates📈 After accumulation

    Differentiate similar companies

    When to use
    Compare proposals sent to similar companies and pull meeting talking points.
    HookDoc data needed
    2+ proposals in a similar industry, with manual mapping by the user.
    Prompt body
    If [proposal A] and [proposal B] were sent to different companies in the same industry, compare their differences and tell me which points to emphasize in the next meeting.
  • H2Recovery / differentiation🔴 After results accumulate🔒 After results accumulate

    Lost-deal post-mortem

    When to use
    Analyze common weaknesses of lost deals (after outcomes accumulate).
    HookDoc data needed
    After 5+ rejected / closed_lost outcomes are recorded.
    Prompt body
    Find the common weaknesses (pages, questions, signal patterns) of proposals with rejected / closed_lost outcomes in the last 30 days.
  • H3Recovery / differentiation🔴 After results accumulate🔒 After results accumulate

    Won-deal pattern

    When to use
    Analyze common strengths of won deals.
    HookDoc data needed
    After 5+ accepted / won outcomes are recorded.
    Prompt body
    Find the common strength pattern of proposals with accepted / won outcomes in the last 30 days, and tell me which pages contributed to the win.
  • I1Visuals🟢 Use today🔁 Often

    Proposal-priority kanban

    When to use
    When you want to see follow-up priorities at a glance.
    HookDoc data needed
    1+ proposal.
    Prompt body
    Build the HookDoc follow-up priorities as a 4-column kanban React artifact (Immediate / Today / Wait_24h / Cold). Each card shows proposal title / open question count / last activity / suggested action.
  • I2Visuals🟢 Use today🎯 Occasionally

    Single-proposal evidence table

    When to use
    Visualize page-level signals for one proposal.
    HookDoc data needed
    1 proposal with some signal data.
    Prompt body
    Lay out [proposal name] as a table artifact with per-page dwell time / download count / comment count / last view. Highlight rows that signal stalling (dwell 60s+ or unanswered comments).
  • I3Visuals🟢 Use today🔁 Often

    Reply-draft labeled cards

    When to use
    Review reply drafts visually with labels and a checklist.
    HookDoc data needed
    1+ unanswered question.
    Prompt body
    Build draft replies for the top-3 unanswered questions as a card artifact. Each card shows (1) reviewer question (2) draft reply (3) parts marked with [needs confirmation] / [example] highlighted (4) a pre-send review checklist.
  • I4Visuals🟡 Within a week📈 After accumulation

    Page reaction heatmap

    When to use
    See dwell distribution across proposals × pages at a glance.
    HookDoc data needed
    30+ page-enter events.
    Prompt body
    Build a heatmap artifact of average per-page dwell over the last 30 days. X-axis = page number, Y-axis = proposal, color intensity = dwell seconds. Empty cells (no data) shown in grey.
  • I5Visuals🟡 Within a week📈 After accumulation

    Question-type distribution chart

    When to use
    Visualize the share of reviewer interest areas.
    HookDoc data needed
    5+ classifiable questions.
    Prompt body
    Build a pie-chart artifact classifying reviewer questions from the last 30 days into pricing / timeline / scope / legal / other. Each slice shows percentage and absolute count, with a short ops recommendation for the largest category alongside.
  • I6Visuals🟡 Within a week📈 After accumulation

    30-day activity line chart

    When to use
    Visualize the monthly activity trend.
    HookDoc data needed
    Some activity in the last 30 days.
    Prompt body
    Build a line-chart artifact of the last 30 days, daily, with three metrics (page view / new comment / download) in different colors. Mark spike days and overlay a 7-day moving average.
  • J1Customization🟡 Within a week🎯 Occasionally

    Get a draft of the company reply standard

    When to use
    Standardize reply tone, pricing language, and scope wording into a company standard.
    HookDoc data needed
    1+ HookDoc record plus your company information.
    Prompt body
    Build a draft company standard that unifies my reply tone, pricing language, and scope wording. Reference HookDoc's reply policy (phrases to avoid · situations needing caution).
  • CT1Connection test🟢 Use today🎯 Occasionally

    Connection check — list available tools

    When to use
    Verify the HookDoc MCP connector is reachable from Claude.
    HookDoc data needed
    HookDoc connector added in Claude (URL only).
    Prompt body
    List every HookDoc connector tool name in a table.
  • CT2Connection test🟢 Use today🎯 Occasionally

    Connection check — follow-up priority summary

    When to use
    Verify the primary follow-up tool returns expected data.
    HookDoc data needed
    1+ proposal sent in the last 30 days.
    Prompt body
    List proposals from the last 30 days that need follow-up, ranked by priority.
  • CT3Connection test🟢 Use today🎯 Occasionally

    Connection check — single proposal 4 signals

    When to use
    Verify expansion 4 tools (outcome / AIRFC / unanswered / version mismatch) chain.
    HookDoc data needed
    1 proposal with submitted outcome or completed AIRFC.
    Prompt body
    Pick one proposal needing follow-up and check outcome, AI review document status, unanswered questions, and version mismatch.

← Claude guide hub

Claude and Anthropic are trademarks of Anthropic PBC. HookDoc is not an official Anthropic product and is not endorsed, sponsored, or approved by Anthropic.