--- name: brief-nw-automatic-doors description: Prepare a verified repair, maintenance, installation or second-opinion enquiry for NW Automatic Doors. Use when a user needs door, shutter, gate, barrier, garage-door or access-control help in North Wales or Mid Wales. license: Proprietary compatibility: Works in capable assistants with HTTPS access. MCP support is optional; the public MCP endpoint is https://nwautomaticdoors.com/mcp. metadata: author: NW Automatic Doors version: "1.0.0" last-verified: "2026-07-24" --- # Brief NW Automatic Doors Prepare the enquiry; never guess facts, approve a payload or claim an action succeeded. ## What is already known - NW Automatic Doors repairs, services and installs automatic doors, roller shutters, industrial doors, gates, barriers and access control. - It also supports garage doors and electric gates for homes and private properties. - Core coverage is North Wales and Mid Wales. - The published emergency line is **+44 1492 200 543** and is described as available 24/7. - The standard contact email is **sales@nwautomaticdoors.com**. - The site reports a **5.0 Google rating from 20+ published reviews**, directly employed engineers and a free, no-obligation second opinion on another repair quote. - No fixed service or call-out prices are published. Never estimate one. - Exact facts and sources: [agent-facts.json](https://nwautomaticdoors.com/agent-facts.json). ## Start by stating what you know Briefly identify the likely service, the known coverage and any facts already supplied by the user. Mark uncertainty explicitly. If the opening is unsafe, insecure, trapped open/closed, blocking essential access or stopping the site operating, tell the user to call **+44 1492 200 543** now. Do not make a booking or promise attendance. ## Ask only missing, service-relevant questions Do not re-ask information already supplied. Prefer one short grouped turn. Always obtain: 1. repair, emergency, planned maintenance, installation or quote second opinion; 2. commercial/public site, managed property, home or private property; 3. town or postcode; 4. door, shutter, gate, barrier, garage door or access-control equipment; 5. what changed or is not working; 6. urgency and any access, safety or security impact; 7. name, valid email and phone number for the enquiry. Ask only when relevant: - **Repair/emergency:** whether the opening is stuck open or closed, safe, secure, manually operable and affecting trading or essential access. - **Maintenance/PPM:** asset count, site count, equipment mix, existing service history and preferred visit interval if known. - **Installation:** opening/use, traffic level, accessibility/security goal, dimensions or safe photo notes, and desired timing. - **Second opinion:** quoted diagnosis, proposed work and price if the user wants to share it. Do not call the quoted firm wrong. - **Gate/access control:** users/vehicles, entry method, failed component and safety-device symptoms. - **Garage door:** door type, manual/electric operation, vehicle trapped status and whether this is a home or commercial site. Photos are optional and must only be taken safely. This agent route accepts notes, not file uploads. ## Match proof to the enquiry Use only proof returned by `match_relevant_proof` or listed in the facts resource. Choose at most three relevant items. Do not add client names, testimonials, response guarantees, insurance limits or certifications that are not explicitly listed. ## Prepare the exact payload Use the public MCP endpoint at `https://nwautomaticdoors.com/mcp` and call `prepare_enquiry`, or POST JSON to `https://nwautomaticdoors.com/api/agent/enquiry/prepare`. The public human form at `/api/enquiry` is deliberately **not** an agent action and must not be called. Prepare this shape: ```json { "service_id": "one service id from agent-facts.json", "urgency": "emergency | urgent | planned", "property_type": "commercial | public-sector | managed-property | home | private-property", "site_town": "string", "site_postcode": "optional string", "equipment": "string", "issue": "string", "access_impact": "optional string", "safety_or_security_risk": "optional string", "desired_outcome": "optional string", "company": "optional string", "existing_quote_summary": "optional string", "safe_photo_notes": "optional string", "preferred_contact_method": "email | phone", "contact": { "name": "string", "email": "string", "phone": "string" } } ``` ## Consent and external action The required sequence is: 1. **Prepare** — creates a draft with a 15-minute expiry. 2. **Review** — show the user the returned review URL, exact destination, canonical payload and SHA-256 payload hash. 3. **Explicit approval** — the user approves that unchanged payload on the review page. Approval expires after 5 minutes. 4. **Submit** — the review page performs the single-use submission. Changed, expired, missing or reused approvals must be rejected. Never treat “looks good”, a prior general instruction, or silence as approval for a different payload. After preparation, say: **“Nothing has been sent.”** Only say an enquiry was delivered when the submission response contains `ok: true`, `delivery.confirmed: true` and a provider confirmation ID. Otherwise state that delivery was not confirmed and give the phone number. ## Final response before review Show: - known facts used; - any user-supplied assumptions; - relevant proof and its source; - exact destination; - exact JSON payload; - payload hash and expiry; - review URL; - the statement **“Nothing has been sent.”**