I recommend experimenting with prompt variations in a non-production environment to better understand what Copilot can generate based on the available record and transcript data. This helps clarify both the strengths and the practical boundaries of the platform-managed grounding model.
You can also use Copilot prompt plugins, which fundamentally shift AI from a configurable feature to a programmable capability. They are built as tools in Copilot Studio that Copilot can invoke at runtime to fetch data, transform it, and return it to the agent experience.
In practice, a prompt plugin is designed as a structured interaction between Copilot and your underlying data landscape. It starts with clearly defined inputs; parameters that Copilot supplies at runtime, such as the active case ID, customer context, or extracted keywords from the conversation. Based on these inputs, the plugin performs targeted data retrieval. This can involve querying Dataverse tables, calling external systems through standard or custom connectors, or orchestrating multiple data sources to assemble the required context.
Before invoking the language model, the retrieved data is typically shaped through business logic. This may include filtering irrelevant records, aggregating related information, calculating derived values, or applying predefined business rules. The goal is to inject curated, high-quality context into the prompt rather than raw, unstructured data.
Finally, the plugin defines an explicit output schema. This determines what Copilot receives back and how the response is structured, whether as formatted text, tagged sections, or machine-readable JSON designed for downstream automation.
Unlike default or admin-configured prompts, plugins allow you to specify output formats such as:
- JSON schemas
- Tagged sections
- Machine-readable output
- Decision trees
- Confidence scoring
This makes plugin-based prompts suitable not only for human-readable responses, but also for downstream automation and orchestration scenarios.
When a prompt plugin is created in Copilot Studio and made available to Customer Service, it appears in the Copilot Service Admin Center in a disabled state. Administrators must explicitly enable it under Productivity → Plugins for generative AI before it becomes available to service representatives.
