# Customer overview ### Customer overview
**Where to find it:** Customers in the left navigation **Who can access it:** All team members *** #### The customer portfolio The Customers view is the default home screen in Startdeliver. It shows every customer your team manages in one place — with AI Health Assessment status, assigned team members, lifecycle stage, renewal date, ARR, and any custom fields your team has configured visible at a glance. This is where CSMs start their day: reviewing what's changed, spotting at-risk accounts, and picking up where they left off. *** #### Lists The portfolio is organized into lists. Each list is a saved view with its own filters, columns, and widgets. You switch between lists using the tabs at the top of the Customers view. Every team member sees the same lists but a list filtered by "Current signed in" will show each CSM only their own customers — one list, personalized for everyone. Common lists teams set up out of the box: My Portfolio, Onboarding, Churn Risks, Expansions, Renewals, Success Plans. You can create as many lists as you need and share them across the team. → See [Lists & filters](/platform-settings/lists-and-filters.md) for how to build, customize, and share lists. *** #### The customer profile Opening any customer takes you to their profile. The profile has three main areas. From the customer profile you can also send one-off emails to users and external recipients without leaving Startdeliver. → [Email](/managing-customers/sending-emails.md)
**The top bar** shows the customer name and logo, assigned team members, the current lifecycle status (Onboarding, Adoption, Engagement, etc.), and — if the customer is part of a group — a link to the parent account. **The assessment panel** shows the current AI Health Assessment — the status label, the plain-language summary, the trend line over time, and a Take Action button with recommended next steps. This panel updates automatically as new data comes in. **The metric tiles** below the assessment show ARR, Usage health, Feedback health, Support health, and any additional fields your admin has configured — for example customer tier, payment status, or a product-specific KPI. Tiles are colour-coded based on rules your admin sets. *** #### Account hierarchy Startdeliver supports parent and child accounts. If a customer is part of a larger group — a holding company, a parent organization, or an enterprise account with multiple subsidiaries — you can link them.
Child accounts appear as independent customers in the portfolio with their own profiles, health scores, and assigned CSMs. The parent account links to all children, giving a consolidated view of the group. This is useful for enterprise customers where different business units have separate contracts but need to be managed as a single relationship at the account level. *** #### Creating a customer To add a new customer, click + Create new at the top of the Customers view. Enter the customer name and any required fields your admin has configured. The customer immediately appears in the portfolio and is ready for a CSM to be assigned and a project to be launched. Customers can also be created in bulk via CSV import (Settings → Import) or automatically via integrations when a new account is created in your CRM or billing system. *** #### Assigning a team member Each customer can have one or more team members assigned. Assignment controls which customers appear in a CSM's personal list view and determines the scope of permission rules if your admin has configured assignment-based access. To assign: open the customer profile, click the team member avatars in the top bar, and select from the team. {% embed url="" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.startdeliver.io/managing-customers/customer-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.