AGENT FEATURES
This is where the real PrintSpeak AI surface is strongest: model selection, prompting, facets, tools, actions, routing, charts, and triggers.
The rows below are grounded in the registered facets, tools, actions, and builder controls found in the PrintSpeak codebase.
Feature family placeholder
Reserved for a dedicated interface preview, workflow diagram, or annotated screenshot.
MATRIX
Model picker
Includes
A searchable model chooser backed by the `Ai::MODELS` registry and per-model score cards.
Why it matters
PrintSpeak clearly supports multiple LLMs and treats model choice as an editor-facing feature.
Prompt templates and instructions
Includes
Template loading plus a system prompt editor in the agent builder.
Why it matters
The product exposes instruction authoring directly, rather than hiding it as a developer-only concern.
Behavior facet
Includes
Configurable style, creativity, and formality controls.
Why it matters
This is explicitly implemented and should be described using the actual control surface.
Attached resources
Includes
Agents can attach assets, expose snippets to prompts, and enable the resource tool.
Why it matters
This is the concrete document-context feature in PrintSpeak, and it pairs with the embedding service in the codebase.
Web research tools
Includes
Google Custom Search via `web_search` plus page extraction through `visit_url`.
Why it matters
The product genuinely supports live web research rather than static-only prompt grounding.
Business data facets
Includes
Company, tenant, enterprise, user, review, estimate, sales info, and sales metrics context.
Why it matters
These domain-specific facets are a stronger and more factual story than vague 'enterprise context' claims.
Chart rendering
Includes
Inline chart generation using the chart facet and registered business chart sources.
Why it matters
Chart support is directly implemented and scoped to tenant or company context.
Classification facet
Includes
Quality, type, and priority classification against configurable prompt rules.
Why it matters
This is a real structured classifier and feeds directly into user-query trigger logic.
Multi-agent routing
Includes
Ask-facet routing to other agents, with mention and slash-command routing layered on top.
Why it matters
The routing story is real and richer than a single chatbot facade.
@mentions and slash commands
Includes
Hidden mention and command facets route `@agent-name` and `/command` style inputs.
Why it matters
This is implemented behavior, not speculative product positioning.
Actions with undo support
Includes
Company updates, industry updates, saved structured data, note creation, and Freshdesk ticket creation.
Why it matters
Several actions are auto-approved, and some explicitly support undo via stored undo data.
Feedback and response helpers
Includes
Feedback buttons, copy-to-clipboard UI, related follow-up questions, and status indicators.
Why it matters
These response embellishments are actual facets in the renderer pipeline.
Scheduled and query triggers
Includes
Hourly/daily/weekly schedule triggers plus user-query triggers with classification prompts, tenant targeting, and Run Now.
Why it matters
Trigger automation is a real feature family that deserves to be stated precisely.
| Capability | Includes | Why it matters |
|---|---|---|
Model picker | A searchable model chooser backed by the `Ai::MODELS` registry and per-model score cards. | PrintSpeak clearly supports multiple LLMs and treats model choice as an editor-facing feature. |
Prompt templates and instructions | Template loading plus a system prompt editor in the agent builder. | The product exposes instruction authoring directly, rather than hiding it as a developer-only concern. |
Behavior facet | Configurable style, creativity, and formality controls. | This is explicitly implemented and should be described using the actual control surface. |
Attached resources | Agents can attach assets, expose snippets to prompts, and enable the resource tool. | This is the concrete document-context feature in PrintSpeak, and it pairs with the embedding service in the codebase. |
Web research tools | Google Custom Search via `web_search` plus page extraction through `visit_url`. | The product genuinely supports live web research rather than static-only prompt grounding. |
Business data facets | Company, tenant, enterprise, user, review, estimate, sales info, and sales metrics context. | These domain-specific facets are a stronger and more factual story than vague 'enterprise context' claims. |
Chart rendering | Inline chart generation using the chart facet and registered business chart sources. | Chart support is directly implemented and scoped to tenant or company context. |
Classification facet | Quality, type, and priority classification against configurable prompt rules. | This is a real structured classifier and feeds directly into user-query trigger logic. |
Multi-agent routing | Ask-facet routing to other agents, with mention and slash-command routing layered on top. | The routing story is real and richer than a single chatbot facade. |
@mentions and slash commands | Hidden mention and command facets route `@agent-name` and `/command` style inputs. | This is implemented behavior, not speculative product positioning. |
Actions with undo support | Company updates, industry updates, saved structured data, note creation, and Freshdesk ticket creation. | Several actions are auto-approved, and some explicitly support undo via stored undo data. |
Feedback and response helpers | Feedback buttons, copy-to-clipboard UI, related follow-up questions, and status indicators. | These response embellishments are actual facets in the renderer pipeline. |
Scheduled and query triggers | Hourly/daily/weekly schedule triggers plus user-query triggers with classification prompts, tenant targeting, and Run Now. | Trigger automation is a real feature family that deserves to be stated precisely. |
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.