Evidence-grounded customer journey
Build this agent step by step, then show it to a customer. Easy mode lets AI do the clicks; Manual mode shows every step yourself.
Self-paced local achievements
0 of 0 Easy checkpoints complete
These points and badges are local, self-reported workshop progress—not externally verified proof or a capability claim.
This opens one prefilled progress issue containing every badge currently earned here. Nothing syncs until you submit it. Resubmitting later merges newly earned badge IDs without duplicate score, and one public issue submission opts your GitHub account into a public verified profile.
Workshop setup
Start in GitHub Copilot Chat. No Frontier desktop app is required; the Easy Mode skill handles any additional setup.
GitHub Copilot Chat is open in VS Code, signed in, and set to Agent mode.
Prepare your Copilot
One skill owns discovery, testing, Draft deployment, and Preview validation.
Go and read https://raw.githubusercontent.com/microsoft/aibast-agents-library/main/skills/aibast-easy-mode/SKILL.md and run the First-Time Fix workshop for me.
Copilot says it has read the skill and is running the workshop. The skill owns the remaining setup and validation.
Prove the solution locally
This step proves the portable business logic before any Copilot Studio work begins. The harness retrieves the immutable package, verifies the source, loads the agent, and runs every locked case.
Give me First-Time Fix using Easy Mode and test it for me.
Copilot reports a verified source and 4/4 locked local cases passed.
Copilot should end by suggesting the next message: Deploy it into Copilot Studio for me.
Create the reviewed Draft
The harness now uses the verified Microsoft Copilot Studio plugin to reuse or create the source-controlled Draft, synchronize the reviewed instructions and assets, validate the PAC project, and leave publication off.
Deploy it into Copilot Studio for me.
First-Time Fix ManualClaude Opus 5.524falseThe harness then validates the real Preview front door before returning its final verdict.
Verify the real experience
The harness already runs these checks automatically. Repeat them here so you understand what was proven and can recognize a correct result yourself.
Every case passes in a fresh Preview conversation, and the agent still appears as Draft.
FTF-01 · Contact Center Agent
The customer on Alder Grove Service keeps dropping. What guided fix should I walk them through right now?
FTF-02 · Contact Center Agent
Is there any network work near Meadow Lane that could explain the outage?
FTF-03 · Field Service Dispatcher
What did the last technician find at Alder Grove Service?
FTF-04 · Field Service Dispatcher
If the light stays red, which technician should go to Alder Grove and what should they prepare? Don't book it yet.
Recognize completion
The workshop is complete only when both the portable agent and the Copilot Studio front door prove the same behavior.
The harness reports status: complete, exact case totals, the Draft identity, and published: false. The module ends here; it does not offer publication.
| What you see | What it means | What to do |
|---|---|---|
| Copilot ignores the workshop | The wrong skill was read, or the chat began before the one line was sent. | Start a new Agent-mode chat and send the one line first. |
| Local validation is not 4/4 | The portable source, package, or locked behavior does not match. | Stop. Do not deploy. Let the harness report the exact failed case and marker. |
| No active Copilot Studio environment | PAC has no selected environment. | Sign in or select the intended environment, then resend the deploy message. |
| The Draft already exists | The recorded schema is already in the environment. | The harness should clone and reconnect automatically. Treat an attendee choice prompt as a harness defect. |
| A Preview case misses a marker | The real front door does not match the reviewed contract. | Keep the case failed. Inspect instructions and assets; do not retry until it happens to pass. |
| The agent is Published | The workshop crossed its safety boundary. | Stop immediately. The module must end at Draft with published: false. |
These links support audit, troubleshooting, and offline delivery. They are not learner steps.
Manual mode · see how it was built
Optional. Easy mode already did all of this for you from one skill file. This path replays every action the AI took, one real browser frame per step, so you can understand the agent before you adapt it. No PAC CLI, YAML import, or plugin architect; stop at Draft.
Manual-mode progress is saved on this device and contributes to the same achievement profile.
Step 1 of 18
Step 2 of 18
First-Time Fix Manual
Step 3 of 18
# First-Time Fix — Manual Global Instructions You are a synthetic first-call resolution pilot for a broadband provider's contact center and field service team. Explain the fixed service snapshot and prepare reviewable drafts without booking a visit, changing a service, or contacting a customer. ## Fixed synthetic snapshot - Use only the uploaded First-Time Fix synthetic records, rules, and four packaged skills. - The broadband provider and every service, plan, cabinet, case, network work record, visit, technician, slot, and booking draft are invented. - Do not browse, consult external sources, or add current-date, market, legal, or customer facts. Never invent a record, value, deadline, decision, or transaction. - Never match a fictional organization, person, or record to a real one or claim access to a live system. ## Natural-language routing - Use **guided connection fix** for: a contact center agent asks which fix to walk the customer through during the call, or what the service status is. - Use **local work check** for: the agent asks whether planned or emergency network work near the service could explain the issue. - Use **previous visit review** for: someone asks what earlier technician visits found or what the technician notes say. - Use **technician booking draft** for: someone asks which technician to send and what job preparation is needed; returns a booking draft that is never booked. ## Human and side-effect gates - Never book, change, or cancel a visit, change a service, dispatch a technician, update a case, or contact a customer. - Every decision stays with authorized contact center agents and field service dispatchers. Present drafts as drafts. - Include only the evidence needed for the question. ## Evidence-first response contract 1. Lead with the specific figure, record, or draft status that answers the question. 2. Keep the agent's tables and figures exactly as returned; do not round or recompute. 3. State the recommended next step and who decides it. 4. Make the no-action boundary explicit; never speculate. 5. End substantive answers with: **Synthetic broadband evidence only. No visit was booked, no service or case was changed, and no customer was contacted.** <!-- locked-preview-anchors:start --> ## Skill routing map Route from the user's natural-language intent to the correct skill below. Do not narrate internal retrieval, tool selection, restrictions, or implementation mechanics; present only the user-facing result. - `FTF-01` uses skill `guided-fix`. - `FTF-02` uses skill `local-work-check`. - `FTF-03` uses skill `visit-history`. - `FTF-04` uses skill `technician-booking`. These skill names above are the ONLY valid skill identifiers. Never invent, guess, or reference any other skill name. If the correct skill or its knowledge cannot be loaded after one retry in the same turn, say so honestly and stop. Do not answer using values you already know from these instructions or from general knowledge -- a response with no real citation is not acceptable output. <!-- locked-preview-anchors:end -->
Step 4 of 18
Step 5 of 18
Step 6 of 18
Step 7 of 18
Step 8 of 18
Step 9 of 18
Step 10 of 18
Step 11 of 18
Step 12 of 18
Step 13 of 18
Step 14 of 18
The customer on Alder Grove Service keeps dropping. What guided fix should I walk them through right now?
Open Preview in a fresh conversation before running FTF-01. A previous response must not influence the evidence.
Step 15 of 18
Is there any network work near Meadow Lane that could explain the outage?
Open Preview in a fresh conversation before running FTF-02. A previous response must not influence the evidence.
Step 16 of 18
What did the last technician find at Alder Grove Service?
Open Preview in a fresh conversation before running FTF-03. A previous response must not influence the evidence.
Step 17 of 18
If the light stays red, which technician should go to Alder Grove and what should they prepare? Don't book it yet.
Open Preview in a fresh conversation before running FTF-04. A previous response must not influence the evidence.
Step 18 of 18
Stop. Do not invent, recreate, or substitute an image. Capture the real frame, update the browserfilm manifest, and regenerate without --allow-pending.
Wait for ingestion to finish before Preview. A partial answer is not evidence.
Use the linked raw SKILL.md. Fix the reviewed source deliberately; do not silently skip the action.
Record the substitution and stop the parity claim until Easy and Manual use the same reviewed model.
Mark the recorded case failed, inspect instructions and inventory, then replay the exact prompt in a fresh conversation.
No. Keep this manual duplicate in Draft unless publication is separately approved. Do not choose Publish as part of this tutorial.
