Talkdesk Studio

Talkdesk Studio Advanced Documentation

Welcome to Talkdesk Studio Advanced Documentation. Here you can find comprehensive documentation to help you deep dive and learn how to make the most of Talkdesk Studio.

Click the button below to get started, or use the search box to find the information you are looking for.

Let's jump right in!

Get Started

Assigning a Call to the Case Owner

Studio makes it easy for you to collect data from Salesforce and use it to assign a call to the appropriate agent. A simple way to do this is by first requesting the caller to input their Case ID on the dial pad. Then, through a Data Dip in Salesforce, you will find out which agent owns the case. Lastly, you will use the Assignment and Dial (A&D) componentcomponent - Components are the basic building blocks of a call flow. There are multiple components available that you can add and configure to suit your needs. Check the full list of available components in the "Studio Components" section of this guide. to assign the call to that agent.

Please follow these instructions to learn in detail how to assign a call using a data dip:

  1. Add the Standard IVR component to your flowflow - A flow represents the full lifecycle of a call. It is a road map to how calls will be handled from the moment they enter the phone system to the end of the call..
  2. Open the Standard IVR component, and on the Preferences tab, choose Text to speech as the message type.
  3. Select the language in which you will write your message.
  4. In the “Text to speech” field, type in the message that will be played when the flow reaches the Standard IVR component.
    Example: “Welcome. Please press 1 if you have a case number. Press 2 if you don’t have a case number.”
  1. Select the Exits tab and under “Custom Exits” choose 2 as the key that the caller should press to go straight to your support line.
  2. Give an appropriate name to the Exit and under “Send to” add the A&D component and name it “Support Queue”.
  3. Click on Add Exit and under “Keypress Exits #2”” choose 1 as the “Keypress”.
  4. Name the Exit and under “Send to” add the Input IVR component.
  5. Scroll down to the “Timeout” and “Invalid” sections and select the Standard IVR from the drop-down lists, creating a loop in both scenarios.
  1. Open the Input IVR component, and on the Preferences tab, choose Text to speech as the message type.

  2. In the “Text to speech” field, type in the message that will be played when the flowflow - A flow represents the full lifecycle of a call. It is a road map to how calls will be handled from the moment they enter the phone system to the end of the call. reaches the Input IVR component.
    Example: “Please insert your case number followed by an asterisk.”

  3. Under “Keypress inputs”, configure the maximum number of digits your caller can input and which key should be used to finalize the input.

  4. In the “Variables” section, click on the drop-down and then on Create variable.

  5. Give a name to the variable. This variable will store the digits that your caller pressed, so we’ve named it “case_number”.

  1. Select the Exits tab, and under “Ok” add the Salesforce data dip component.
  2. Scroll down to the “Timeout” section and add the number of seconds the system will wait for an input before it times out.
  3. Under “Send to”, create a loop by selecting Input IVR from the drop-down.
  4. Open the Salesforce data dip component and paste the following query:
SELECT Id, CaseNumber, Owner.Email, CreatedDate FROM Case WHERE CaseNumber = '%{current_flow.case_number}' ORDER BY CreatedDate DESC LIMIT 1

Note: If you have given a different name to your variable (step 14), replace “case_number” (the lower case instance only) with the name of your variable.

  1. Click on Retrieve Data.
  2. Click on the Owner.Email drop-down and add a new variable with the name “case_owner”.

The case number your caller inserted in the dial pad (and that was stored in the “case_number” variable) will be used to find in Salesforce the agent who owns the case. The agent’s information (email) will be stored in the “case_owner” variable, which will be used in step 27 to assign the call to that agent.

  1. Select the Exits tab, and add a new A&D component under “Ok”.
  2. Name it “Assign to Owner”.
  3. Add the Play Audio component in both the “No result” and “Error” sections. In this componentcomponent - Components are the basic building blocks of a call flow. There are multiple components available that you can add and configure to suit your needs. Check the full list of available components in the "Studio Components" section of this guide., you will inform your callers that you were unable to find the case.
  4. Create a loop in the “Timeout” section by selecting the Input IVR “Case number IVR” in the “Send to” dropdown.
  1. Open the A&D component named “Assign to owner”.
  2. Select Agents as the assignment type.
  3. Under “Select how to find agents”, choose "Variables in the flow context" and select "case_owner" from the list.
  4. Fill out the remaining fields on the Preferences tab.
  5. Select the Exits tab and choose the support queue (A&D component) in all drop-downs.
  1. Open the Play Audio component.
  2. Select the Preferences tab, and in the “Text to speech” field, type the message that will be played when the flow reaches this component.
    Example: “We apologize, but we were unable to find the Case ID.”
  3. Select the Exits tab and route the call to the “Support Queue”.
  4. Complete the configuration of your A&D components and save your flowflow - A flow represents the full lifecycle of a call. It is a road map to how calls will be handled from the moment they enter the phone system to the end of the call. when you are finished.

From now on, if a caller inserts their Case ID when requested, the call will automatically be routed to the agent who owns the case in Salesforce. If the agent is offline or if the caller inserts an invalid Case ID, for example, the call will be directed to the “Support Queue”.

Updated 2 months ago

Assigning a Call to the Case Owner


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.