Example prompt
Copy this into Claude once it is connected to Klipy:What happens
1
Claude reads the meeting
Claude calls
get_meeting_transcript to read the transcript and the meeting’s participant summary, so the follow-up is built on the real conversation — not your memory of it.2
It checks the wider history
Claude calls
search_interactions to pull related email and meeting context for the same contact, so the draft picks up threads from before this one call.3
It prepares a draft
Claude calls
draft_email_message to create a suggested email. This does not send anything — the draft waits in Klipy for your review.4
You review and send
Open the draft, edit anything you want, then approve it through Klipy’s gated send handshake. Sending only happens when you confirm.
Good to know
- A connected email account is required.
draft_email_messageneeds a mailbox connected to Klipy. Without one, it returns a blocked status with guidance instead of a draft. Connect email and calendar first. - The recipient must already be a contact. The first
toaddress has to match an existing CRM contact. If the person from the call is not in your CRM yet, add them first. - Transcripts come from recorded meetings. If the call was not recorded by Klipy’s notetaker, there is no transcript to ground the draft — Claude can still work from email history via
search_interactions.
Related
Meeting recaps
Turn the same meeting into a structured recap and next steps.
Cold deal outreach
Re-engage deals that went quiet, one personal note at a time.
Tool reference
Every tool Claude can call, grouped by scope.