The Instruction Manual Policy

When to use it

Select this policy for any document containing assembly instructions, user manuals, maintenance procedures, setup guides, or troubleshooting documents.

How the Manual Policy Protects Your Data

1. Actionable Sequencing (Preserving Order)

The most critical failure of a Support Agent is giving a customer Step 3 before Step 1. This policy actively looks for setup, operation, and maintenance instructions and forces them into strict numbered lists. It preserves the chronological sequence of the original document, ensuring the AI agent guides the user step-by-step without hallucinating the order of operations.

2. Troubleshooting Extraction

Manuals often bury the "FAQ" or "Troubleshooting" sections at the very end. The policy actively hunts for these sections—the "If X happens, do Y" logic—and structures them into clear problem/solution pairings, making them highly retrievable for customer support queries.

3. Noise Reduction

To optimize the context window and lower token costs, the policy aggressively strips out metadata that is useless to an LLM:

• Table of Contents: TOCs and page numbers confuse LLMs and pollute vector searches. The policy deletes them entirely.
• Financials & Inventory: Even though manuals shouldn't contain pricing or stock levels, the policy acts as a firewall. If it finds any, it redacts them to maintain separation of concerns.

4. Smart Identifier Mapping (The "SKU" Anchor)

Just like our other policies, this engine anchors the manual to a specific product ID. It scans the document to find the primary identifier, allowing your workflow to link this manual directly to a specific product in your database.

• Priority 1: Searches for 'Item' or 'Item Number'.
• Priority 2: If absent, searches for 'Model' or 'Item ID'.
• Fallback: Defaults to the most prominent product name on the manual's cover or title.

5. Pure Transcription

Technical instructions must be exact. The policy is strictly forbidden from rewriting, paraphrasing, or interpreting the instructions. It copies the exact terminology, warnings, and formatting of the source data so the agent's advice is technically sound and legally compliant.

What the Output Looks Like

When your n8n workflow retrieves instructions, it receives a perfectly sequenced Markdown document, completely free of PDF formatting artifacts.

# Model: X500-Pro

## Setup Instructions
1. Unbox the device and locate the primary power cable (Part A).
2. Connect the power cable to the rear terminal before turning on the device.
3. Press and hold the power button for 5 seconds until the LED indicator flashes blue.
4. Download the companion app to complete the Wi-Fi pairing process.

## Troubleshooting
**Issue: The LED indicator is flashing red.**
- Ensure the battery is fully inserted.
- Check the rear terminal for dust or debris.
- If the issue persists, perform a hard reset by holding the power button for 15 seconds.

**Issue: Device will not connect to Wi-Fi.**
- Verify your router is broadcasting a 2.4GHz network. The device does not support 5GHz networks.

Why This Matters for Automation Developers

By applying the Instruction Manual Policy during ingestion, you drastically improve the performance of Technical Support agents:

• Improved Chunking: Because we strip the Table of Contents and convert the layout into linear Markdown headings, your Vector DB chunks the data logically by section, rather than randomly splitting a sentence across two columns.
• Step-by-Step Reliability: By forcing numbered lists, the LLM is naturally prompted to deliver step-by-step instructions to the user in the exact order intended by the manufacturer.
• Ease of Use: You do not need to build complex OCR pipelines or Python scripts to clean up messy PDF manual layouts. We hand you clean data.