SALES

Draft a tailored objection-rebuttal follow-up email from a Zoom discovery call

After a discovery call, an agent identifies the prospect's top objections and drafts a personalized follow-up email that addresses each one.

CategorySales
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom discovery transcript completedZoomZoom
  • ActionClassify and rank prospect objectionsHugging FaceHugging Face
  • LogicSelect matching rebuttal material
  • ActionAgent composes tailored follow-up email
  • OutputCreate unsent draft in rep's GmailGmailGmail

What it does

This workflow turns the objections raised on a discovery call into a ready-to-send follow-up. An agent reads the transcript, pulls out the prospect's most important objections, and writes a tailored email that addresses each one with the right proof point or reframe, then drafts it in the rep's Gmail for a quick human review before sending.

When to use it

Use it when reps lose deals to slow or generic follow-ups. It works best for teams that want every post-call email to directly answer the concerns a prospect actually voiced, while keeping a human in the loop on the final send.

How it works

The flow triggers on a completed Zoom transcript. An agent classifies and ranks the objections, then pulls matching rebuttal material from your approved messaging library. It composes a personalized email referencing the prospect's own words and the relevant proof points. The draft, with the objection list attached as context, is created in the rep's Gmail as an unsent draft so they can edit and send it themselves.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.