| Last active | User | First match | Questions | Cost | Feedback |
|---|---|---|---|---|---|
| 2026-09-30 09:50 | gerty.bester@dext.com | For the AI Assist guidance named "Correct Total Amount to GBP for Car Rentals", was it created by a user or by the agent (Dext AI)? What is its created-by value and created date? | 1 | $57.6242 | — |
| 2026-09-28 19:03 | gerty.bester@dext.com | Of the AI Assist guidances that are currently active (switched on), what share were generated automatically by Dext (auto-generated from edit history) versus written by the customer? Also, of AI Assist suggestions applied since tracking began, what share were auto-applied versus manually accepted? | 1 | $34.3431 | — |
| 2026-09-27 15:01 | gerty.bester@dext.com | Total number of AI Assist suggestions created and applied to date (all time, global), and the number of partner practices and client businesses that have had at least one AI Assist suggestion. | 3 | $135.9652 | — |
| 2026-09-27 12:51 | gerty.bester@dext.com | Since April 2026, how many new Dext user signups used Google SSO or Microsoft SSO, and what share of all new signups is that, by month? | 3 | $326.9042 | — |
| 2026-09-11 14:37 | suzannah.weinfass@dext.com | How many Solo-type clients have had usage in the last 90 days (active/engaged filter: number of days since last usage <= 90), using the same base filters as before (Corporate finance account type, has Dext parent, not demo, not suspended, not reseller)? | 1 | $2.5222 | — |
| 2026-09-01 13:51 | yordan@dext.com | Show me partner accounts with outstanding invoices, aging buckets, total debt, account manager, last login, next invoice date, NetSuite number, company registration number, subsidiary | 1 | $1.2311 | — |
| 2026-08-17 09:47 | kathryn.buckley@dext.com | Using the same engagement definition as the Feature Adoption Omni dashboard (https://dext.omniapp.co/dashboards/feature-adoption), what is the percentage of Partner accounts and the percentage of Client accounts using Item Messaging, on average over the last 6 months? | 1 | $0.8667 | — |
| 2026-08-05 13:29 | yordan@dext.com | Using Product Usage - Users topic, run the actual query and give me the current total number of distinct Dext Solo accounts (is_solo true), latest available date, excluding demo accounts | 3 | $1.5024 | — |
| 2026-07-20 15:26 | yordan@dext.com | top 5 accounts by ARR with contact email addresses | 1 | $1.2086 | — |
| 2026-07-16 14:45 | yordan@dext.com | Find partner account CRNs and account names for users with these email addresses: rromena@hotmail.com, damian@fmta.uk, pamela@cannonaccountants.co.uk, dwhite@iwlservices.co.uk, scottg@gmcgca.com, administrator@syncbs.co.za, milda@1185films.com, jemma.smart@gvbookkeeping.co.uk, libby@jbuildersservices.co.uk | 2 | $1.7478 | — |
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.