ClaudeEach reusable support answer

Turn a documented fix into a support video in Claude

Give Claude your help article and the question customers keep asking. Review ngram’s plan, check the troubleshooting steps and add the finished video to your support answer.

See what you can make

A support explanation created through Claude from ngram’s published recovery guide. The diagram separates plan review, a pending question, active production and error recovery.

Prompt

Use the connected ngram tools to prepare a support video for ngram users who are unsure why a video is waiting for input. Base the explanation on this published help article: https://help.ngram.com/en/articles/6454925-understand-generation-status-retries-and-recovery Source facts to explain: - Reopen the same conversation and read its last message. - If a plan is waiting, review it and choose Request changes or Approve plan. - If ngram asks a question, answer in the same conversation. - Active production can take time. Keep the existing project while checking its status. - If an error appears, read its recovery message before retrying. - If one careful retry does not resolve the failure, contact Support with the conversation link and the action that failed. Create a 45-second, 16:9 Blueprint video with English narration. Use a labeled decision diagram for plan review, a question, active production and an error. Present the documented controls as text labels within the diagram. Use only these source facts. Keep narration under 100 words. Explain the expected result as continuing the same conversation after the needed input is supplied. End with the documented support escalation. Use diagrams and text, with no invented product screen. Show selected settings and the total estimate before creation. After I confirm, stop for plan review and bring back the complete narration and scene plan. Wait for approval before production. Continue the same video when I request progress. Do not create scheduled tasks or messages. Return its preview, ngram project link and MP4 export when ready. If the ngram connector is not connected, read https://www.ngram.com/markdown/docs/connect-ngram-to-claude.md?view=1 and help me connect ngram to Claude. Wait for me to complete sign-in and approve access, then resume this workflow.

Read the video transcript

Video waiting for input? Reopen the same conversation and read its last message. If a plan is waiting, review it, then choose Request changes or Approve plan. If ngram asks a question, answer in the same conversation. Active production can take time. Keep the existing project while you check its status. If an error appears, read its recovery message before retrying. Once the needed input is supplied, the same conversation continues. If one careful retry doesn’t resolve the failure, contact Support with the conversation link and the action that failed.

How it works

One source. A repeatable workflow.

04 steps · Claude

Start with

A documented symptom, checks and resolution

ngram logo

Create in

Claude

Make

A reusable troubleshooting video

  1. Supply the documented answer

    Open a Claude conversation with ngram enabled. Paste the workflow prompt and add the support article. Identify the symptom and the intended customer. Supply genuine screenshots when the explanation needs a product control.

  2. Review the decision path

    Confirm the prepared settings with plan review. Compare each check and branch with the source. Make sure the diagram distinguishes waiting for input, active work and an unresolved failure. Request a correction before approving production when needed.

  3. Check the finished answer

    Ask Claude for progress on the same video. Watch the returned preview and follow the instructions in order. Verify the success state and the escalation path against the article.

  4. Add it to the support answer

    Choose an appropriate sharing or export option. Put the video beside the maintained help article or include its viewing link in your reviewed support reply.

Watch the workflow

Create a troubleshooting video in Claude

Follow the documented source, settings confirmation and decision-diagram revision, then watch the complete support explanation. Waiting time is removed.

Read the walkthrough transcript

The published support article and its source facts are supplied to Claude. The Blueprint style is selected and creation is confirmed with plan review. A revision keeps the error-recovery path separate from the branches that continue after user input. The revised diagram is reviewed and production is approved for the same video. Claude returns the finished MP4 and project link. The complete 45-second explanation plays with this narration. Video waiting for input? Reopen the same conversation and read its last message. If a plan is waiting, review it, then choose Request changes or Approve plan. If ngram asks a question, answer in the same conversation. Active production can take time. Keep the existing project while you check its status. If an error appears, read its recovery message before retrying. Once the needed input is supplied, the same conversation continues. If one careful retry doesn’t resolve the failure, contact Support with the conversation link and the action that failed.

Your starting point

Start with the prompt.

Prepare the answer in Claude, then check that each branch leads to the next step in your help article.

Open Claude ↗

Connect ngram to Claude

Review. Then deliver.

Claude returns the completed video and its ngram project. Compare the explanation with your source before delivery.

While your video is being made

Ask Claude for the current video’s status and review any pending question or plan.

Share a link

Choose appropriate visibility in ngram, then place the viewing link beside the maintained support answer.

Download the video

Ask Claude to prepare an MP4 and choose an export option available to your ngram account. Download in the ngram project requires an eligible paid plan. Check the saved file before uploading or sending it.

If the workflow needs attention

Ask Claude to inspect the existing video’s reported problem. Keep its ID and project link when continuing the same run.

A branch skips a prerequisite
Quote the missing prerequisite and identify the affected step. Ask Claude to place it before the action in the existing video.
The diagram implies every failure is resolved
Separate the successful path from the unresolved case. Supply the documented escalation and ask for a correction to the diagram and narration.
The product control has changed
Supply the current documentation and genuine interface evidence. Revise the affected instruction in the same project, then check the complete answer.

Keep the workflow. Change the story.

  1. 01

    Reuse the structure for another symptom

    Replace the symptom, source, checks and escalation together. Keep each new answer tied to the article that establishes its supported path.

  2. 02

    Maintain the answer with the article

    Keep the video project link with the written support source. Request a revision when that source changes and review the updated video before replacing the shared answer.

Turn your next source into a video.