Whether the AI agent answers automated phone menus and waits in hold queues on the calls it places, and for how long. On by default: an agent that never chose (enabled null) navigates, and a customer who does not want it turns it off once with enabled: false, which every save keeps. A write of this section must say what enabled is: true (on), false (off) or null (follow the platform default, which is on). An empty object, null for the whole section, or a section without enabled is refused with 400 navigation_enabled_required (an older client used {} for off, and it is never guessed at). The section is replaced whole: limits you leave out return to their defaults. Agent create accepts the same section as metadata.navigation under the same rules; the generic agent update keeps the stored section and refuses a different one, naming this route. Navigation applies only to outbound calls (calls the agent places, campaign calls included); inbound calls (a phone test you dial in to included), browser tests, simulations, chat and SMS never navigate. Time in menus and on hold is billed at the normal call rate, and a campaign retries a call that ended at the hold limit or the call's maximum length, or whose other side hung up during the hold, without a person reached earlier (running out of the menu limit is final), so a waiting call can cost far more than one that ends at once. While a call is in a menu or on hold, the answer-detection non-human-audio ending is suspended; turn navigation off if an agent must hang up on hold music. The two limits are per agent and apply to the whole call, never to one menu or one queue: time spent in menus and time spent on hold are counted separately, and the call also ends if it reaches its overall maximum length (turn_taking.max_call_seconds). A single call cannot change them. While navigation is on (chosen or by default), a limit longer than the AI agent's maximum call length (turn_taking.max_call_seconds, at most 1740 seconds) is refused with 400, because a hold or a menu cannot outlast the call; the same refusal applies when you shorten the maximum call length below a limit already set, and when you switch navigation back on beside such a limit. A limit kept beside enabled: false is kept as it is. Applied when a call starts; saving never changes an in-progress call, and no republish is needed. Saving and publishing are never refused because an agent cannot navigate yet: an agent on GPT-Live, or one whose languages navigation is not released in (it is released in English, German, French, Spanish, Italian, Dutch, Portuguese, Russian and Polish; an agent qualifies when at least one of its languages is released and the transcribers Skysay supports can listen to all of its languages with at most two connections; its menus in the unreleased ones are then not navigated), keeps its setting, its calls run without navigation, and the voice-stack response says why in navigation.eligible and navigation.ineligible_reason. Such agents start navigating when support ships, with no change on your side. The tool names press_digits, wait_on_hold and abandon_navigation are reserved for navigation and refused for your own tools.