Draft a clearer phone menu from misroutes Get the source data and prepare the review Documentation-checked component path; proposed workflow, not tested WHAT WAS CHECKED Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution. BEFORE YOU START - 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. DATA ACQUISITION LIMITS - Phone-tree capture is manual. CallRail paths apply only when CallRail is the actual phone platform. STOP IF - Unknown current tree/destinations, no observed misroutes, or a different PBX without its verified controls. KEEP THE ANALYSIS COPY SEPARATE Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. INPUT FORMAT LIMIT All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data. NATIVE REVIEW INPUTS version: 1 status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible compatibleWithoutMapping: False existingKitFilesInspected: - file: destinations.csv firstLine: destination_id,caller_category,business_hours_route,after_hours_route - file: menu-draft.txt firstLine: EMPTY OUTPUT TEMPLATE: menu-draft.txt - file: menu-policy.txt firstLine: G14: menu-policy.txt - file: misroutes.csv firstLine: call_id,selected_route,staff_corrected_destination,disposition_code - file: route-tests.csv firstLine: test_id,caller_input,time_context,expected_destination,expected_fallback - file: routing-matrix.csv firstLine: menu_option,caller_category,destination_id,business_hours_route,after_hours_route,fallback requiredNativeInputs: - name: CallTree kind: editorial_table proposedDistinctTemplate: native-calltree-template.csv columns: - route_id - keypad_number - current_wording - destination_alias - no_input_route - invalid_input_route - hours_rule - source_ref acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Misroutes kind: editorial_table proposedDistinctTemplate: native-misroutes-template.csv columns: - call_alias - selected_route - staff_confirmed_destination - evidence_ref acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Scope kind: approved_text_section proposedDistinctTemplate: native-scope-template.txt requiredContent: 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. templateFilesCreatedByThisTask: False requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence. OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. CallTree: native-calltree-template.csv Misroutes: native-misroutes-template.csv Scope: native-scope-template.txt STEP 1: Capture the live menu and observed misroutes Tool: CallRail / existing phone administrator Open: Settings > selected company > Workflow > existing call flow; staff’s existing misroute log Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step 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. Expected output: Current call-tree specification and deidentified operational examples. Use it next: Paste approved menu text, route IDs and staff definitions into the drafting workspace. Check: 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. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step STEP 2: Draft from the approved source packet Tool: Acrobat PDF Spaces / AI Assistant, optional Open: Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: downstream_application_ai Paste only the approved nonconfidential packet, source IDs and full Scope note. Paste the exact prompt into the Space chat. Do not upload raw client records; this is a downstream drafting assistant, not an AI in the source application. PASTE THIS PROMPT Using only the current CallTree, staff-confirmed Misroutes and Scope, draft concise phone-menu wording. Preserve every approved destination and keypad number unless you explicitly mark a proposed change for review. Cover no input, invalid input, closed hours and human fallback only where supported by the captured flow. Return old wording,new wording,route_id,reason,evidence_refs and a synthetic caller-path test matrix. Do not ask callers to disclose case facts publicly, diagnose legal urgency, promise representation or change routing. Expected output: Revised script and route-preserving test matrix. Use it next: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs. Check: The script must match actual destinations and recording language; proposed new paths need an approved owner. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html STEP 3: Human review and final action Tool: Responsible firm reviewer Open: Internal Review worksheet / review document Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Phone administrator and lawyer approve wording and each destination. Save the draft. If later authorized, an operator uses the Menu step Read Message/Play Recording controls, saves/assigns the flow, and makes controlled test calls from a number outside the flow. Expected output: Approved phone-menu script, with implementation and testing still pending. Use it next: CallRail Settings > company > Workflow > selected call flow > Menu; implementation is separate. Check: No save, assignment, recording upload or test call was performed. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step ACCOUNT AND SOURCE CHECKS STILL NEEDED - The live account, entitlement, exact headers, records and field coverage have not been observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.