Skip to main content

Get started with Kinn

You only need one product and one feedback source to get a useful first answer. Start small; you can add more sources and teammates later.

1. Create your account and product​

After verifying your email, enter:

  • Company Name — the team or organization using Kinn
  • Product or Game Title — the app, game, service, or project whose feedback you want to understand

Complete the billing setup shown in the app. Kinn then opens an onboarding conversation for your new product.

2. Give Kinn a short product description​

In the onboarding chat, explain what the product is and who it serves. Two or three plain sentences are enough:

Northstar is a co-op survival game for PC. Players build settlements and explore together in groups of up to four.

This context helps Kinn recognize product names, features, and relevant conversations. You can update it later under Settings → [Product] → General or by asking Kinn in chat.

3. Connect one focused source​

Open Settings → Integrations → Add Integration and choose the place with the most useful feedback today:

  • A Discord or Slack channel used for support
  • Your app's store listing
  • Your Steam page
  • A subreddit, social post, or YouTube channel
  • A support inbox through Email

Follow that integration's setup page, then allow the first index to finish. See Integrations if you are unsure which source to choose.

4. Ask your first question​

Return to New Chat and ask a question with a topic and time period:

What were the most common complaints in the past 30 days? Show a few source examples for each one.

Continue with follow-up questions such as:

  • Which complaint is growing fastest?
  • Are people reporting it on more than one source?
  • Turn the result into a chart.

5. Add context gradually​

Once the first source is working:

  • Connect another source to compare audiences.
  • Save release dates or known issues as notes.
  • Save a question you repeat often as a saved prompt.
  • Invite teammates from Settings → Team.

You do not need to configure everything at once. A focused source and a clear question are the best starting point.