Put a member online, offline, or on a break — for chats, for calls, or both — the same change an admin makes from Settings → Team Members or Calls → Team.

• scope: chats — chat auto-assignment only (round-robin, team pools, automations). Chats already assigned stay with the member.
• scope: calls — Lodgestory Voice only: an offline or on-break member is not rung by incoming calls (department queues or direct). Applied to every voice agent the member has (e.g. India and US). A member with no voice agent returns 404.
• scope: both — chats first, then calls. The chat change always stands; the call outcome is reported in calls.status (applied, partial, not_configured, failed), so check it before assuming calls changed.

breakType (offline only) must match one of your break types (case-insensitive; see GET …/break-types) and is recorded as the status label in reports. Omit it for a plain offline status. Every change is recorded in the member's availability history with your service account as the one who made it.

Disabled members can be taken offline but not brought online (403). Re-sending the status a member already has adds no history entry.

Security:

• The organisationId in the URL must match the organisation your JWT was issued for — requests for a different organisation fail with 401.
• Requires CRM_ADMIN, ACCOUNT_OWNER, or CRM_BOT role; other roles receive 403.