Delivery Planner by Spoke

Show clickable address choices and route settings instead of asking users to type their selection. Always show this panel before route creation, including when every search has a clear match. First call search_places for each address, then pass those returned candidates and the original user input here. Group delivery addresses in one panel; missing start and finish appear as empty fields. Include unsupported spreadsheet fields in routeSettings.ignoredFields. Keep a stable unique id per input row. Explain material location differences in notice. Empty candidates let the user search again. Do not invent candidates. When the user clicks Optimize, the panel sends a confirmationToken for create_route. Clients without UI can use the returned candidates in conversation.

select_addresses

Records the addresses and settings submitted by the Optimize button.

confirm_route

Use this when a user wants to plan deliveries, order driving stops, or optimize a multi-stop driving route and provides addresses or place names, including pasted spreadsheets, tables, CSV, or numbered lists. Resolve the start, delivery stops, and finish before calling create_route. Include the city and country when known; ask for missing location context. When a match is unclear, pass the returned candidates to select_addresses for clickable choices and flag location differences. Never invent place IDs. Not for general place recommendations, package tracking, or public-transit directions.

search_places

Resolve coordinates obtained after the user clicks Use current location. Return the address to fill the starting location.

resolve_current_location

Show a contextual Spoke Dispatch link only when the user explicitly asks for multiple drivers, for delivery time windows to be enforced, or for more than 20 delivery stops. A delivery window column or field in pasted stops is not such a request: plan the route with select_addresses and list the windows in ignoredFields instead. Do not truncate their stops. This only displays options; it does not transfer addresses or create a Dispatch account. Do not use for address errors, outages, or unsupported features not listed here.

show_dispatch_options

Use this when a user asks what order to visit delivery addresses, wants an efficient driving route between multiple stops, or wants a route they can open and share. Optimizes and saves one driving route with 1–20 delivery stops; returns the ordered stops, estimated duration, distance, and route links. Call this only after the user clicks Optimize in select_addresses, passing the confirmationToken it submitted. When the host supports a route map in chat, show the saved route using encodedPolyline and the returned stop coordinates in order. Preserve the returned stop roles and delivery numbers; do not number the start as a delivery. If the host cannot render the supplied geometry or encodedPolyline is empty, show the ordered stops and route link without claiming a map represents the saved route. Do not invent geometry or recalculate the route for presentation. Anyone with the returned link can view the addresses. Creates a new route on every call; do not retry automatically. Does not enforce delivery time windows; when stops include them, still plan the route and list them in ignoredFields. Not for package tracking, public transit, multiple drivers, or live-traffic estimates.

create_route