# Client Summary https://docs.wisecp.com/de/client-summary The account read at a glance: what is owed, what has been bought, who the client is and how much the record is worth trusting. ## Opening the Screen Summary is the first tab of a client record, so it opens with the client: `{admin}/users/detail?id={client}&tab=summary` ## What Is on the Screen Four cards, each one saying a single thing and supporting it underneath. - **Accounting**: Money still uncollected, with the paid, unpaid, cancelled and refunded split underneath. - **Client Details**: Who the client is: name and company, contact details, location and account facts. - **Trust Score**: A 0-100 reading of how established the account is, with the four inputs that produced it. - **Total Order Volume**: What the client has spent, where their services stand, and how the portfolio splits by product group. ### Accounting The lead figure is what has not been collected yet, so the card answers "does this account owe us anything" before anything else. Under it, a single bar shows the collection mix - paid, unpaid and cancelled - and the counts sit beside their amounts. Refunds are listed but kept out of the mix: a refunded invoice was collected once, and counting it again would understate the paid share. The card's own actions are here too: issue a new invoice, send a reminder, or open the client's invoice list. ### Client details Account type, e-mail address and phone with their verification marks, language, currency, location, registration date and last sign-in. An unverified address can be marked as verified from here without leaving the tab. ### Trust score One number between 0 and 100, and the four axes that produce it. The score is not stored; it is calculated again from the current data every time the card is opened, so there is no way to bring yesterday's score back. Each axis draws its points from its own threshold table, the four are added up, and the total is capped at 100. With the default tables the highest reachable total is exactly 100. - **Active Services**: Only services in the **active** state are counted. Suspended, cancelled and expired ones do not enter the figure. - **Total Revenue**: The sum of the client's **paid** invoices - lifetime, not for a period. Amounts are added up without regard to currency. - **Account Age**: The time since the registration date, in years. An account younger than a month counts as zero. - **Support Requests**: The number of requests in the last **three months** - the ones opened in that window, not the ones still open. The default thresholds and the points they award: | Axis | Condition | Points | | --- | --- | --- | | Active services | none | 0 | | Active services | 1 - 5 | 20 | | Active services | 6 - 15 | 25 | | Active services | 16 and above | 30 | | Total revenue | none | 0 | | Total revenue | up to 100 | 5 | | Total revenue | up to 500 | 10 | | Total revenue | up to 1,500 | 15 | | Total revenue | up to 3,000 | 20 | | Total revenue | over 3,000 | 25 | | Account age | younger than a month | 0 | | Account age | up to 1 year | 5 | | Account age | up to 4 years | 10 | | Account age | up to 7 years | 15 | | Account age | up to 9 years | 20 | | Account age | over 9 years | 25 | | Support requests | none | 0 | | Support requests | 1 - 5 | 20 | | Support requests | 6 - 10 | 15 | | Support requests | 11 - 30 | 10 | | Support requests | 31 and above | 5 | On the card each axis shows its points against its own ceiling (active services 30, revenue and age 25, support requests 20). The ceilings are not equal; the number of services contributes most to the total. The total also gives the badge under the card its name: - **Excellent**: 80 and above. - **Good**: 60 - 79. - **Fair**: 40 - 59. - **Poor**: Below 40. The thresholds and points are opened by the settings icon in the card's top-left corner. What is changed there applies to **the whole installation** - there is no per-client scoring. ### Total order volume The headline figure is everything the client has spent. The badge beside it counts their services, whatever state those are in. The four numbers below report where the services stand: active, suspended, renewing within 30 days, and cancelled. Each opens the service list filtered to that set. Renewing looks forward only; an overdue service appears on the accounting card instead. At the bottom the portfolio splits by product group. The tint behind a row shows that group's share of the volume. ## Tasks ### Chase an unpaid balance 1. Read the lead figure on the Accounting card - it is the uncollected total, not the lifetime one. 2. Use the reminder action to send the client their outstanding invoices. 3. Open the invoice list from the same card when you need to see them one by one. 4. Once a payment lands, the lead figure and the collection bar show the new position the next time the tab opens. ### Verify a contact detail 1. Find the e-mail address or phone on the Client Details card; an unverified one is marked. 2. Use the mark-as-verified action next to it. 3. The chip in the header strip clears at the same time. ## Things to Watch > **The lead figure is what is owed, not what was earned** > > The Accounting card leads with the uncollected amount. Total earnings are on the order volume card - reading one for the other is the easiest mistake to make on this tab. > **The trust score decides nothing on its own** > > No automation reads it. It is there to help you prioritise, and the thresholds behind its badges are yours to configure. > **Opening no support requests lowers the score** > > The request axis reads as "fewer is better", but **zero** gives the lowest value: 1-5 requests earn 20 points while an account that has opened none earns 0. The reason is that silence cannot tell a loyal client apart from an abandoned account. A new, trouble-free account scoring lower than you expected is usually this. > **Amounts are shown in one currency** > > Invoice totals are gathered into a single currency so the card can be read at a glance. An individual invoice always keeps the currency it was issued in. ## Required Privileges The tab opens with the client record itself. Its actions need more: issuing an invoice and sending reminders need `USERS_OPERATION`, and the balance figure follows `USERS_MANAGE_CREDIT`. ## Related Articles - [Client Detail Overview](https://docs.wisecp.com/en/client-detail-overview) - [Client Invoices](https://docs.wisecp.com/en/client-invoices) - [Client Products and Services](https://docs.wisecp.com/en/client-products-and-services)