---
title: CreateCallbackCommand
---
## PureCloud::CreateCallbackCommand

## Properties

|Name | Type | Description | Notes|
|------------ | ------------- | ------------- | -------------|
| **script_id** | **String** | The identifier of the script to be used for the callback | [optional] |
| **queue_id** | **String** | The identifier of the queue to be used for the callback. Either queueId or routingData is required. | [optional] |
| **routing_data** | [**RoutingData**](RoutingData.html) | The routing data to be used for the callback. Either queueId or routingData is required. | [optional] |
| **callback_user_name** | **String** | The name of the party to be called back. | [optional] |
| **callback_numbers** | **Array<String>** | A list of phone numbers for the callback. | |
| **callback_scheduled_time** | **DateTime** | The scheduled date-time for the callback as an ISO-8601 string. For example: yyyy-MM-ddTHH:mm:ss.SSSZ | [optional] |
| **country_code** | **String** | The country code to be associated with the callback numbers. | [optional] |
| **is_automated** | **BOOLEAN** | Whether or not to automatically place a call for this callback. | [optional] [default to false]|
| **automated_callback_config_id** | **String** | The id of the configuration to handle the response (e.g. live voice, machine) from automatically placing a call for a callback. | [optional] |
| **data** | **Hash<String, String>** | A map of key-value pairs containing additional data that can be associated to the callback. These could be set up for instance to be used in a customized script shown during the call. Example: { \"notes\": \"ready to close the deal!\", \"customerPreferredName\": \"Doc\" } | [optional] |
{: class="table table-striped"}