Search Confluence for internal knowledge before reaching out

<context>
Before I reach out to a prospect for the first time — or before a first call — I want to search our internal Confluence knowledge base to see whether there's any relevant documentation, integration guide, competitive intel, or product context that directly applies to this company's use case. I want to go into the conversation knowing what our own knowledge base says about their situation.

My prospect:
- Company: [COMPANY NAME]
- Industry / use case: [INDUSTRY OR SPECIFIC USE CASE — e.g. "mid-market SaaS SDR ramp" or "enterprise RevOps"]
- What I sell: [PRODUCT / SOLUTION]
- Tech stack (if known): [TOOLS THEY USE — or "unknown"]
- Call type: [FIRST CALL / RE-ENGAGEMENT / DEMO]
</context>

<task>
1. Search Confluence for any page that is relevant to this prospect's context:
   - Search by industry, use case, company size, or tech stack keywords
   - Look for: integration guides, use case documentation, customer stories (anonymised),
     competitive positioning pages, onboarding templates
   - Return: page title, Confluence link, one sentence on why it's relevant

2. Use Lusha to validate the primary contact and check for account signals:
   - Confirm the right contact — current title, verified at company
   - Any signal in the last 30 days worth referencing on the call?

3. Build a pre-call Confluence brief:

   PROSPECT: [company] · [contact verified]
   ACCOUNT SIGNAL: [Lusha finding or "none detected"]

   RELEVANT CONFLUENCE PAGES:
   For each: title, link, why it matters for this specific prospect

   TALKING POINTS FROM CONFLUENCE:
   2–3 specific points from the content directly relevant to this prospect's use case
   — not generic product claims

   KNOWLEDGE GAPS:
   Any area where Confluence has no relevant content — so the rep knows what
   to research elsewhere before the call

4. If no relevant Confluence content found: flag it and suggest what page should exist.
</task>

<constraints>
- Talking points must come from actual Confluence content — don't generate generic claims.
- Knowledge gaps are useful output — don't skip them.
- The Atlassian connection covers both Jira and Confluence — one connection, both tools.
- If a page is only tangentially relevant: note it but don't include it in talking points.
</constraints>

The situation: An SDR is preparing a first call with Dunmore Analytics — a 580-person SaaS company, VP of Sales, Series B just closed. Known tech stack: HubSpot, Outreach. Running the Confluence search before dialling.

Pre-call Confluence brief — Dunmore Analytics

PROSPECT: Dunmore Analytics · T.K., VP of Sales ✓ confirmed at company ACCOUNT SIGNAL: Series B funding confirmed 18 days ago — new budget and headcount targets expected

RELEVANT CONFLUENCE PAGES

TALKING POINTS FROM CONFLUENCE

1. From the Mid-Market SaaS SDR Ramp page: “Companies at your growth stage typically see SDR ramp time double between Series A and Series B headcount targets — the data quality problem gets worse as the team grows, not better. The integration with HubSpot means new hires have verified data from day one.”
2. From the Series B Playbook: “The post-funding window is typically 4–6 weeks before headcount planning locks in. The teams that build the data layer before the hiring surge get faster ramp times — the ones that build it after are playing catch-up.”
3. From the HubSpot Integration Guide: “The HubSpot integration is native — no workaround, no API setup required. Most teams are live within 48 hours of starting the configuration.”

KNOWLEDGE GAPS

No Confluence page found for: Outreach + HubSpot combined stack use case. If T.K. asks how the product works alongside both tools simultaneously, the rep will need to check with a solutions engineer before the call — no internal documentation covers this combination.

Illustrative example — fictional company names used. Run with your own Confluence space and prospect data to see live results.