Creates the recommended dispositions and call reasons for each type the domain has no codes of yet, or only for type. Nothing runs it automatically. A type that already has any code (inactive included) is skipped and its codes are not changed, so calling it again is safe. Each created code has seededyes, a description, and sort-order in the order below starting at 0; every disposition has a classification and every call reason none. POST only. Requires the Office Manager, Call Center Supervisor, Reseller or Super User scope.Dispositions | name | direction | system-applied | classification | description | |---|---|---|---|---| | Resolved | both | no | positive | The caller's issue or request was fully handled on this call. | | Follow-up Required | both | no | neutral | Not finished; someone needs to act or call back later. | | Callback Scheduled | both | no | positive | A time was agreed to call the customer back. | | Escalated | both | no | neutral | Passed to a supervisor or specialist team to handle. | | Transferred | both | no | neutral | Sent on to another agent, queue or department. | | Left Voicemail | both | no | neutral | No answer; a message was left. | | Wrong Number | both | no | negative | The caller or number reached the wrong business. | | Not Interested | outbound | no | negative | The contact declined the offer or conversation. | | Abandoned in Queue | inbound | yes | negative | The caller hung up before an agent answered. | | No Answer | both | yes | negative | The call rang out with nobody picking up. | | Line Busy | outbound | yes | negative | The number was busy. | | Call Failed | both | yes | negative | The call could not be connected (network or number error). |Call reasons (all system-appliedno, classificationnone) | name | direction | description | |---|---|---| | Sales Inquiry | inbound | A prospect asking about products, pricing or availability. | | Sales Outreach | outbound | Calling a prospect or customer to sell or upsell. | | Order Status | both | Checking where an order, shipment or delivery is. | | Billing or Payment | both | Invoices, charges, refunds or taking a payment. | | Technical Support | both | Help with a product or service that isn't working as expected. | | Appointment or Scheduling | both | Booking, moving or cancelling an appointment. | | Complaint | inbound | The customer is unhappy and wants it put right. | | General Information | inbound | Hours, locations, policies and other general questions. | | Collections | outbound | Following up on an overdue balance. | | Survey or Feedback | outbound | Asking the customer about their experience. |
Request
Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Path Params
Query Params
Responses
🟢200OK
application/json
Nothing to create (each type asked for already has codes); an empty list
Bodyapplication/json
🟢201Created
🟠400Bad Request
🟠401Unauthorized
🟠403Forbidden
🟠404Record Not Found
🟠405
🟠409
🔴503Service Unavailable
Request Request Example
Shell
JavaScript
Java
Swift
curl--location--request POST 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//callcenter-codes/seed?type=undefined' \
--header'Authorization: Bearer <token>'