Development record: October 29, 2026. Written retrospectively.
You can now ask an assistant to export LiteLedger’s customer signals for use alongside your other customer-experience data. The assistant connects through MCP, the protocol it uses to call LiteLedger’s tools.
The new export_customer_signals tool provides frustration, confusion, success and delight counts, analysis coverage, and source evidence. Choose a date range and request customer totals, daily, weekly or monthly rows, or individual messages carrying a signal. The export reuses the same analysis facts as the report and keeps missing analysis explicit.
For example, ask your connected assistant:
Use LiteLedger to export weekly customer signals for October 1–25, 2026, using UTC dates. Collect every page, keep assessment coverage with the counts, and explain what the data can support.
Exports cover the full selected scope across multiple pages. Each identifies its data version. Have the assistant collect every page and check the row count before replacing an earlier result for the same scope. Records absent from the new version need to come out of the older result too.
Compare account or project activity over the same time window where identifiers match. A time match alone does not establish a shared session.
See the MCP setup page after sign-in for connection instructions and more examples.