Change AI escalation rules and knowledge-gap behavior

Update the existing guest-facing escalation policy using a fresh get_ai_handoff_policy read and expectedPolicyVersion. enabled and the complete intents array are required; preserve IDs/fields of rules you intend to retain. Omit knowledgeGapBehavior or workingHours to preserve them. New rules may omit id and receive a service-generated stable ID; inspect returned IDs. Normally at most eight rules; existing oversized policies can only shrink without adding IDs. propertyIds must reference active properties from list_properties. Working hours require all seven distinct days with valid HH:mm times in the business timezone. A 409 conflict requires reload/reconciliation. The service schedules existing handoff projections after saving; on uncertain failure read current policy before retrying. This affects future escalation and projection state; it does not resolve cases, send a guest reply, or enable server knowledge-gap rollout gates. Required permission: ai_settings:write. Connected business only.

put/settings/ai/handoff-policy

Request

  • Base URL
    https://platform-api.visitoai.com/m2m/v1
  • Auth
    HTTP bearer

Request body

expectedPolicyVersionstring required

Copy policy.policyVersion from get_ai_handoff_policy, including default when no stored policy exists. Stale versions return HANDOFF_POLICY_VERSION_CONFLICT (409); reload and reconcile.

enabledboolean required
knowledgeGapBehavior'disabled' | 'report_only' | 'create_handoff'

Response

Success

Changes

No recorded changes to this operation across all 1 revision of this API.