REPORTING & QA
PrintSpeak has AI usage reporting, conversation history, previews, and internal test utilities. It does not expose the broad evaluation matrix we previously described.
This section is intentionally narrower after factchecking. It reflects the real reporting and preview surfaces available today.
Feature family placeholder
Reserved for a dedicated interface preview, workflow diagram, or annotated screenshot.
MATRIX
AI usage summary
Includes
Pie-chart and area-chart views summarizing usage across agents and months.
Why it matters
There is a real reporting dashboard for adoption and traffic, which is stronger than inventing a test suite.
Usage by user
Includes
Date-range filtered user breakdowns with CSV export.
Why it matters
This is a concrete operational report exposed in enterprise reporting.
Usage by tenant
Includes
Date-range filtered tenant breakdowns with CSV export.
Why it matters
This gives rollout visibility by location or business unit without overstating QA coverage.
Conversation history
Includes
A filterable AI conversation list by agent, model, and tenant.
Why it matters
This is the real operational audit/review surface for AI usage.
Conversation transcript view
Includes
Per-conversation transcript display with message counts, metadata, and timestamps.
Why it matters
Reviewers can inspect what actually happened in production conversations.
Agent preview
Includes
The agent builder includes a live preview entry point for the current configuration.
Why it matters
Editors can manually validate changes before treating the agent as ready.
Facet previews
Includes
Builder modals preview how individual facets inject or render context.
Why it matters
This supports configuration QA even though it is not a formal regression runner.
Instructions preview
Includes
A dedicated preview for the final instruction set sent to the model.
Why it matters
Prompt QA is supported at the builder layer, which is more accurate than claiming answer baselines.
Widget configuration preview
Includes
External widget configuration pages show themes, titles, and validation warnings.
Why it matters
This supports embed QA for external agents before sharing code with customers.
Internal SDK test harnesses
Includes
The repo includes an SDK test page and headless test scripts for widget verification.
Why it matters
These are real internal QA utilities, but they should not be presented as a polished customer-facing evaluation suite.
| Capability | Includes | Why it matters |
|---|---|---|
AI usage summary | Pie-chart and area-chart views summarizing usage across agents and months. | There is a real reporting dashboard for adoption and traffic, which is stronger than inventing a test suite. |
Usage by user | Date-range filtered user breakdowns with CSV export. | This is a concrete operational report exposed in enterprise reporting. |
Usage by tenant | Date-range filtered tenant breakdowns with CSV export. | This gives rollout visibility by location or business unit without overstating QA coverage. |
Conversation history | A filterable AI conversation list by agent, model, and tenant. | This is the real operational audit/review surface for AI usage. |
Conversation transcript view | Per-conversation transcript display with message counts, metadata, and timestamps. | Reviewers can inspect what actually happened in production conversations. |
Agent preview | The agent builder includes a live preview entry point for the current configuration. | Editors can manually validate changes before treating the agent as ready. |
Facet previews | Builder modals preview how individual facets inject or render context. | This supports configuration QA even though it is not a formal regression runner. |
Instructions preview | A dedicated preview for the final instruction set sent to the model. | Prompt QA is supported at the builder layer, which is more accurate than claiming answer baselines. |
Widget configuration preview | External widget configuration pages show themes, titles, and validation warnings. | This supports embed QA for external agents before sharing code with customers. |
Internal SDK test harnesses | The repo includes an SDK test page and headless test scripts for widget verification. | These are real internal QA utilities, but they should not be presented as a polished customer-facing evaluation suite. |
RELATED FAMILIES
ENTERPRISE FEATURES
The real admin surface centers on agent creation, versioning, import/export, scope controls, and operational configuration inside the enterprise UI.
AUTHENTICATION
The implemented access model centers on agent API keys, signed or encrypted tokens, origin controls, and agent/context resolution.
SDK
The implemented surfaces are a standalone widget script, a JS API, trigger elements, and internal Rails/Stimulus helpers.