Creating Tasks and Accepting Reservations: Accept a Reservation using Assignment Callback Instructions
Remember when we created a Task and accepted it using the Reservations subresource of the REST API? I do. And it was grand.
This time, we'll create another Task, again using the REST API, but we will have our server accept the Reservation as soon as it is notified, via a synchronous HTTP response.
Before we create the next Task, once again make sure that our Worker Alice is in a non-available Activity state.
Repeat the commands from step 2 to create another Task that only Alice is eligible to handle. Here's our PHP file from earlier:
_30<?php_30// Get the Twilio-PHP library from twilio.com/docs/libraries/php,_30// following the instructions to install it with Composer._30require_once "vendor/autoload.php";_30use Twilio\Rest\Client;_30_30// put your Twilio API credentials here_30// To set up environmental variables, see http://twil.io/secure_30$accountSid = getenv('TWILIO_ACCOUNT_SID');_30$authToken = getenv('TWILIO_AUTH_TOKEN');_30_30// Set your WorkspaceSid and WorkflowSid_30$workspaceSid = 'WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';_30$workflowSid = 'WWXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';_30_30// instantiate a new Twilio Rest Client_30$client = new Client($accountSid, $authToken);_30_30// create a new task_30$task = $client->taskrouter_30 ->workspaces($workspaceSid)_30 ->tasks_30 ->create(array(_30 'attributes' => '{"selected_language": "es"}',_30 'workflowSid' => $workflowSid,_30 ));_30_30_30// display a confirmation message on the screen_30echo "Created a new task";
and the curl command:
_10curl https://taskrouter.twilio.com/v1/Workspaces/{WorkspaceSid}/Tasks \_10--data-urlencode Attributes='{"selected_language": "es"}' \_10-d WorkflowSid={WorkflowSid} \_10-u {AccountSid}:{AuthToken}
This time, before bringing Alice online, we need to make changes to our assignment.php file. Open it and modify the existing code to reflect the following:
_10<?php_10_10$assignment_instruction = [_10 'instruction' => 'accept'_10];_10_10header('Content-Type: application/json');_10echo json_encode($assignment_instruction);
Instead of returning an empty JSON document as before, we've included an 'assignment instruction' in our response. The 'accept' assignment instruction tells TaskRouter to automatically accept the Reservation and assign the Task to the Worker it has been reserved for.
To kick this process off, we need to transition Alice to an available Activity. With your Workspace open in the TaskRouter web portal, click 'Workers' then click to edit Alice and set her Activity to 'Idle'.
Now, click 'Tasks' in the main navigation, and you should see that the Task has an Assignment Status of 'assigned':
What actually happened is that Alice was reserved for a very short period of time. TaskRouter made a request to your web server at the Assignment Callback URL, and your server told TaskRouter to accept the Reservation. At that point, Alice's Activity transitioned to the 'Assignment Activity' of the TaskQueue that assigned the Task, as it did in the previous step.
And that's that. We created another Task using the REST API, accepted it via an assignment instruction at our Workflow's Assignment Callback URL and saw that this immediately accepted the Reservation for our Worker.
Onward! Next we learn about shortcuts to create Tasks originating from Twilio phone calls.