We only use cookies to enhance your experience. No cross-site tracking, no ads. Read our Cookie Policy.
Show how it's done on screen and talk through the whole process.
Give it the supercut link. It reads the transcript and frames.
Your agent writes it into Intercom, ready for you to send.
The fastest way to answer a how-to support ticket is to record the answer in Supercut and tell your agent to draft the reply from it. It pulls the transcript and the frames, and drafts the reply in the conversation, ready for you to send.
Connected to your agent.
Connected to your agent.
Claude, Cursor, or similar.
A customer asks something that is faster to show than to write. Hit record, do the thing on screen, and narrate it. Include:
Open by naming the issue they ran into, then show how you solve it.
Where to click, in order, from where they actually start.
Show the working state, so they know what success looks like.
Anything that changes the steps: plan, permission, browser.
Give your agent the Intercom conversation and the supercut link. It reads what the customer asked and everything already said in the thread, then pulls the transcript and frames from the recording. It writes the reply in the customer's context, not as a generic walkthrough.
Your agent writes the reply as an internal note on the conversation, following the steps you went through in the supercut. It can link the recording too, so they can watch it instead of reading. You read it, edit anything that is off, and send it yourself.
Some answers are already on video. Keep the approved ones in one Supercut playlist, then point your agent at the playlist instead of recording again. It finds the answer, reads the transcript, and drafts the reply from it. Nobody records the same answer twice.
Paste this to your agent. Swap [CONVERSATION] for the Intercom conversation URL or ID, and [RECORDING] for the supercut link, or the entire Supercut playlist where you store all the canned responses.
Draft a support reply for Intercom conversation [CONVERSATION], using [RECORDING] as the answer. [RECORDING] is either one Supercut recording or a Supercut playlist.
1. Read the conversation first. Note what the customer asked, what they have already tried, and anything about their plan or setup that changes the answer.
2. If [RECORDING] is a playlist, find the recording in it that answers the question. Read that recording's transcript and pull the frames that show each step.
3. Write the reply: answer the question first, then the steps in the order the recording shows them, then link the recording so they can watch it instead of reading.
4. Add the reply to the conversation as an internal note. Do not send it to the customer.
Rules:
- Only describe steps that appear in the recording. If the customer asked something it does not cover, say so at the top of the note instead of filling the gap.
- Do not invent plan limits, pricing or timelines. If the conversation does not say, ask me.Your agent can only work with what the recording and the conversation gave it. The answers it writes are as good as the context you give it in the supercut.
Record the thing once, hand it to your agent, and the answer writes itself in Intercom. The explanation you would have typed out, and then typed out again for the next person, is on video instead.
If the answer has been recorded before, nobody needs to record it again. Your agent pulls that video through the MCP and writes the reply from it. The canned responses your team reaches for become videos.
This is one of several things your agent can do across the two tools.
Record the bug happening. Your agent gets the transcript and frames, and the Linear ticket writes itself.
Explain how it should work, once. Your agent writes the stories your developers need to build it.
Point your agent to your PM's feature demo video, and it writes the help center article, screenshots included.
Put what your team records into a shared playlist. Then anyone can ask it a question and get an answer back.
Record yourself doing the work once. Your agent picks it up and writes the documentation directly in your database.
Record your update. Your agent posts the summary, the action items, and links to the moments that matter.
One prompt fetches every comment on your recording and gives you the summary and the actions in one go.