G14: native input mapping Draft a clearer phone menu from misroutes Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs CallTree -> native-calltree-template.csv Exact columns: route_id,keypad_number,current_wording,destination_alias,no_input_route,invalid_input_route,hours_rule,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Misroutes -> native-misroutes-template.csv Exact columns: call_alias,selected_route,staff_confirmed_destination,evidence_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Scope -> native-scope-template.txt Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Complete each required field from approved source evidence. Old files and reviewed mapping destinations.csv Original first line: destination_id,caller_category,business_hours_route,after_hours_route menu-draft.txt Original first line: EMPTY OUTPUT TEMPLATE: menu-draft.txt menu-policy.txt Original first line: G14: menu-policy.txt misroutes.csv Original first line: call_id,selected_route,staff_corrected_destination,disposition_code route-tests.csv Original first line: test_id,caller_input,time_context,expected_destination,expected_fallback routing-matrix.csv Original first line: menu_option,caller_category,destination_id,business_hours_route,after_hours_route,fallback destinations.csv and routing-matrix.csv -> CallTree only after inspecting the actual current phone tree. These old schemas do not supply all required route_id, keypad_number, current_wording, no_input_route, invalid_input_route, hours_rule and source_ref. Preserve observed destination_alias mapping separately from proposals. misroutes.csv -> Misroutes: verify call_id -> call_alias and selected_route. staff_corrected_destination supports staff_confirmed_destination only after staff evidence review; add evidence_ref. Do not use caller narratives or recordings in the minimized packet. menu-policy.txt and route-tests.csv -> Scope: preserve approved wording constraints, hours/fallback definitions and expected tests. menu-draft.txt is an old output. Proposed routing and expected test behavior are not observed current behavior. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. Responsible lawyer/operations reviewer approves scope, definitions and any later action. AI optional; use only approved minimized data and retain originals separately. Phone-tree capture is manual. CallRail paths apply only when CallRail is the actual phone platform. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Capture the live menu and observed misroutes Location: Settings > selected company > Workflow > existing call flow; staff’s existing misroute log Inspect without saving. Manually transcribe the current read-message/recording wording, keypad choices, destination roles, timeout/no-input route, business-hour branches and tracking numbers using it. Collect staff-verified aggregate misroute examples; do not upload recordings or caller narratives. Verification: No universal PBX export or native misroute classifier is claimed. Current CallRail menu guidance includes an explicit Does nothing route; absent that option the menu repeats three times. https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step Do not proceed when - Unknown current tree/destinations, no observed misroutes, or a different PBX without its verified controls. Scope template requirements Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documentation-checked component path; proposed workflow, not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.