Saved, fill-in-the-blank questions that give users a fast, consistent starting point.
Where a skill guides the assistant, a Prompt Template guides the user. It is a saved question with typed inputs. A user picks the template, fills in a few fields like a date range or a focus area, and the finished question is sent to the assistant. This keeps frequent analyses consistent and saves users from writing long requests.
The fields of a Prompt Template
| Field | Required | Purpose |
|---|---|---|
| Prompt ID | Yes | A unique identifier (lowercase letters, numbers, hyphens, underscores). |
| Title | Yes | The name users see when choosing a template. |
| Template Content | Yes | The question text, with placeholders for the user's inputs. |
| Description | No | A short explanation shown in the template list. |
| Category | No | A grouping such as Sales & CRM or Manufacturing. |
| Status | No | Draft (hidden) or Published (visible). |
| Visibility | No | Private, Shared, or Public. |
| Rendering style | No | How placeholders are filled in. The flexible style supports conditions and lists; the simple style does direct substitution. |
| Version, Use Count, Last Used | Read-only | Versioning and usage analytics. |
Template inputs (arguments)
Each template defines the inputs a user fills in. Inputs can be required or optional and can carry a default value.
| Input type | What the user sees |
|---|---|
| Text | A free-text box. |
| Number | A numeric value. |
| Yes / No | A simple toggle. |
| Choice | A dropdown with one selection. |
| Multi-choice | A dropdown allowing several selections. |
Each input also carries a display label, an optional help description, a required flag, an optional default, and, for choices, the list of allowed values.
Built-in templates and categories
The gateway ships with ready-to-use templates across common retail areas. Categories include Data Analysis, Sales & CRM, Purchasing, Manufacturing, HR & Payroll, Documentation, Data Quality, and System Administration.
| Template | Category | Inputs |
|---|---|---|
| Sales Analysis | Sales & CRM | Focus area (required); time period (default last month); include territory (yes/no). |
| CRM Analysis | Sales & CRM | Focus area (required); time period; include campaigns (yes/no). |
| Purchase Analysis | Purchasing | Focus area (required); time period; include inventory (yes/no). |
| Manufacturing Analysis | Manufacturing | Focus area (required); include quality (yes/no). |
| HR Analysis | HR & Payroll | Focus area (required); time period; include payroll (yes/no, needs payroll permission). |
| Document Type Documentation | Documentation | Document type name (required); include examples (yes/no). |
| Data Quality Audit | Data Quality | Document type name (required); time range (default all). |
How users run a template
-
The assistant offers the list of available templates the user can access.
-
The user picks one and fills in the inputs.
-
The finished question is sent to the assistant, which answers using the right tools and reports.
Versioning and system templates
Changes to a template's question, inputs, or rendering style create a new version automatically, so you keep a history you can review and restore. The built-in templates cannot be edited or deleted directly. To customize one, duplicate it as a private copy, change the copy, and publish that.