# Draft a clearer phone menu from misroutes Canonical page: https://agents.paretoid.com/workflows/draft-a-clearer-phone-menu-from-misroutes/ Category: Intake & Booking Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Turn recorded routing mistakes into a short menu and test plan. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Turn recorded routing mistakes into a short menu and test plan. Why it matters: A confusing phone menu can send callers to the wrong team or leave them without a human route. Comparing actual misroutes with approved destinations gives staff a concrete redesign to test. ## Sources and evidence - pain: [Pain evidence: Public discussion](https://www.reddit.com/r/LawFirm/comments/1py4kva/2025_phone_intake_stats_for_a_small_pi_firm/) original post 2025-12-28. The firm identified 34 of 103 intake-extension calls as people who belonged on other extensions, including opposing counsel. Self-reported counts. - method: [Method: CallRail keypad routing and call-flow tests](https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step) CallRail documents keypad routing, call tags, and test-call checks. This recipe drafts a menu and test plan; it does not configure or deploy the phone flow. - method: [Method: CallRail keypad routing and call-flow tests · supporting guide 2](https://support.callrail.com/hc/en-us/articles/5712100621325-Tag-Step) Additional official capability reference. The complete adapted recipe has not been tested. - method: [Method: CallRail keypad routing and call-flow tests · supporting guide 3](https://support.callrail.com/hc/en-us/articles/5711246099853-Troubleshooting-call-flows) Additional official capability reference. The complete adapted recipe has not been tested. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Monthly disposition/misroute review 1. compare caller-selected route with staff-corrected destination 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - 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. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-checked component path; proposed workflow, not tested - Phone-tree capture is manual. CallRail paths apply only when CallRail is the actual phone platform. Access and setup: - The live account, entitlement, exact headers, records and field coverage have not been observed. ### 1. Capture the live menu and observed misroutes Tool: CallRail / existing phone administrator 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. Expected output: Current call-tree specification and deidentified operational examples. Next step: Paste approved menu text, route IDs and staff definitions into the drafting workspace. Check before continuing: 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. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step ### 2. Draft from the approved source packet Tool: Acrobat PDF Spaces / AI Assistant, optional Location: Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat 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. Prompt: ```text 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. Next step: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs. Check before continuing: The script must match actual destinations and recording language; proposed new paths need an approved owner. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step 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 ### 3. Human review and final action Tool: Responsible firm reviewer Location: Internal Review worksheet / review document 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. Next step: CallRail Settings > company > Workflow > selected call flow > Menu; implementation is separate. Check before continuing: No save, assignment, recording upload or test call was performed. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.callrail.com/hc/en-us/articles/5711311620749-Menu-Step ## What you will get routing-matrix.csv: menu_option, caller_category, destination_id, business_hours_route, after_hours_route, fallback; route-tests.csv: test_id, caller_input, time_context, expected_destination, expected_fallback; menu-draft.txt: short approved-for-review script ## Human review and limits No substantive legal advice or AI case screening. Test all routes and retain a human escape option. Recording requires separate firm approval and required notice/consent. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema misroutes.csv: call_id, selected_route, staff_corrected_destination, disposition_code destinations.csv: destination_id, caller_category, business_hours_route, after_hours_route; menu-policy.txt: languages, accessibility needs, human escape, no-input, invalid-input and unanswered handling Synthetic example input: ```text C1: existing client selects new inquiries C2: no keypad input C3: correct route is unanswered after hours ``` Expected synthetic output: ```text C1: clearer option wording C2: approved human fallback C3: approved after-hours fallback, no live change ``` Failure check: No substantive legal advice or AI case screening. Test all routes and retain a human escape option. Recording requires separate firm approval and required notice/consent. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/g14-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/g14/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Input template: misroutes.csv](https://agents.paretoid.com/assets/starter-kits/g14/misroutes.csv) — Header-only input template; preserve exact names and order - [Synthetic input: misroutes.csv](https://agents.paretoid.com/assets/starter-kits/g14/misroutes-example.csv) — Fabricated sample rows for an offline manual trial - [Input template: destinations.csv](https://agents.paretoid.com/assets/starter-kits/g14/destinations.csv) — Header-only input template; preserve exact names and order - [Synthetic input: destinations.csv](https://agents.paretoid.com/assets/starter-kits/g14/destinations-example.csv) — Fabricated sample rows for an offline manual trial - [Output template: routing-matrix.csv](https://agents.paretoid.com/assets/starter-kits/g14/routing-matrix.csv) — Header-only output template; preserve exact names and order - [Expected output: routing-matrix.csv](https://agents.paretoid.com/assets/starter-kits/g14/routing-matrix-example.csv) — Hand-authored synthetic expected result; not an executed workflow result - [Output template: route-tests.csv](https://agents.paretoid.com/assets/starter-kits/g14/route-tests.csv) — Header-only output template; preserve exact names and order - [Expected output: route-tests.csv](https://agents.paretoid.com/assets/starter-kits/g14/route-tests-example.csv) — Hand-authored synthetic expected result; not an executed workflow result - [Policy/input template: menu-policy.txt](https://agents.paretoid.com/assets/starter-kits/g14/menu-policy.txt) — Required source/policy preparation scaffold; not populated with firm instructions - [Synthetic policy/input: menu-policy.txt](https://agents.paretoid.com/assets/starter-kits/g14/menu-policy-example.txt) — Fixture-only context; not an approved production policy - [Draft scaffold: menu-draft.txt](https://agents.paretoid.com/assets/starter-kits/g14/menu-draft.txt) — Blank output scaffold; no message, form or appeal is sent - [Synthetic expected draft: menu-draft.txt](https://agents.paretoid.com/assets/starter-kits/g14/menu-draft-example.txt) — Hand-authored draft or blocked-output example for fixture review - [Synthetic fixture expectations](https://agents.paretoid.com/assets/starter-kits/g14/fixture-expectations.txt) — Acceptance targets and failure checks; no claim of workflow execution - [Review prompt](https://agents.paretoid.com/assets/starter-kits/g14/starter-prompt.txt) — Copyable offline review prompt; no executable automation - [Setup and prerequisites](https://agents.paretoid.com/assets/starter-kits/g14/README.txt) — Recipe-specific setup, evidence sources and usage boundaries - [Native input scaffold: CallTree](https://agents.paretoid.com/assets/starter-kits/g14/native-calltree-template.csv) — Empty editorial table for CallTree; populate from verified source evidence after reviewed mapping; not a native export - [Native input scaffold: Misroutes](https://agents.paretoid.com/assets/starter-kits/g14/native-misroutes-template.csv) — Empty editorial table for Misroutes; populate from verified source evidence after reviewed mapping; not a native export - [Native input scaffold: Scope](https://agents.paretoid.com/assets/starter-kits/g14/native-scope-template.txt) — Approved text input for Scope; complete from verified evidence and include in the AI-visible packet - [Native input mapping and scope guide](https://agents.paretoid.com/assets/starter-kits/g14/NATIVE-INPUT-MAPPING.txt) — Old-file-to-native-input compatibility map, acquisition requirements, privacy and blocking gates ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Using these redacted misroute records and our departments, propose the shortest clear phone menu separating new inquiries, existing clients and professional callers. Include no-input, wrong-input, unanswered and after-hours fallbacks. Produce a test matrix. Do not infer whether someone is a client from their story or deploy the flow. INPUTS misroutes.csv: call_id, selected_route, staff_corrected_destination, disposition_code destinations.csv: destination_id, caller_category, business_hours_route, after_hours_route; menu-policy.txt: languages, accessibility needs, human escape, no-input, invalid-input and unanswered handling OUTPUT routing-matrix.csv: menu_option, caller_category, destination_id, business_hours_route, after_hours_route, fallback; route-tests.csv: test_id, caller_input, time_context, expected_destination, expected_fallback; menu-draft.txt: short approved-for-review script Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.