Use this field-by-field template to collect product identity, the selected part, quantities and the evidence needed for confirmation.
A message saying “send the broken plastic piece” can trigger several exchanges before anyone can confirm the product or part. A complete request separates observed evidence from assumptions.
Use the following fields as a copyable starting point for your intake form or support message. Leave unknown values explicitly unknown. The template prepares a request; it does not certify compatibility or authorize a substitution.
Product brand: [brand]. Model: [exact model]. Serial number: [serial or unreadable]. Product revision or purchase information: [if known]. Label photograph: [attachment]. Console or accessory identity: [if relevant]. Include the actual label rather than only the name used on a sales listing.
Part description: [plain-language name]. Official part number: [confirmed reference or unknown]. Diagram title and revision: [source]. Illustration callout: [position]. Side or variant: [left/right/configuration]. Quantity needed: [quantity]. Keep the callout and orderable reference in separate fields; item 12 may not be the supplier’s part number.
Reason: [missing, damaged, worn, incorrect item or other]. Photo of the component in context: [attachment]. Close-up: [attachment]. Observed issue: [what the user sees]. Avoid turning an observation into a diagnosis. “The cover is cracked” is useful evidence; “the motor must be faulty” may be an unconfirmed inference.
Ask for the product label and a contextual photo before proposing a reference.
Confirm model applicability and preserve the diagram version.
Include the selected component and a precise action for the receiving team.
Mark it unknown and include the product label, diagram callout and photos. The request can ask a supplier to identify the component before quoting or ordering.
Require it when the manufacturer uses serial ranges to determine compatibility. Otherwise, explain which alternate evidence the receiving team can use and how uncertain identity is handled.
Yes. The fields are a starting point for an intake form or message. Connecting a visual selector to the form is a separate implementation decision.
The selected part and source context can be used to design a more complete handoff. Agree which fields should transfer and which still need buyer or supplier confirmation during the pilot.
Send the approved manual, diagrams or photos you already have. Request a free guide demo so your team can review one product task before deciding how to expand it.
Compatibility status: [confirmed by source / needs confirmation]. Requested action: [identify part / confirm compatibility / quote / check availability / request service]. Proposed replacement or substitution: [none unless approved]. If a reference is superseded, ask whether the replacement requires other components or a different procedure.
Requester: [name and team]. Contact: [preferred channel]. Existing order or ticket: [reference]. Delivery region: [region]. Required date: [if relevant]. Collect full shipping details only when necessary for the next step. Keep account and personal information out of publicly shareable part-view links.
Illustrative request: “Please identify the left side panel shown in callout B of the supplied assembly manual. The model label photo and a photo of the damage are attached. The order reference is included privately. I need one panel; the supplier part number is unknown. Please confirm the reference and whether a replacement panel is available.” No invented supplier code is needed to make this request actionable.
