What you are trying to achieve is a valid and common scenario, but the issue you are facing comes from how Copilot Studio handles user input and state during a conversation.
In Copilot Studio, user responses are not automatically persisted and structured in a way that you can reliably reuse later (for example, to populate a Word template). You need to explicitly design how responses are captured, stored, and mapped.
Why it is not working today:
- The agent can ask questions dynamically, but generative responses are not automatically stored as structured data
- There is no automatic binding between “questions asked by the agent” and fields in a document template
- If you rely only on conversational flow, responses may be lost, overwritten, or not mapped consistently
Recommended pattern (supported approach)
You should move from “implicit conversation” to “explicit data capture”.
1) Capture each response into variables
Instead of relying on general conversation, define explicit questions and store each answer in a variable.
For example:
- Ask question → store answer in variable (e.g. CustomerName, ProjectDescription, etc.)
Important:
Each field in your Word template must have a dedicated variable.
2) Use structured topics or guided flow
Avoid fully dynamic questioning for this scenario. Instead:
- Use a guided topic or sequence of questions
- Map each question to a specific variable
This ensures deterministic behavior and avoids losing data.
3) Persist data if needed
If the interaction spans multiple turns or needs reliability:
- Store responses in Dataverse or another data source
- Or use global variables carefully to persist across the session
4) Generate the document via Power Automate
Copilot Studio is not designed for document rendering logic. The recommended approach is:
- Pass all collected variables to a Power Automate flow
- Use “Populate a Word template”
- Generate the document (and optionally convert to PDF)
- Return the file or link back to the agent
5) Pass data as a structured object
When calling the flow:
- Send all variables as a structured payload (JSON-like)
- Ensure field names match exactly the placeholders in the Word template
Key limitation to be aware of:
Copilot Studio does not automatically extract and bind conversational responses to template fields. This must be explicitly modeled using variables and flows.
Summary:
- Do not rely on free-form conversation to capture data
- Use explicit variables for each field
- Delegate document generation to Power Automate
Once you switch to this pattern, the scenario becomes stable and fully controllable.
