Turn a Slack DM Sales Conversation Into a CRM Update

You are a sales ops analyst who reconstructs sales conversations from Slack threads. You ignore reactions, gifs, and chit-chat, and you focus only on commitments, decisions, blockers, and sentiment shifts.
Agency: [AGENCY_NAME] — [SERVICES]
CRM: [CRM_TOOL]
Client/Prospect: [PROSPECT_NAME] at [PROSPECT_COMPANY]
Relationship: [RELATIONSHIP_TYPE — e.g. "Slack Connect channel with active retainer client" or "DM with prospect from referral"]
Input source: Slack thread (chronological, oldest at top)
Raw thread:
[SLACK_THREAD]
Reconstruct this Slack conversation as a CRM update: what was discussed, what was agreed, what's outstanding, and how the relationship sentiment has shifted.

- Ignore reactions, emoji-only messages, and pure scheduling chit-chat.
- Convert Slack timestamps to plain dates (e.g. "May 21").
- Capture every commitment with owner + due date.
- Note any sentiment shifts (e.g. "tone cooled after May 22" or "warmer after deliverable shipped").
- If the thread contains a pricing/scope discussion, surface it explicitly.
- Output should be paste-ready into a CRM note or deal record.

Slack Conversation Recap — [PROSPECT_COMPANY]

Date range: [first] → [last]
What was discussed (3-5 bullets):
Decisions made:
Commitments (with owner + due):
Open / unresolved:
Pricing or scope changes mentioned:
Sentiment shift: [warmer / neutral / cooler] + 1-sentence why
Recommended CRM action: [e.g. Move deal to Proposal stage; Update renewal probability; Log expansion opportunity]

• [AGENCY_NAME] — Your agency name
• [SERVICES] — Services you sell
• [CRM_TOOL] — HubSpot, Pipedrive, Close, etc.
• [PROSPECT_NAME] — Primary contact name
• [PROSPECT_COMPANY] — Prospect company name
• [RELATIONSHIP_TYPE] — Describe the relationship: prospect DM, Slack Connect channel with active client, etc.
• [SLACK_THREAD] — Paste the Slack thread, oldest at top. Strip reactions/gifs if you want a cleaner result.

Agency: Beam Creative — Webflow + brand design
CRM: HubSpot | Client: Aisha Patel at Loomwear | Relationship: Slack Connect channel with active retainer client
Thread snippet:
May 18 — Aisha: Hey — quick one, our Q3 product line drops Aug 1. Need a microsite for it. Can Beam handle?
May 18 — Jordan: Totally. Let me scope. What's the timeline pressure?
May 20 — Aisha: Live by Jul 25 ideally. Budget around $25k.
May 21 — Jordan: Doable. I'll send a SOW Friday with two options (lite/full).
May 22 — Aisha: Cool. Looping in our CMO Dan and CFO Devon in the SOW thread.
May 24 — Aisha: Hey any update on the SOW? Devon's asking.

Slack Conversation Recap — Loomwear

Date range: May 18 → May 24
What was discussed:
• New scope: Q3 product-line microsite, live by Jul 25
• Budget anchor: $25k
• SOW format: two options (lite/full)
• Stakeholders expanding: CMO Dan + CFO Devon now in approval chain
• Friction emerging: SOW promised Friday, not delivered as of May 24

Decisions made:
• Beam will deliver the microsite (verbal scope agreement)
• Two-tier SOW format agreed

Commitments (with owner + due):
• SOW with two options — Owner: Jordan — Due: Fri May 22 (OVERDUE, 2 days past)
• Approval — Owner: Aisha + Dan + Devon — Due: TBD pending SOW

Open / unresolved:
• SOW not yet sent (urgent — CFO already asking)
• Final pricing not confirmed
• Production timeline not validated against Beam capacity

Pricing or scope changes mentioned: New $25k scope, separate from existing retainer.

Sentiment shift: Cooler — Aisha's May 24 "any update?" + CFO pressure means trust is starting to dip. Recover by sending SOW today with a brief apology.

Recommended CRM action: Create new HubSpot deal "Loomwear — Q3 Microsite — $25k" in Proposal stage; flag overdue SOW task to Jordan; log expansion opportunity tag on parent account.

• Strip reactions and emoji noise before pasting — saves tokens and improves recall.
• For active Slack Connect channels with retainers, run this weekly as a Monday-morning standup feeder.
• Use a separate prompt run for each distinct topic in long channels — one thread, one CRM update, otherwise the model blends scope discussions together.