Use a procedure that moves from clarification to an authorized resource, then to a bounded response and confirmation. A drafted reply, a sent reply, and a resolved preparation question are different records. Keep them distinct.
Clarify the missing instruction before choosing a guide
Zapier's published customer-service SOP example describes clarifying inquiries, consulting accurate information, escalating unresolved requests, and following up. The narrower procedure below applies those ideas to an original workshop-guide inquiry. It does not copy the linked template or promise a particular customer outcome. Zapier's customer-service SOP example
For fictional inquiry Q1, record the customer's request as “I cannot find the preparation guide.” Add fields for workshop name, session date, expected format, what they already tried, and the part of preparation they need explained. The session date is initially unknown. Keep that field unknown instead of assuming the next event on your calendar.
A complete clarification draft is:
Which workshop and session date are you preparing for? What format are you looking for, and where have you already tried to find the guide? Please also tell us which preparation instruction you need help locating.
This draft has not been sent. It asks for the information needed to select a resource without supplying a guessed guide or requesting unnecessary personal details.
Match the confirmed request against an authorized list
The original demonstration list contains two resource records:
| Resource ID | Workshop | Session date | Available format |
|---|---|---|---|
| GuideA | Workshop A | October 20, 2026 | |
| GuideB | Workshop B | November 3, 2026 | DOCX |
These are illustrative IDs, not working download links. In an actual procedure, attach the authorized resource location, version, and evidence that it belongs to the session. Supply and test any real URL before using it in a customer message.
If Q1 is clarified as Workshop B on November 3 with DOCX requested, GuideB matches all three fields. If the customer requests PDF instead, the listed DOCX guide does not satisfy that format request. Record the mismatch and route it to the actual role authorized to provide an alternative. Keep that role [TO CONFIRM] until your organization supplies it. Do not rename a DOCX file as PDF or invent a policy allowing conversion.
Write a response that stops at what is known
For the clarified Workshop B/DOCX case, use this complete review draft:
The authorized preparation resource listed for Workshop B on November 3, 2026 is GuideB in DOCX format. Please confirm whether it opens in the format you need and whether it answers your preparation question. If it does not, tell us what remains unclear so we can route that request appropriately.
This is a demonstration response for review, not a ready-to-send attachment message: no actual file or tested location has been supplied. Before sending in the real workflow, include the verified resource through your approved delivery method. Avoid wording such as “attached” or “download here” until the attachment or link actually exists and has been checked.
For the PDF mismatch, the escalation draft is:
The request is for Workshop B on November 3, 2026 in PDF format. The authorized list currently supplies GuideB as DOCX. Please confirm whether an authorized PDF alternative is available and how it may be provided. No alternative has been promised to the customer.
Keep the actual escalation owner, accepted next step, and return timing blank until confirmed. The procedure does not create a refund, account-access, or format-conversion policy.
Follow up on the preparation question
The maintained ticket should retain Q1's clarified fields, matched resource ID and version, draft, actual sent evidence if any, customer response, and remaining question. A sent timestamp proves dispatch only. With no customer response, label the case “Awaiting confirmation” rather than marking the question resolved automatically.
Ask whether the resource opened and addressed the preparation need. If either answer is no, preserve the new information and route the remaining issue. Close the inquiry according to the actual team's confirmation procedure, with the evidence that supports the decision. A review sheet can show the missing-input and matched-resource branches without collecting customer data or sending anything.
Copy this prompt for the inquiry procedure
Create one complete, self-contained US-English HTML companion for “Customer service • preparation guide SOP”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Select text; B · DOCX; B · PDF; Unclarified Q1. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Write a complete US English customer service SOP for a workshop preparation-guide inquiry. Include roles to confirm, intake fields, decision branches, complete clarification/response/escalation drafts and a follow-up evidence record. Keep all example data fictional. Q1: I cannot find the preparation guide. Workshop/session date/expected format need clarification; date initially unknown. Ask what the customer already tried and which preparation instruction they need. No guessed guide. Authorized illustrative list: GuideA, Workshop A, October20,2026,PDF; GuideB, Workshop B,November3,2026,DOCX. Use resource IDs,not fake working links. Actual resource/version/location must be supplied and any URL tested before real sending. For confirmed Workshop B/November3/DOCX, match GuideB. For PDF requested, record mismatch and escalate to actual authorized alternative-resource role TO CONFIRM. Do not manufacture a PDF,rename formats,invent policy or promise an alternative. Draft response names exact resource/session/format and asks whether it opens and answers the preparation question. It is a review draft,not an actually attached/sent file. Separate draft,sent evidence,customer confirmation and remaining question. Actual confirmation/owner/return timing remain blank. Sent without response is awaiting confirmation,not automatic resolution. Keep maintained ticket outside the review copy. Proposed HTML branch/draft views preserve missinginputs/resource match/blankconfirmation and require construction/testing. No send button,resolution checkbox,actual customer data,refund/account access or guaranteed result.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# A Customer Service SOP Template for Matching the Right Resource to the Request
“I cannot find the preparation guide” sounds like a request you can answer by sending a link. But which workshop does the customer mean, and which date and format do they need? Sending the first guide you find can create a second problem while making the ticket look handled.
Use a procedure that moves from clarification to an authorized resource, then to a bounded response and confirmation. A drafted reply, a sent reply, and a resolved preparation question are different records. Keep them distinct.
## Clarify the missing instruction before choosing a guide
Zapier's published customer-service SOP example describes clarifying inquiries, consulting accurate information, escalating unresolved requests, and following up. The narrower procedure below applies those ideas to an original workshop-guide inquiry. It does not copy the linked template or promise a particular customer outcome. [Zapier's customer-service SOP example](https://zapier.com/blog/sop-template/)
For fictional inquiry Q1, record the customer's request as “I cannot find the preparation guide.” Add fields for workshop name, session date, expected format, what they already tried, and the part of preparation they need explained. The session date is initially unknown. Keep that field unknown instead of assuming the next event on your calendar.
A complete clarification draft is:
> Which workshop and session date are you preparing for? What format are you looking for, and where have you already tried to find the guide? Please also tell us which preparation instruction you need help locating.
This draft has not been sent. It asks for the information needed to select a resource without supplying a guessed guide or requesting unnecessary personal details.
## Match the confirmed request against an authorized list
The original demonstration list contains two resource records:
| Resource ID | Workshop | Session date | Available format |
| --- | --- | --- | --- |
| GuideA | Workshop A | October 20, 2026 | PDF |
| GuideB | Workshop B | November 3, 2026 | DOCX |
These are illustrative IDs, not working download links. In an actual procedure, attach the authorized resource location, version, and evidence that it belongs to the session. Supply and test any real URL before using it in a customer message.
If Q1 is clarified as Workshop B on November 3 with DOCX requested, GuideB matches all three fields. If the customer requests PDF instead, the listed DOCX guide does not satisfy that format request. Record the mismatch and route it to the actual role authorized to provide an alternative. Keep that role `[TO CONFIRM]` until your organization supplies it. Do not rename a DOCX file as PDF or invent a policy allowing conversion.
## Write a response that stops at what is known
For the clarified Workshop B/DOCX case, use this complete review draft:
> The authorized preparation resource listed for Workshop B on November 3, 2026 is GuideB in DOCX format. Please confirm whether it opens in the format you need and whether it answers your preparation question. If it does not, tell us what remains unclear so we can route that request appropriately.
This is a demonstration response for review, not a ready-to-send attachment message: no actual file or tested location has been supplied. Before sending in the real workflow, include the verified resource through your approved delivery method. Avoid wording such as “attached” or “download here” until the attachment or link actually exists and has been checked.
For the PDF mismatch, the escalation draft is:
> The request is for Workshop B on November 3, 2026 in PDF format. The authorized list currently supplies GuideB as DOCX. Please confirm whether an authorized PDF alternative is available and how it may be provided. No alternative has been promised to the customer.
Keep the actual escalation owner, accepted next step, and return timing blank until confirmed. The procedure does not create a refund, account-access, or format-conversion policy.
## Follow up on the preparation question
The maintained ticket should retain Q1's clarified fields, matched resource ID and version, draft, actual sent evidence if any, customer response, and remaining question. A sent timestamp proves dispatch only. With no customer response, label the case “Awaiting confirmation” rather than marking the question resolved automatically.
Ask whether the resource opened and addressed the preparation need. If either answer is no, preserve the new information and route the remaining issue. Close the inquiry according to the actual team's confirmation procedure, with the evidence that supports the decision. A review sheet can show the missing-input and matched-resource branches without collecting customer data or sending anything.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review the decision branches
Use the HTML companion to check that the missing date prevents a resource choice and that the matched branch preserves the requested format. Keep actual tickets, files, delivery, and customer confirmations in the approved service workflow.
Finish with the exact resource matched to a clarified request, or a specific unresolved mismatch assigned for follow-up; a reply alone should never conceal the customer's remaining question.