Chandler · usage
← Back to sessions

Session

User
kathryn.buckley@dext.com · Kathryn Buckley
Started
2026-08-06 08:52
Last activity
2026-08-06 09:28
Questions
7
Grouping
backfill — reconstructed from timing by migration 011
session_id
5484b453-ab11-46c3-b90b-9a95eb55dca3

Transcript

  1. 2026-08-06 08:52 ask success $0.8032 236.9 s full detail →
    How many Dext client accounts that are attached to a Partner and currently active have only a basic Dext subscription with no add-ons — meaning no AI Assist, no Vault, no Data Health, no Dext Solo, and no e-invoicing in France?
    No answer recorded.
    1 row EXPERIMENTAL Subscriptions Signals
  2. 2026-08-06 08:54 ask success $0.4098 117.4 s full detail →
    How many Dext client accounts that are attached to a Partner and currently active have only a basic Dext subscription with no add-ons — meaning no AI Assist, no Vault, no Data Health, no Dext Solo, and no e-invoicing in France?
    No answer recorded.
    1 row Bookings
  3. 2026-08-06 08:56 generate success $0.3742 60.4 s full detail →
    How many Dext client accounts that are attached to a Partner and currently active have only a basic Dext subscription with no add-ons — meaning no AI Assist, no Vault, no Data Health, no Dext Solo, and no e-invoicing in France?
    No answer recorded.
    Bookings
  4. 2026-08-06 08:57 ask success $0.0193 10.2 s full detail →
    What is the definition of the field has_any_prepare_contract_addon on eds_bookings? Which specific add-ons or contract types does it include (e.g. AI Assist, Vault, Data Health, Dext Solo, France e-invoicing)?
    No answer recorded.
  5. 2026-08-06 09:00 ask success $0.2282 95.8 s full detail →
    Using the same account population as before (Dext client accounts attached to a Partner, currently active, with a paid subscription, excluding demo and reseller accounts), break this down by region. For each region show: total number of such client accounts, the number of those accounts with no add-ons (has_any_prepare_contract_addon is false) i.e. "basic" subscription accounts, and the percentage of accounts in that region that are "basic".
    No answer recorded.
  6. 2026-08-06 09:02 ask success $0.2395 108.2 s full detail →
    Break down eds_all_accounts by region. Filters: finance_account_type = 'Corporate', has_dext_parent = true, is_suspended_dext = false, has_prepare_access = true, salesforce_account_type != 'Reseller', parent_or_client_has_dext_paid_subscription = true, is_dext_demo = false, and eds_calendar_day.is_latest_available_date = true. For each region show: total distinct accounts, distinct accounts where eds_bookings.has_any_prepare_contract_addon is false, and that as a percentage of the region total.
    No answer recorded.
  7. 2026-08-06 09:28 ask success $0.5309 162.3 s full detail →
    Same population as before (Dext client accounts attached to a Partner, currently active, with no add-ons versus with add-ons), broken down by region. Show total number of client accounts per region, number with a basic subscription (no add-ons), and basic accounts as a percentage of total accounts in that region.
    No answer recorded.
    16 rows Bookings

Cost is the LLM completion spend LiteLLM priced for each call, summed per request. Chandler is running on the Codex CLI, which draws ChatGPT plan quota rather than per-token API billing, so this figure is not money paid — it is what the same traffic would have cost on the API, priced from the token counts Codex reports. Read it as the size of the bill avoided. Two known limits: embedding spend is not recorded, so retrieval and matching cost is missing, and because the figure is one sum per request it cannot be split by model within a request — a request's classifier and agent calls can use different models while llm_model holds only one name. Only authenticated calls are logged, USAGE_LOG_ENABLED can switch logging off, and log writes are fail-soft — this is not a complete record of traffic. Questions are grouped into sessions: a session is exact when the caller echoed its id back to us and otherwise inferred from a 30-minute gap in that user’s activity, so a grouping is only as good as the source shown on the session itself. A call with no attributable user gets no session at all; those questions are listed separately rather than dropped.