Skip to content
Clevera Help Center

Find where to start for your team

Short paths for customer support, product marketing, sales, training and onboarding, and developers: what to make first, which features to use and where to read more.

Updated 5 min read

Most teams need only part of Clevera at first. Find your team below for what to make first, which features matter and where to read more. Each path assumes you've added your brand and installed the desktop app; see Set up your workspace.

Your team Make first
Customer support and help center A troubleshooting video and its article, on a doc site
Product marketing A social clip and a product demo for your next feature
Sales A sales pitch demo you share as a link
Training and onboarding An onboarding video and an SOP
Developers and AI assistant users A connection from Claude, ChatGPT or Cursor

Customer support and help center

Answer the questions you get most often with a video and an article, then put them in a help center.

  1. Record the fix for your most common ticket with the desktop app, talking through each step.
  2. Make a How-to video (Troubleshooting) from the recording, then a Troubleshooting article from the same recording.
  3. Create a doc site, add the article, and publish. If you already have a help center in Zendesk, Intercom, Help Scout or another tool, import it instead of starting empty.
  4. Turn on the site's Ask AI assistant, then check Search and Feedback insights for what readers can't find.

On Pro and up, hand over the upkeep to Autopilot: Build a help center from my app, Keep my help center up to date when we ship, Turn customer questions into help articles and Fill the gaps in my help center every week.

Product marketing

Turn each launch into a set of clips, a demo and a write-up, all in your brand.

  1. Check your brand on Brands. Social clips and templates use its logo, colors, fonts and voice.
  2. Make a social clip for the feature: Feature spotlight, Launch teaser or Feature announcement. Add the feature's web page as a source and the AI reads it for pictures and facts. Social clips need Starter or above.
  3. Record the feature and make a Product demo (New feature or Product launch) with real product footage.
  4. Make a Product update or Blog post article from the same recording.
  5. Translate the clip and the demo for each market you sell in.

On Pro, send finished videos to LinkedIn, X and YouTube from the Share window.

Sales

Send prospects a demo they can watch on their own time, and see whether they did.

  1. Record your demo flow, or let Record with AI record it in a demo account.
  2. Make a Product demo (Sales pitch). For a deck, use Investor pitch with your slides or PDF.
  3. Send it as a link in your email, or embed it on a page, then open its analytics for views, completion and how far viewers got.
  4. For outreach, make a Customer story clip or an AI avatar clip that talks the viewer through the product (Starter and up).

Training and onboarding

Write a process down once and teach it the same way every time, for new teammates or new customers.

Internal training

  1. Record the process while you explain it. Speaker notes keep your script on screen without showing in the recording.
  2. Make an SOP article and an Onboarding how-to video from the recording.
  3. Group them in a collection, or publish them on a doc site. On Pro, make the site private with a password or workspace sign-in.

Customer onboarding

  1. Make a How-to video (Getting started) for your first-run setup.
  2. Embed it in your app or send its link in your welcome email, and translate it for your customers' languages.
  3. On Pro and up, Make getting-started videos for new users in Autopilot plans a first-steps path through your app.

Developers and AI assistant users

Work with Clevera from your own tools, and keep docs in step with your code.

  1. Connect Claude or ChatGPT as a connector, or create an API token for Claude Code, Codex, Cursor or another MCP client. From there you can find recordings, request videos and articles, run Autopilot tasks and work on doc sites. AI agents & API is on Pro and Custom.
  2. Script your own flows with the REST API, and get webhooks when an agent's job finishes or waits for approval.
  3. On Pro and up, connect your GitHub repository to Autopilot so Keep my help center up to date when we ship plans fixes after each release.
  4. Publish articles to GitHub, GitLab or Bitbucket as Markdown files. Doc sites also publish llms.txt and Markdown copies of public pages for AI tools.

The desktop app runs on Linux as well as Mac and Windows.

For the full picture, see Understand what Clevera does.