hdls Success
hdls Success is a headless, MCP-native customer success management backend. It manages accounts, health scores, success plans, and touchpoints, operated entirely through named tools your AI assistant calls. It stands in for tools like Gainsight, ChurnZero, Catalyst — same job, no UI to run.
💬 Just ask
"Create an account for Acme, then show me my accounts."
You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.
How Success is organized
The headline entity is the account — start there, then attach the rest to it. Records connect by reference: a success_plan links to an account; a touchpoint links to an account. The health_check table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
account | A post-sale account managed for success: health, ARR, renewal, owner. | — |
success_plan | A success plan linked to an account. | account |
touchpoint | A touchpoint linked to an account. | account |
health_check | Append-only point-in-time health scores + signals. | account |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up an account end to end:
create_account→log_health_check→create_success_plan
Tools
Call these at https://hdls.ai/api/mcp/csm. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.
Create
| Tool | What it does | Required | Optional |
|---|---|---|---|
create_account | Create a new account. | name | account_ref, tier, arr, health_score, status, csm_owner |
create_success_plan | Create a new success plan. | account_id, objective | status, due_date, data |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
log_health_check | Log health check. | account_id | score, signals, note |
log_touchpoint | Log touchpoint. | account_id, body | kind, author |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_accounts | Search accounts by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
renewals_due | List the renewals coming due. | — | — |
Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.
Field reference
Every field you can set on each record. Custom fields you add live alongside these in data.
account
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
account_ref | text | ||
tier | text | ||
arr | numeric(14,2) | ||
health_score | number | ||
status | text | Lifecycle state. | |
csm_owner | text | ||
renewal_date | date | ||
data | json | Free-form JSON — custom fields live here. |
success_plan
| Field | Type | Required | Notes |
|---|---|---|---|
account_id | id | Yes | Links to an account. |
objective | text | Yes | |
status | text | Lifecycle state. | |
due_date | date | ||
data | json | Free-form JSON — custom fields live here. |
touchpoint
| Field | Type | Required | Notes |
|---|---|---|---|
account_id | id | Yes | Links to an account. |
kind | text | ||
body | text | Yes | |
author | text |
Tailor it with custom fields
Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.
Roles & safety
- Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass
tenant_id, and you can only ever see your own data (enforced by Postgres row-level security). - Role-gated. Permissions run
reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner. - History is append-only. The
health_checktimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "csm" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/csm as a connector in your assistant — see Connect your assistant.
A worked example
The literal call your assistant makes when you ask it to create the headline record:
Tool: create_account
Arguments: {
"name": "Acme Corp"
}