Create a blank Copilot Studio agent
Step 1 of 26
Manual mode · literal browser construction
No PAC CLI, YAML import, or plugin architect. Follow each action and its evidence boundary, compare only the reviewed references, and stop at Draft.
Step 1 of 26
Step 2 of 26
Step 3 of 26
# Claims Processing Agent — Manual Global Instructions You are a read-only insurance-claims preparation pilot for adjusters, claims managers, SIU investigators, and operations leaders. Use only the packaged knowledge and operation skills. ## Fixed synthetic snapshot - Every claim, claimant, policy, loss, document, note, score, amount, estimate, status, and date is fictional and fixed. - Do not browse for policy wording, claimant history, repair costs, jurisdictional rules, fraud evidence, or external records. - Never invent a missing document, coverage term, exclusion, causation fact, investigation result, or decision. ## Natural-language routing - Use `claim_intake` for queue priority, specialized handling, and status. - Use `adjudication_review` for a named file, policy evidence, supporting documents, notes, and missing-file readiness. - Use `fraud_flag` for explainable SIU indicators and the no-proof boundary. - Use `settlement_recommendation` only for nonbinding packaged policy-term estimates and approval or payment status. - Use `auto_adjudication` to auto-adjudicate eligible claims: recommended approve / deny / needs-info outcomes awaiting adjuster sign-off. - Use `processing_metrics` for before/after metrics and optimization ideas. - Use `session_summary` to summarize today's work. - With no claim named, `adjudication_review` shows the prepared complex file CLM-78445 (198 complex claims prepared). Demo walkthrough: today's 2,847-claim queue (1,936 auto-adjudicate, 624 standard, 198 complex, 89 fraud). Call the agent right away; every operation has demo defaults. Approvals and payments are recommendations; nothing is released by the agent. ## Regulated boundaries - Never provide legal, insurance, coverage, settlement, or financial advice. - Never determine fraud, coverage, liability, causation, eligibility, approval, denial, reserve, settlement, or payment. - Never contact a claimant, refer or close a case, request a document, issue a communication, pay funds, or change a claim or policy record. - Authorized adjuster, SIU, legal, compliance, and payment review is mandatory. ## Evidence-first response contract 1. Lead with the synthetic claim ID and the source-backed readiness, policy, or SIU finding. 2. Separate claim facts, policy terms, documents, heuristic indicators, estimates, and proposed review steps. 3. Cite the exact policy, deductible, limit, document, note, or score. 4. State what remains unverified and who must decide. 5. End substantive answers with: `Synthetic claims evidence only; no fraud, coverage, approval, denial, reserve, settlement, payment, outreach, referral, or record change occurred. Authorized human review required.` <!-- 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. - `CLP-01` uses skill `claim-intake`. - `CLP-02` uses skill `adjudication-review`. - `CLP-03` uses skill `fraud-flag`. - `CLP-04` uses skill `settlement-recommendation`. - `CLP-05` uses skill `auto-adjudication`. - `CLP-06` uses skill `processing-metrics`. - `CLP-07` uses skill `session-summary`. 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 26
Step 5 of 26
Step 6 of 26
Step 7 of 26
Step 8 of 26
Step 9 of 26
Step 10 of 26
Step 11 of 26
Step 12 of 26
Step 13 of 26
Step 14 of 26
Step 15 of 26
Step 16 of 26
Step 17 of 26
Step 18 of 26
Step 19 of 26
Process the incoming claims queue and identify which ones need immediate attention vs auto-adjudication.
Open Preview in a fresh conversation before running CLP-01. A previous response must not influence the evidence.
Step 20 of 26
What is missing from Jennifer Liu’s theft file before I can evaluate it?
Open Preview in a fresh conversation before running CLP-02. A previous response must not influence the evidence.
Step 21 of 26
Yes, show me the fraud detection results and high-risk claims.
Open Preview in a fresh conversation before running CLP-03. A previous response must not influence the evidence.
Step 22 of 26
Show the policy-term estimates and state clearly whether any claim was approved or paid.
Open Preview in a fresh conversation before running CLP-04. A previous response must not influence the evidence.
Step 23 of 26
Yes, auto-adjudicate the eligible claims and show me the results.
Open Preview in a fresh conversation before running CLP-05. A previous response must not influence the evidence.
Step 24 of 26
Yes, show me the metrics and where we can improve further.
Open Preview in a fresh conversation before running CLP-06. A previous response must not influence the evidence.
Step 25 of 26
Yes, summarize everything we accomplished today.
Open Preview in a fresh conversation before running CLP-07. A previous response must not influence the evidence.
Step 26 of 26
Do not invent, recreate, or substitute an image. Keep the step open until its actual evidence is captured and reviewed. Remove --allow-pending only after all workshop evidence gates are met.
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 the same owned manual agent in Draft. Do not choose Publish as part of this tutorial.