Create a Confluence customer page when a deal closes

<context>
A deal just closed. I want to create a permanent customer page in our Confluence space — not just an internal Slack post, but a structured knowledge page that CS, implementation, and account management can reference and update throughout the customer's lifetime. It should capture everything from the sales process so CS doesn't have to ask the AE for context.

The deal:
- Customer company: [COMPANY NAME]
- ACV: [DOLLAR AMOUNT]
- Contract start date: [DATE]
- Confluence space: [SPACE KEY OR NAME — e.g. "CS" or "Customers"]
- Parent page: [PAGE TITLE OR "create at top level of space"]
- AE who closed: [AE NAME]
- CS owner: [CS NAME]
- Primary contact: [NAME AND TITLE]
</context>

<task>
1. Use Lusha to validate and map all contacts at this account:
   - Primary contact: confirmed title, verified email, direct phone
   - Any other contacts from the sales process
   - Any account signal detected in the last 30 days

2. Search Gmail for the full sales thread with this account:
   - What problem did the customer describe in their own words?
   - What was promised during the sales process — integrations, onboarding, timelines, intros?
   - Any unresolved concern or objection before close?
   - Competitor mentioned during evaluation?
   - Stated reason for choosing us?

3. Create a Confluence page in the specified space with this structure:

   # [Company Name] — Customer Page
   ACV · CS Owner · AE · Contract start · Created: [date]

   ## The Problem in the Customer's Words
   Direct quote from the sales thread — not a paraphrase

   ## Key Contacts
   Verified contacts with title, email, phone, and role in the relationship

   ## What Was Promised
   Every commitment made during the sales process — specific, actionable, owned

   ## Open Concerns at Close
   Any objection or concern not fully resolved — CS should address early

   ## Competitor Evaluated
   Any alternative the customer considered

   ## Why the Customer Chose Us
   Stated reason from the sales thread

   ## Account Signals
   Any Lusha signal suggesting expansion potential or risk

   ## Relationship History
   Key dates and milestones — first contact, discovery, proposal, close

   ## Notes
   [Empty — for CS to add ongoing notes]

4. Return confirmation the page was created with the Confluence link.
</task>

<constraints>
- The customer's problem statement must use the customer's own words from Gmail — not a summary.
- What Was Promised is a checklist CS owns from day one — every item must be specific.
- If Gmail shows no thread: flag it — the AE must provide context before CS starts.
- The Notes section must be left empty — it's for CS to fill in, not to pre-populate.
</constraints>

The situation: Ashford Platforms closes at $95K ACV. The AE runs the prompt immediately after marking the deal closed-won.

Confluence page created in CS space (Confluence link returned on live run)

Ashford Platforms — Customer Page

$95K ACV · CS Owner: Marcus · AE: Sarah · Contract start: June 1, 2026 · Created: May 28, 2026

The Problem in the Customer’s Words

From D.R.’s email, May 7 discovery call:

“New SDRs are taking 6+ weeks to ramp because they’re building lists manually. We need the data layer to already exist when a new hire starts. If that problem is solved, everything else downstream gets easier.”

Key Contacts

What Was Promised

• ☐ Native HubSpot connector — confirmed on May 21 call · CS owns
• ☐ HubSpot connector documentation — promised at onboarding · CS owns · Due: June 7
• ☐ Solutions engineer intro for technical setup — agreed May 14 · AE to schedule · Due: June 9
• ☐ SDR onboarding case study from similar-stage SaaS company — promised May 18 · AE to send · ⚠ Overdue

Open Concerns at Close

Z***I*** was evaluated in parallel. D.R. raised data coverage concerns — not fully resolved before close. M.L. was the comparison driver. Address in first CS call: “What were the specific coverage gaps you saw with Z***I*** — let’s map those against what we have.”

Competitor Evaluated

Z***I*** — evaluated in parallel. Customer chose Lusha on data quality and ease of use per D.R. D.R. was the coverage question raiser; M.L. drove the head-to-head comparison.

Why the Customer Chose Us

From D.R.: “The SDR adoption story was the deciding factor — your interface is something an SDR actually uses on day one, not something they need training for.”

Account Signals

Sales headcount up 34% in last 60 days — 8 open AE and SDR roles. Current contract covers existing team. Expansion conversation natural at 90 days.

Relationship History

• April 22: First outbound email from Sarah — cold outreach, D.R. replied same day
• May 3: First discovery call — D.R. and M.L., 45 minutes
• May 14: Second discovery call — Z***I*** comparison raised
• May 21: HubSpot integration confirmed
• May 27: Proposal sent
• May 28: Closed-won · $95K ACV

Notes

[Empty — CS to add ongoing notes here]

Illustrative example — fictional company names used. Run with your own deal data to see live results.