Goal: Manage callbacks over API
- LUCS is installed
- API Setup and Preconditions are met
- Service must be defined as Outbound to allow for Callback. To do this, head to LUCS Configurator → Services → Select Service → Set Direction Type to "InboundOutbound"
- Users (Agents) must be configured and selectable so task Assignment is possible
Usage example steps
Create an example Callback. In this case, Target is the customer and ServiceSip is the service being called.
Callback creation example
Repeat this multiple times to get callback tasks appear in the system:
Callback is visible in LUCS FrontEnd as Callback Task
→ Response Body Example: Callback created will have missing DTO items filled out with defaults. An unique ID is being assigned:
Example Response body of "CreateCallbackDto"
Details of Callback are known.
ID is used for next examples.
|3||GET Callback||The same results as shown above can be requested via API by using the unique ID (in this example "0f3cf4cd-71f9-4224-a415-3aa5b37bfd59") as parameter.|
Callback Details are requested
(just as a check)
|4||POST Search Callbacks|
Alternatively you can use the extended Search for multiple callbacks. To get more than 1 search result, repeat step 1 with different "Targets" to create multiple callback requests.
Example Response body of "SearchCallbackRequest"
|Returns Queued Callback Tasks between timespan|
|5||POST Cancel Callback|
To remove any callback, the GUID (identifier) is used again. If the task has been removed already or wasn't found, an 404 Error (not found) is thrown.
|Callback is removed from the list of pending callback tasks.|