SALES

AE-to-CSM handoff packet from a closed-won Front conversation

When an AE tags a Front conversation as closed-won, this builds a structured handoff packet in Notion from the deal's Salesforce record and emails the assigned CSM a link.

CategorySales
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFront conversation tagged "closed-won"Front
  • ActionRead conversation contacts and messagesFront
  • ActionLook up matching Salesforce OpportunitySalesforce
  • ActionSummarize thread into goals, criteria, risksOpenAI
  • ActionCreate populated Notion handoff pageNotionNotion
  • OutputEmail CSM the packet linkGmailGmail

What it does

Turns a single Front tag into a complete customer-success onboarding packet. It pulls the deal's commercial terms from Salesforce, summarizes the buying conversation from Front, and writes a tidy Notion page the CSM can read in two minutes instead of digging through threads.

When to use it

Run this the moment a deal closes and the account moves from the AE to a CSM. It removes the manual copy-paste handoff doc that AEs hate writing and CSMs never trust.

How it works

  1. 1An AE applies the "closed-won" tag to a conversation in the Front shared inbox, firing the trigger.
  2. 2The flow reads the conversation's contacts and message history from Front to identify the account and the buying committee.
  3. 3It looks up the matching Opportunity in Salesforce to grab ARR, product mix, contract dates, and the owning rep.
  4. 4An LLM step distills the Front thread into stated goals, success criteria, and open risks.
  5. 5A Notion page is created from a handoff template with all fields populated and the source thread linked.
  6. 6The assigned CSM is emailed the Notion link via Gmail with a short summary.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FrontShared inbox, conversations.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Connect GmailRead, draft, send, label.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.