Conversations
Chat Sessions
Chat Sessions
Contacts
Contacts
Companies
Companies
Blocklist
Blocklist
Custom Statuses
Custom Statuses
Search
Search
AI Configuration
Autopilot
Autopilot
AI Training
AI Training
Training Directories
Training Directories
AI Actions
AI Actions
Knowledge
Website Crawling
Website Crawling
Help Center
Help Center
Channels
Email
AI Phone Agents
AI Phone Agents
WhatsApp
Widget
Widget
Operations
Teams
Teams
Use
list_team_categories or create_team_category to find a category ID, then set category_id with update_team_settings. Send null to clear it. Categories organize teams without changing their routing. Category reads require teams:read; creation requires teams:write.Use list_office_hours to find a schedule, then set support_office_hours_id; null restores the workspace default. Schedules and categories must belong to the current workspace. Set support_assignment_strategy and auto_assign_interval_seconds to configure assignment. Pacing accepts 0 to turn it off or whole seconds from 15 to 3600.To configure call routing, first use get_team to review the current settings,
then call update_team_settings with the team ID and only the settings to change.
This requires both teams:read and teams:write. Omitted settings stay unchanged;
it does not add members, change their availability, or set organization-wide auto-answer.0 disables it and null inherits the organization
setting. Distribution accepts longest_available or fewest_answered_today.
Enabling Support does not make an unstaffed or unavailable team ready to answer calls.
See inbound calls for routing prerequisites.Users
Users
Office Hours
Office Hours
Organization
Organization
Macros
Macros
Custom variables are authored in the OpenCX dashboard (Settings → Macros → Variables); the API and MCP surface them read-only via
list_macro_variables. Macro attachments are also authored in the dashboard and returned read-only by list_macros and get_macro. Options can be set with create_macro and update_macro: update_macro takes the full list, so keep an option by passing its id and leave one out to remove it.Outbound Sequences
Outbound Sequences
Workflows
Workflows
Analytics
CSAT
CSAT
Handoff Analytics
Handoff Analytics
SLA Policies
SLA Policies
SLA Analytics
SLA Analytics
Impact Report
Impact Report
Customer Insights
Customer Insights
Compliance and Audit
Audit Logs
Audit Logs
Redaction
Redaction
Media
Media
Related Documentation
Prompt Library
Ready-to-use prompts by domain
Workflows
Multi-step scenarios that chain prompts together
Get Started
Connect the MCP server to your AI client
Troubleshooting
Common issues and how to resolve them
Contact segment management
Usecreate_contact_segment, update_contact_segment, and delete_contact_segment to manage saved contact filters. These tools require segments:write. Companion makes them available to users with contact write permission.
Updates change only supplied fields; supplying a definition replaces the complete filter rules. Membership recalculates in the background after creation or filter changes. Deletion removes the segment and its memberships while keeping contacts, and does not rewrite references in other configurations.
Use list_contact_segments, get_contact_segment, list_segments_for_contact, and check_contact_in_segment to inspect definitions and membership with segments:read. See contact segments for examples.