leadbay_plan_tour_in_city

Plan a field sales tour for me in <City or region the user is visiting (e.g. 'Limoges', 'Bay Area'). Used as the geo filter for both Monitor and Discover lookups. A country is not a city: this workspace already covers exactly one country, and a country name here silently fences the tour to a same-named village. Do NOT omit the argument to recover — a city-less tour returns arbitrary leads from across the whole workspace, which is not an itinerary. Ask which city or region the visit is to. If not provided in the user's most recent message, ask once before proceeding.><if the user supplied this argument, render the short parenthetical or inline clause derived from it; otherwise empty. Source: When the visit is (e.g. 'May 24', 'next Thursday'). Surfaced in the outreach drafts as 'I'll be in on '.>.

GATE — DEFER TO TOOL RENDERING. When you call a Leadbay composite that ships its own RENDERING block (every composite in 0.9.0+ does), render the response using that block's recipe verbatim — score bars, glyph palette, column order, hide-list, link priorities, all of it. Do NOT substitute prose, a numbered list, or a different column structure even when an orchestrating prompt's body suggests alternate framing. Prompt-specific commentary (motivational nudges, summaries, next-action recommendations) belongs ABOVE or BELOW the canonical table, never in place of it.

If the prompt's body and the tool's RENDERING appear to conflict, the tool's RENDERING wins for the structural layout; the prompt's voice wins for the commentary that surrounds it.

PHASE 1 — CLARIFY SCOPE FIRST (ask before building)

Before calling leadbay_tour_plan, ask me what the tour should cover — a field tour is high-intent and the scope changes what lands on the map. Use your host's interactive question widget (ask_user_input_v0 in Claude chat — {questions:[{question, type:"single_select", options:[…]}]}; or AskUserQuestion in cowork / Claude Code — {questions:[{question, header, multiSelect, options:[{label, description}]}]}). Ask at most 2 short tap-to-answer questions:

1. Who to include? — options: "Mix — known accounts + fresh prospects" (default), "Only my known accounts (follow-ups)", "Only fresh new prospects".
2. Enrich contacts that have no phone/email? — options: "Yes, enrich the top stops", "No, just plan the tour".

Skip a question only if I already answered it in my request (e.g. "plan a tour of just my new leads in NYC" → who-to-include is already "only new"; don't re-ask). If I gave the full scope up front, skip PHASE 1 entirely and go to PHASE 2.

Map my answers to the leadbay_tour_plan call:

• Mix → defaults (followups_count: 6, discover_count: 6).
• Only known accounts → discover_count: 0.
• Only new prospects → followups_count: 0.
• Enrich = yes → after the tour is planned (PHASE 2), call leadbay_enrich_titles / leadbay_prepare_outreach(enrich:true) on the top stops that have no recommended_contact channel, before drafting outreach.