Recall Builder guides intake along the active repair branch

Supply mileage and the official recall source at intake

Recall Builder begins by requesting mileage in, mileage out and the official recall document. Paste the procedure text or attach a supported PDF or DOCX file. Analysis begins after the required intake information and source are provided.

The full document stays available as the basis for the conversation. This matters when a recall contains several inspection outcomes or conditional repair operations.

Follow questions that belong to the applicable procedure path

The assistant analyses the document as a conditional decision tree. Your confirmed inspection result or completed operation establishes which follow-up facts apply to the active repair branch.

• Clarifications are selected from the full procedure rather than an isolated excerpt.
• Incompatible repair paths are excluded once the applicable branch is established.
• Subsequent answers are considered alongside the source and earlier confirmed information.

For a procedure with alternate inspection outcomes, provide the actual result so the conversation can follow the corresponding operations. Do not select a repair path merely because it appears elsewhere in the document.

Complete mandatory campaign facts before finalization

Mileage remains required. If the selected procedure requires a resulting software version or a campaign completion label, Recall Builder requests that confirmation and will not finalize while it is missing.

Supply findings, measurements, software information, label application and any corrections requested for the applicable path. When that path is complete, the final recall narrative appears directly in the chat.

Use New Recall to clear the current in-memory conversation before starting with another source. The separate context-preservation update describes how later repair answers stay attached to an already selected option.