Editing the Dashboards

All of Revibe's CX dashboards — Orders, Tickets, Calls, Disputes, Claims — live in one place (a GitHub “repository” called cx-dashboard). You don't edit them by hand. Instead you open Claude Code (an app), tell it in plain English what you want changed, and it makes the change and publishes it for you.

The flow is always the same three steps:

• You say what to change (naming the dashboard).
• Claude edits the right file and saves it to GitHub.
• The website updates itself automatically in a minute or two — refresh the page to see it.

You only do this once. After that, you just open the app and talk.

1. Get access to the dashboardsAsk Mohamed (or a repo admin in the revibe-tech org) to add your GitHub account as a collaborator on the revibe-tech/cx-dashboard repository, with write access. You'll get an email invite — click Accept. (If you don't have a GitHub account, create a free one first at github.com and send Mohamed your username.)
2. Install Claude CodeDownload the Claude Code desktop app for your computer (Windows or Mac) and install it. Sign in with your Anthropic (Claude) account. If you don't have one, Mohamed can add you to the team plan.
3. Open the dashboards projectIn Claude Code, open the cx-dashboard project. The simplest way: type clone the GitHub repo revibe-tech/cx-dashboard and open it and Claude will download it and set it up. Sign in to GitHub if it asks.
4. You're readyFrom now on you just open Claude Code and type what you want. The next sections show how.

The most important thing when asking for a change is to name the right dashboard — use the same name you see on the workspace selection page. Claude uses that to find the right files. Here's the map:

The Disputes dashboard has several inner pages you can also name directly:

To change something, open Claude Code and type your request. A change goes live in three moves:

1. AskName the dashboard and say what you want. Example: On the Disputes dashboard, rename the “Win Rate (Closed)” card to “Success Rate”.
2. Claude makes the change and publishes itClaude edits the right file and saves it to GitHub. The website rebuilds automatically — usually within a minute or two.
3. Refresh and checkOpen the dashboard in your browser and refresh the page (or press Ctrl+F5) to see it. You can ask Claude “is it live yet?” and it will check for you.

You don't need special wording — just be clear. A good request usually has three parts: which dashboard, what to change, and what it should become.

The pattern

Examples that work well

• On the Disputes Daily Breakdown, make “All open” the default filter.
• On the Orders dashboard, add a column to the late-orders table showing the courier name.
• On the Claims dashboard, change the SLA-warning colour from yellow to orange.
• On the Disputes main dashboard, add a KPI card for “Average first response time”.

If you're not sure what it's called

Describe what you see on screen — Claude will find it. For example: On the disputes main page, the big red number labelled “Money Lost” — can we also show it in USD? A screenshot with an arrow works great too; you can paste one straight into Claude.

Discussing new metrics

You can also just think out loud before changing anything: What metrics could we add to the Orders and Claims dashboards to track SLA performance? Suggest options first, don't change anything yet. Claude will propose ideas; you pick; then it builds the ones you approve.

Nothing is ever permanent or lost — every change is saved in history and can be reversed by asking.

• Undo the last change: Undo the last change you made and publish it.
• Go back to an earlier version: Roll the Disputes dashboard back to how it looked this morning.
• Something looks broken: tell Claude what you see — the Claims dashboard is showing an error after the last change, please fix or revert it.