Get Luminair ↑
A small software company where everyone does three jobs

Four people, eleven tools, and the same argument again.

One place where product, support and numbers meet, and where decisions stay decided.

Try it in 6 stepsDownload Luminair
Support3 apps connected

Summarise this month's support tickets by feature. Which complaint is growing fastest, and does our usage data back it up?

Support ticketsProduct usageTask list
  1. Claudegroups the tickets by problem
  2. Geminichecks whether similar complaints are really the same issue
  3. Codexcounts customers affected and drafts the tasks
You get

Support, September

  • Export to CSV: 31 tickets, up from 12
  • Usage agrees: export clicks doubled after the redesign
  • 2 groups merged: same bug, different wording
How this job looks in a Luminair session. Illustration with sample content.
The problem

Feedback is in Slack. Tickets are in the helpdesk. Numbers are in analytics. The reason you chose not to build that feature in March is in a call nobody recorded.

Try it yourself in Luminair

Six steps. No setup beyond the AI plan you already have.

  1. 1

    Install Luminair and sign in

    Download Luminair and open it. Go to Settings → Models → Add account and sign in with an AI plan you already pay for, like Claude, ChatGPT or Gemini.

  2. 2

    Make a folder for this job

    In the sidebar, choose New folder… and name it “Support”. Then choose New session in this folder. Everything for this job stays together.

  3. 3

    Bring the information in

    You need: support tickets, product usage and task list. Connect Intercom, Asana and Gmail in Settings → Connectors, or export the files and drag them into the chat.

  4. 4

    Ask for the result

    Paste this into the session, or say it in your own words:

    Summarise this month's support tickets by feature. Which complaint is growing fastest, and does our usage data back it up?
  5. 5

    Get a second opinion

    Pick a different model in the model picker and ask it to check the first answer:

    Are any of these groups actually two different problems with similar wording?
  6. 6

    Make it repeat

    Open Flows → New and add the steps: Read new tickets and Slack feedback → Group by feature and count → Draft tasks and a weekly summary. Choose when it runs, like every Monday at 09:00. Nothing is sent or changed until you approve it.

How it plays out

Three folders, one window

Create folders for Product, Support and Growth. Connect Intercom and Asana in Settings → Connectors, and PostHog for usage data, so sessions can read what customers said and what they did.

Ask across all of it

Ask what customers complained about this month and whether usage agrees. Use one model for careful analysis and another for fast drafting, in the same window.

Write decisions down

When you decide, save the decision and the reason in Journal. A weekly Flow summarises new tickets by feature and drafts the tasks for your tracker, ready for you to confirm.

You stay in charge

Tasks and replies are drafted, not sent. A founder confirms what goes into the tracker and what goes to a customer.

The new engineer asks why something was decided and gets the real answer, with the date, in ten seconds.

Sign in with the AI plan you already have and start with this job.

Download Luminair