Every week, we're going to shine a light on one skill from the Skill Library — a ready-made workflow you can turn on today. First up: Call Follow-Up Email, one of the most requested workflows since we opened this community.

The problem it solves

You just got off a call with a customer. You meant to send a quick follow-up email while it was fresh — a recap, a next step, something to keep the conversation moving. Then the next call started, then a meeting, then it's 5pm and that email never got written.

This skill closes that gap. It turns a call you already had into a drafted, specific follow-up email in seconds — not a generic "great speaking with you today" template, but one that actually references what was discussed.

How it works

Ask for it in plain language: "Draft a follow-up email for my last call with Acme Corp" or "I told a customer I'd send them something after we hung up — can you write that?" You don't need to name RingCentral, mention call history, or specify a tool. The skill figures out the rest:

1. It finds the call. It looks at your recent RingEX call activity and shows you the likely match — with a flag for whether that call has a recording or an AI transcript attached, since that changes what kind of email it can write.
2. It figures out who to email. It checks your contacts for the other person's email address. If nothing has it on file (a common gap today), it'll just ask you directly rather than guessing — it will never invent an email address.
3. It writes a real draft. If a transcript or AI call summary exists, the email references actual topics from the conversation instead of filler. If it doesn't, it says so upfront and gives you a shorter, honest draft instead of pretending otherwise.
4. It finds a way to send it. If you have an email tool connected, it'll offer to send through that. If not, it hands you a complete To/Subject/Body draft to paste into whatever email client you actually use — so you're never stuck just because a specific plugin isn't installed.
5. It always shows you the draft first. Nothing goes out the door without you seeing the full email and giving an explicit yes.

Why we like this one

It's a good example of what these skills are trying to do generally: take something you'd do manually in three or four steps, across two or three tools, and collapse it into one request — while staying honest about what it can and can't find. If there's no transcript, it tells you. If it can't find an email address, it asks instead of guessing. That matters more than looking impressive in a demo.

Try it

This skill runs on the RingEX Phone server. If you've already connected RingCentral to Claude or ChatGPT, just ask for a follow-up email after your next call. If you haven't connected it yet, see Getting Started with Claude and ChatGPT to set that up first.

Built something on top of this skill, or found a gap in how it handles a specific case? Tell us in the comments — spotlights like this one are as much about hearing what's missing as showing what works.