Summarise a claims process page
Use selected browser sources to summarise a claims process page. DeepShell assists with summarise work; you prepare the inputs, verify the evidence, and complete any external action.
Before you start
Inputs: Insurer claims-process page.
Define: the audience, date or version, comparison criteria, and intended destination.
Access: open the sources yourself and select only content you are authorised to send to a model provider. Inaccessible or unselected pages are outside the task.
The process, step by step
- 1You complete
Prepare insurer claims-process page. Confirm you can share the selected material with a model provider.
- 2You complete
Open the relevant pages or attachments, select the sources in the panel, and set the scope. Log in or navigate to any required pages yourself.
- 3DeepShell assists
Summarise the material for the stated audience while retaining caveats. Request: Step, Required document, Deadline, Contact channel, Source.
- 4You complete
Check that exceptions, limitations, dates, and important minority findings remain represented.
- 5You complete
Copy or export the reviewed result, then update the destination system yourself if needed.
Requires another tool: sending, publishing, form submission, CRM updates, purchases, and schedules are outside this extension workflow. Use the destination application yourself.
Your reusable workflow pack
Replace bracketed fields before use. Keep the sources and output together for the next reviewer.
Reusable prompt
Task: Summarise a claims process page. Use only these selected sources: Insurer claims-process page. Audience: [add the intended reader]. Scope: [add dates, criteria, versions, or exclusions]. Return these fields or sections: Step, Required document, Deadline, Contact channel, Source. Cite the source and page or section for factual statements. Mark missing information as "Not stated". Separate facts from assumptions. Do not invent figures, decisions, or events. Finish with unresolved questions and a review checklist. Do not send, submit, purchase, or update another system.
Output template
Step: [fill from the selected source; otherwise Not stated] Required document: [fill from the selected source; otherwise Not stated] Deadline: [fill from the selected source; otherwise Not stated] Contact channel: [fill from the selected source; otherwise Not stated] Source: [fill from the selected source; otherwise Not stated]
Output structure
Step / Required document / Deadline / Contact channel / Source
- 01Step: [source-grounded step]
- 02Required document: [source-grounded required document]
- 03Deadline: [source-grounded deadline]
- 04Contact channel: [source-grounded contact channel]
- 05Source: [source-grounded source]
Review, then complete the process
- Check that exceptions, limitations, dates, and important minority findings remain represented.
- Have the appropriate domain professional review the original material and the output before acting on it.
- Every material claim has a source you can open and inspect.
- Missing information is explicitly marked; no placeholders remain in the final deliverable.
- A named person has approved the result before it is shared or used.
Copy or export the reviewed result, then update the destination system yourself if needed.
Done means: the intended reviewer can trace the result to its sources, all missing details are resolved or explicitly flagged, and any external action has been completed by an authorised person.
If the result is incomplete
Check source selection and access first. Narrow the question, specify the missing field, or supply an authorised source. For long or scanned documents, verify that the relevant text is readable. If evidence is still missing, record the gap rather than accepting an invented answer.
Time, cost, and validation
No measured run time, cost benchmark, or end-to-end extension test is recorded for this guide. Actual cost depends on source length, model, and retries. Use the settled receipt from a real run; do not treat the example as a performance promise.
Practical questions
What should I prepare?
Insurer claims-process page. Define the audience, scope, and required fields before you start.
Which steps are automated?
Summarise the material for the stated audience while retaining caveats. Source selection, review, and any sending, submission, or system update remain your responsibility.
What if the source is incomplete?
Keep missing values marked as Not stated. Add an authorised source or narrow the task; do not ask the model to fill gaps with plausible facts.
Has this workflow been tested in the extension?
This is an illustrative process guide. No end-to-end extension test or measured cost benchmark is recorded for this guide.