Sometimes a chat is not the right place to finish a task. A visitor might start by talking to your Copilot Studio agent, but the task ends in a form, maybe because the form has legal text, a signature, or fields that are easier to review on screen. The smart move is to have the agent collect what it can during the chat, then send the visitor to a form that is already filled in with those details. They just check it and submit. In this guide I will show you how to pre-fill Power Pages forms with data the agent gathered.
Why Pre-Fill a Form at All
Asking a visitor to type the same information twice is a quick way to annoy them. If the agent already learned their name, their reason for the request, and other details during the chat, making them retype all of it into a form feels pointless. Pre-filling solves this. The agent passes what it collected into the form, so the visitor sees those fields already done.
This makes the whole experience faster and friendlier. The visitor moves from chat to form without losing their place, and they only have to handle the parts the agent could not collect. Less typing means fewer drop-offs and happier visitors.
How the Hand-Off Works
The idea is a clean hand-off from the chat to the form. During the conversation, the agent gathers details and stores them. When it is time to move to the form, the agent sends the visitor to the form’s page and passes the collected details along. The form reads those details and fills in the matching fields. The visitor lands on a form that already knows a lot about their request.
So the agent collects, the page carries the data over, and the form displays it. The visitor experiences one smooth journey instead of two disconnected steps.
Step One: Collect the Data in the Agent
Start in Copilot Studio by building the part of the conversation that gathers the details. Use Question nodes to ask for each piece of information the form will need, and store each answer in a clearly named variable. Ask one thing at a time and keep the tone friendly, so it feels like a helpful chat rather than an interrogation.
Only collect what makes sense to collect in chat. Some fields are better left for the form, like long text or things the visitor needs to read carefully. Focus the agent on the details that are quick and natural to gather in conversation.
Step Two: Pass the Data to the Form Page
When the agent is ready to send the visitor to the form, it passes the collected details along to the form’s page. A common way to carry small pieces of information from one page to another is through the web address, by adding the values as parameters on the link. The agent sends the visitor to the form using a link that includes the details it gathered.
This means the form page receives the information the moment it loads. The values travel along with the visitor as they move from the chat to the form, ready to be placed into the right fields.
Step Three: Fill the Form Fields
On the form page, you read the incoming values and place them into the matching fields. Power Pages can read values from the web address and use them to set field values when the form loads. So the field for name gets the name the agent collected, the field for the reason gets the reason, and so on. By the time the visitor sees the form, those fields are already filled.
Map each incoming value to the correct field carefully. A mismatch here puts the right data in the wrong box, which confuses the visitor. Take the time to line them up properly so the form looks exactly right.
Step Four: Let the Visitor Review and Submit
The point of pre-filling is to save effort, not to remove control. So always let the visitor review the filled-in form before they submit. They can check that everything is correct, fix anything that needs changing, and complete any fields the agent did not collect. Then they submit, just like a normal form.
This review step matters. It gives the visitor confidence that the information is right, and it catches any detail the agent might have misheard. The result is a form that is mostly done but still fully in the visitor’s hands.
Keep It Secure
Passing data between a chat and a form means handling personal details, so be careful. Avoid putting sensitive information where it does not belong, and remember that values carried in a web address are not the place for anything secret. For signed-in users, you can rely on what the site already knows instead of passing private details around. And respect your table permissions and form rules throughout.
A little care here keeps the convenience of pre-filling from turning into a privacy problem.
Test the Whole Journey
Before launch, walk through the full path. Chat with the agent, let it collect the details, and follow the link to the form. Confirm that every field is filled with the right value in the right place. Change a field to make sure the review step works, and submit to check that the record saves correctly.
Try it with different answers to make sure the mapping holds up. Test signed in and signed out if that applies. A few careful runs confirm that the hand-off from chat to form feels seamless for your visitors.
Wrapping Up
Pre-filling Power Pages forms with data from a Copilot Studio agent gives your visitors a smooth path from chat to completed form. The agent collects the easy details, passes them to the form page, and the form shows up already filled in. The visitor reviews, finishes any extra fields, and submits. Keep the data secure, map the fields carefully, and test the whole journey. Do this and you spare your visitors the pain of typing the same thing twice, turning two steps into one effortless flow.