Alga PSA Client Review
Overview
An account manager wants one page on a client: what we did, what is still open, what we
billed and whether they pay on time. Everything here is a read; no tool is admin-gated
in Conduit. For a long multi-section review, hand off to the
alga-client-review-analyst agent.
Common Workflows
1. Identify the client
alga_clients_list with search (add is_inactive false to skip old accounts), then
alga_clients_get for the record. If several clients match, list them and ask which one.
Pull alga_clients_locations_list and alga_clients_contacts_list for the sites and
people on the account.
2. Service activity for the period
- Opened in period:
alga_tickets_list with client_id, entered_from and
entered_to (UTC timestamps). Use fields to keep rows small and page to the end.
- Closed in period: same, with
closed_from / closed_to.
- Still open:
client_id with is_open true, sorted by entered_at ascending to
surface the oldest first.
- Break the opened tickets down by
priority_name and status_name, and note repeat
themes from titles (password resets, printer, VPN). Themes are the QBR talking points.
3. Time spent
Time entries are filtered by user and work item, not by client. Two practical routes:
- For a small ticket set, call
alga_tickets_time_entries_list for every ticket that
was open at any point in the period, keep only the entries dated inside the period,
and sum. That set is the union of the opened, closed and still-open pulls above plus
tickets opened before the period ended and closed after it (alga_tickets_list with
client_id, and entered_to and closed_from both at the period end). Respect the
4-calls-at-once limit per connection.
- For a broad view,
alga_time_entries_list with date_from / date_to and
work_item_type ticket, then keep only entries whose work item is one of this
client's tickets.
Report billable and non-billable hours separately (is_billable).
4. Billing
alga_invoices_list with client_id and an invoice_date_from / invoice_date_to
window for what was billed.
- Same with
status overdue for anything outstanding; alga_invoices_get and
alga_invoices_items_list when you need the lines.
alga_contracts_list has no client filter: filter rows by owner_client_id (or
owner_client_name) yourself. Use is_active true for current agreements.
5. Environment and projects
alga_assets_list with client_id for the managed estate; group by asset_type and
status.
alga_projects_list with client_id for active and recent projects; see
project-status to go deeper.
6. Write the summary
Sections: account snapshot (sites, key contacts, active contracts), service activity
(opened, closed, open backlog, top themes), effort (hours, billable split), billing
(invoiced in period, overdue), estate (asset counts), projects, and recommendations.
State the period and anything you could not read (for example a 403 on invoices).
Gotchas
- Ticket date filters are UTC timestamps; invoice and time-entry date filters are
YYYY-MM-DD. Mixing them up fails validation.
- Internal notes (
is_internal true on comments) and internal-audience knowledge
articles are for staff. Leave them out of anything the client will see.
- Counts are only as complete as the key's role. If invoices or time come back 403,
say so rather than reporting zero.
- Confirm how your Alga instance stores invoice amounts (for example on one invoice in
the Alga UI) before publishing totals.
- Nothing can be changed from here. Follow-ups such as "chase the overdue invoice" go in
the recommendations for a person to action.
Related Skills
1---2name: alga-psa-client-review3description: >4 Building a per-client account picture from Alga PSA for a QBR, renewal or5 health check: client record, locations and contacts, ticket volume and6 open backlog over a period, time spent, invoices and payment state,7 contracts, assets, and active projects. Covers which Alga filters exist per8 record type (contracts have no client filter) and how to keep internal9 notes out of client-facing output.10when_to_use: >-11 When preparing a QBR, account review, renewal conversation or client12 health check from Alga PSA data. Use when: alga qbr, alga client review,13 alga account health, client summary alga, how much work did we do for14 client alga, alga client report.15metadata:16 source: https://skillmd.com/skills/wyre-ai/alga-psa-client-review17---1819# Alga PSA Client Review2021## Overview2223An account manager wants one page on a client: what we did, what is still open, what we24billed and whether they pay on time. Everything here is a read; no tool is admin-gated25in Conduit. For a long multi-section review, hand off to the26`alga-client-review-analyst` agent.2728## Common Workflows2930### 1. Identify the client3132`alga_clients_list` with `search` (add `is_inactive` false to skip old accounts), then33`alga_clients_get` for the record. If several clients match, list them and ask which one.34Pull `alga_clients_locations_list` and `alga_clients_contacts_list` for the sites and35people on the account.3637### 2. Service activity for the period3839- **Opened in period**: `alga_tickets_list` with `client_id`, `entered_from` and40 `entered_to` (UTC timestamps). Use `fields` to keep rows small and page to the end.41- **Closed in period**: same, with `closed_from` / `closed_to`.42- **Still open**: `client_id` with `is_open` true, sorted by `entered_at` ascending to43 surface the oldest first.44- Break the opened tickets down by `priority_name` and `status_name`, and note repeat45 themes from titles (password resets, printer, VPN). Themes are the QBR talking points.4647### 3. Time spent4849Time entries are filtered by user and work item, not by client. Two practical routes:5051- For a small ticket set, call `alga_tickets_time_entries_list` for every ticket that52 was open at any point in the period, keep only the entries dated inside the period,53 and sum. That set is the union of the opened, closed and still-open pulls above plus54 tickets opened before the period ended and closed after it (`alga_tickets_list` with55 `client_id`, and `entered_to` and `closed_from` both at the period end). Respect the56 4-calls-at-once limit per connection.57- For a broad view, `alga_time_entries_list` with `date_from` / `date_to` and58 `work_item_type` ticket, then keep only entries whose work item is one of this59 client's tickets.6061Report billable and non-billable hours separately (`is_billable`).6263### 4. Billing6465- `alga_invoices_list` with `client_id` and an `invoice_date_from` / `invoice_date_to`66 window for what was billed.67- Same with `status` overdue for anything outstanding; `alga_invoices_get` and68 `alga_invoices_items_list` when you need the lines.69- `alga_contracts_list` has **no client filter**: filter rows by `owner_client_id` (or70 `owner_client_name`) yourself. Use `is_active` true for current agreements.7172### 5. Environment and projects7374- `alga_assets_list` with `client_id` for the managed estate; group by `asset_type` and75 `status`.76- `alga_projects_list` with `client_id` for active and recent projects; see77 [project-status](../project-status/SKILL.md) to go deeper.7879### 6. Write the summary8081Sections: account snapshot (sites, key contacts, active contracts), service activity82(opened, closed, open backlog, top themes), effort (hours, billable split), billing83(invoiced in period, overdue), estate (asset counts), projects, and recommendations.84State the period and anything you could not read (for example a 403 on invoices).8586## Gotchas8788- Ticket date filters are UTC timestamps; invoice and time-entry date filters are89 `YYYY-MM-DD`. Mixing them up fails validation.90- Internal notes (`is_internal` true on comments) and internal-audience knowledge91 articles are for staff. Leave them out of anything the client will see.92- Counts are only as complete as the key's role. If invoices or time come back 403,93 say so rather than reporting zero.94- Confirm how your Alga instance stores invoice amounts (for example on one invoice in95 the Alga UI) before publishing totals.96- Nothing can be changed from here. Follow-ups such as "chase the overdue invoice" go in97 the recommendations for a person to action.9899## Related Skills100101- [api-patterns](../api-patterns/SKILL.md)102- [ticket-triage](../ticket-triage/SKILL.md)103- [time-and-billing](../time-and-billing/SKILL.md)104- [project-status](../project-status/SKILL.md)