# Building inbound flows in Talkdesk Studio Systems: Talkdesk For Talkdesk administrators with Studio permissions who are setting up or rebuilding inbound voice routing for one or more Talkdesk numbers. Canonical: https://warmtransfer.net/guides/talkdesk-studio-flow-setup Last verified: 2026-10-02 A Talkdesk Studio Incoming Call flow covers an inbound call from the moment it arrives until the call ends or its post-call actions, such as surveys, finish[^65]. This guide builds that flow from Time Based Rules, Standard IVR and Assignment and Dial components and then publishes it, because a Studio flow must be published before it can be assigned to phone numbers[^61][^35][^12][^48]. ## Before you start - Studio roles have View, Manage and Publish permissions. Manage allows editing, saving, restoring and duplicating flows. Publish allows publishing flows and managing phone number assignments[^44]. - The Publish permission requires View and Manage[^45]. - The Single Device Mode account device setting must be enabled for Talkdesk Studio to work[^56]. - The Studio service quota is 500 flows per account[^49]. - A single flow execution can run at most 500 steps[^50]. - Inventory the numbers you plan to route, because a Talkdesk phone number can be assigned to only one Studio flow at a time[^42]. - Inventory the agents who will take these calls, because agents must be in Available status to receive Studio-assigned interactions[^6]. ## What changes by situation - How should Assignment and Dial pick agents? Ring groups: route to named groups of agents; Attributes: match agents by attributes, optionally with proficiency. - Will each number get its own flow, or will several numbers share one flow? One flow per number (or per group of numbers with identical behaviour); One shared flow for several numbers. - What can a caller do instead of waiting in queue? Request a queue callback; Leave a voicemail; Nothing: wait until an agent answers or the waiting time runs out. ## Step 1: Confirm permissions and account settings that affect Studio ### Do - Confirm that your role has View and Manage, and also Publish if you will publish the flow and assign numbers[^44][^45]. - Confirm that Single Device Mode is enabled[^56]. - Review the account Blocklist setting, because it affects Studio flows[^16]. - Review account Holiday Hours, because they determine routing before a flow's Time Based Rules component runs[^34]. - Review account Inbound Call Recording, which applies to a flow that has no Record component and does not work with Forward to external number[^2]. - Account-level Business Hours and Timezone settings are used only for reporting, and only when a flow has no Time Based Rules component[^1]. ### Verify - Studio opens from Admin > Studio[^28]. - Suggested check: if your role includes publishing rights, confirm that you can open the number-assignment control on an existing flow's card. ## Step 2: Create the Incoming Call flow ### Do - In Admin > Studio, click Create flow, and choose Empty flow to build from scratch or Import flow to create the flow from a JSON file[^28]. - Choose the Incoming Call type, one of 4 Studio flow types alongside API Request, Incoming Message and Outgoing Call[^66]. - Choose the name carefully: a published flow cannot be renamed directly, and the workaround is Duplicate version to a new flow, rename and publish it, then reassign the numbers through Manage numbers[^51]. ### Verify - A Studio flow can have only one draft version, and a flow can be built or changed only in that draft[^43]. - Suggested check: confirm that the new flow opens on the canvas as a draft. ### Rollback - A flow must be published before it can be assigned to phone numbers[^48]. - Suggested rollback: leave the draft unpublished and assign no numbers to it. ## Step 3: Add business-hours routing **One flow per number (or per group of numbers with identical behaviour)** ### Do - Add a Time Based Rules component, which routes interactions to agents during defined business hours and can send contacts to voicemail outside them[^61]. - For each exit, set a name, a timezone, one or more time ranges and a Send to destination component[^57]. - Set each open-hours exit to Report as: Inside Business Hours, which is required for calls through it to be counted as inside business hours[^62]. - Send the No match exit to your closed treatment; calls that leave through No match are reported as outside business hours[^60]. - For public holidays or other special periods, add a Calendar Based Rules component, which can play differentiated greetings and route to another number or voicemail[^17]. - Account Holiday Hours still determine routing before this component runs[^34]. ### Verify - Suggested check: confirm that each exit's timezone matches the site this number serves. - Suggested check: after the flow is live, place a test call outside the configured hours and confirm that it follows the No match path. ### Rollback - Clicking Edit on a published flow creates a draft copy, and the previous version stays published while you change or remove the rule[^30]. **One shared flow for several numbers** ### Do - Add one Time Based Rules component and give each exit a name, a timezone, one or more time ranges and a Send to destination[^57]. - Set open-hours exits to Report as: Inside Business Hours[^62]. - Send the No match exit to your closed treatment; calls through it are reported as outside business hours[^60]. - Time Based Rules exits apply to the phone numbers associated with the flow that contains them[^58]. - WarmTransfer's reading of the sources is that numbers sharing one flow will probably share the same Time Based Rules schedule unless the flow branches before that component, so a number that needs different hours is simpler to give its own flow[^55]. - If several Time Based Rules steps run on the same path, the last one executed decides whether the call is reported as inside or outside business hours[^59]. - Add a Calendar Based Rules component for public holidays or other special periods[^17]. - Account Holiday Hours determine routing before Time Based Rules runs[^34]. ### Verify - Suggested check: list every number you plan to assign in Step 9 and confirm that they all share the same opening hours and timezone. ### Rollback - Clicking Edit on a published flow creates a draft copy, and the previous version stays published while the draft is worked on[^30]. ## Step 4: Build the menu with Standard IVR ### Do - Point the open-hours exit's Send to destination at a Standard IVR[^57]. - For each menu option, add a custom exit that sets the key the caller presses, a display name and the next step the flow runs[^35]. - Set the Timeout, the number of seconds to wait for a selection before redirecting, and choose where the Invalid Input exit for unconfigured keys goes[^38]. - We infer that an IVR whose Timeout or Invalid Input exit loops back to itself will probably hit the 500-step execution quota if a caller never responds, so bound any loop or end it at an agent or voicemail[^36]. ### Verify - Talkdesk notes that errors appear on each save while an IVR flow is being built, which is expected until all steps are configured[^37]. - Saving triggers automatic error verification, and errors must be resolved before the flow can be published[^53]. ### Rollback - Suggested rollback: delete or rewire the menu exits in the draft. ## Step 5: Configure Assignment and Dial **Ring groups: route to named groups of agents** ### Do - In Preferences, choose the Ring Groups assignment type; only one type can be selected per component[^13]. - Select the target ring groups, or store a ring group name in a flow variable and use it with the Ring groups type, as Talkdesk's FAQ describes[^9]. - Set the maximum ringing time, after which an unanswered call goes back to the queue, between 30 and 600 seconds[^7]. - Set the agents to ring at once, up to 10; Talkdesk warns that ringing several agents at once can add latency[^3]. - Choose Single Attempt to try one batch of agents once, or Exhaust to keep looking for available agents until the maximum waiting time is reached[^10]. - Set the priority from 1, the highest, to 10, the lowest, either fixed or from a flow variable; priority outweighs time in queue[^8]. - Set the maximum waiting time, waiting music and waiting messages, which can use Amazon Polly text-to-speech, an uploaded audio file, or an external URL or variable[^14]. ### Verify - Agents must be in Available status to receive Studio-assigned interactions, and when several agents match, the most idle agent is chosen[^6]. - Suggested check: confirm that each selected ring group contains agents who will be available during open hours. ### Rollback - Suggested rollback: change the preferences in the draft and publish again. **Attributes: match agents by attributes, optionally with proficiency** ### Do - In Preferences, choose the Attributes assignment type; only one type can be selected per component[^13]. - Select the attributes an agent must have, plus proficiency where configured, and combine them with AND or OR conditions[^5]. - Choose Idle time or Most proficient sorting; Most proficient uses only the first attribute in the list and breaks ties by idle time, so put the deciding attribute first[^11]. - Set the maximum ringing time between 30 and 600 seconds[^7]. - Set the agents to ring at once, up to 10[^3]. - Choose Single Attempt or Exhaust[^10]. - Set the priority from 1 to 10[^8]. - Set the maximum waiting time, waiting music and waiting messages[^14]. ### Verify - Agents must be in Available status to receive Studio-assigned interactions, and when several agents match, the most idle agent is chosen[^6]. - Suggested check: confirm that at least one agent who will be available during open hours holds the required combination of attributes. ### Rollback - Suggested rollback: change the attribute conditions in the draft and publish again. ## Step 6: Wire the Assignment and Dial exits and error handling ### Do - Give the No answer, Maximum waiting time reached and No match found exits each a destination, such as Voicemail[^12]. - To overflow to a second team, place a further Assignment and Dial component on the first one's exits (chained routing)[^27]. - Open Error handling and replace the default: for Assignment and Dial the default is End flow, and Talkdesk strongly advises configuring it so the call can continue[^31]. - Choose between default behaviour, end flow, an existing exit, or a custom exit[^32]. ### Verify - Saving triggers automatic error verification, and errors must be resolved before the flow can be published[^53]. - Suggested check: confirm that every exit on the canvas has a destination. ### Rollback - Suggested rollback: rewire the exits in the draft. ## Step 7: Offer an alternative to waiting **Request a queue callback** ### Do - In the Assignment and Dial Alternative Exits, pick a keypress, name the exit and choose Request callback from queue in Send to[^19]. - Choose the number to dial: the caller's original number, another number defined earlier in the flow, or the original number plus an extension[^24]. - Wire the Invalid Inbound Phone Number exit, which anonymous callers take; Talkdesk suggests collecting a number with Input IVR and requesting the callback again from that variable[^20]. - In that path, the Input IVR stores the digits in a flow variable, and Request Callback from Queue uses it through From variable in the flow context under Number to dial[^23]. - Wire the Invalid Outbound Caller ID, Duplicate Request and Call Finished exits[^25]. ### Verify - After the caller confirms, they hear the Request successful message and the call hangs up, while they keep their place in the assignment queue[^21]. - The assigned agent sees the caller's name and number, the request time, the originating queue and the dialed number, and can accept or decline the callback[^18]. - If no agent becomes available within the callback time limit, an optional timeout message can play and the missed callback is marked as an Abandoned Call[^26]. - Suggested check: place a test call, press the callback key while waiting, and confirm that a test agent receives the callback offer. ### Rollback - Talkdesk states that queued callbacks are not charged while waiting in the queue, only when they are served[^22]. - Suggested rollback: remove the alternative exit in a new draft and publish again. **Leave a voicemail** ### Do - In the Assignment and Dial Alternative Exits, pick a keypress, name the exit and choose Voicemail in Send to[^19]. ### Verify - Alternative Exits give queued callers keypress ways out of the waiting queue[^4]. - Suggested check: place a test call, press the voicemail key while waiting, and confirm that the call reaches voicemail. ### Rollback - Suggested rollback: remove the alternative exit in a new draft and publish again. **Nothing: wait until an agent answers or the waiting time runs out** ### Do - Add no callback or voicemail Alternative Exit, and make sure the Maximum waiting time reached exit sends the call to a component such as Voicemail[^12]. - With Exhaust, Assignment and Dial keeps looking for available agents until the maximum waiting time is reached[^10]. ### Verify - Suggested check: place a test call that waits past the maximum waiting time and confirm that it follows the exit you wired. ## Step 8: Save, validate and publish ### Do - Save and validate the draft, resolve any errors, then click Publish in the top-right corner[^47][^53]. ### Verify - A flow must be published before it can be assigned to one or more phone numbers[^48]. - Suggested check: confirm that the flow shows a published status. ### Rollback - A flow has only one published version, so publishing a later draft automatically archives this one[^46]. - An archived version can be restored with the Restore version button, which creates a draft copy of it; if a draft already exists, Studio shows a warning[^52]. ## Step 9: Assign numbers to the flow **One flow per number (or per group of numbers with identical behaviour)** ### Do - In the Studio app, click the No numbers dropdown on the flow's card, select Manage numbers, tick the number (or group of identical numbers) for this flow, click Save and confirm in the modal[^15]. ### Verify - A number can be assigned to only one Studio flow at a time[^42]. - Suggested check: confirm that the number shows on this flow's card and no longer shows on its previous flow. ### Rollback - Uncheck the number in the Manage Numbers side panel and click Save[^64]. - Suggested rollback: reassign the number to the flow it used before. **One shared flow for several numbers** ### Do - In the Studio app, click the No numbers dropdown on the flow's card, select Manage numbers, tick every number that should use this flow, click Save and confirm in the modal[^15]. - A single Studio flow can be assigned to several phone numbers[^33]. ### Verify - Each number can be assigned to only one Studio flow at a time[^42]. - Suggested check: confirm that every intended number appears on this flow's card. ### Rollback - Uncheck numbers in the Manage Numbers side panel and click Save[^64]. ## Step 10: Test with real calls and check the execution trail ### Do - Talkdesk recommends placing test calls to the numbers assigned to a Studio flow to hear what callers will hear[^63]. - Test with no agent Available and with one agent Available, because only Available agents receive Studio-assigned interactions[^6]. ### Verify - Suggested check: test inside and outside business hours, every menu key, an invalid key and a timeout, and confirm that each path behaves as designed. - Calls that leave Time Based Rules through No match are reported as outside business hours[^60]. - For step-level evidence, request the studio_flow_execution report type through the Explore API, with at most 1 month of data per request[^67]. ### Rollback - If a test fails on a live number, uncheck it in Manage Numbers and click Save[^64]. - Alternatively, restore the previous archived version, which creates a draft copy that you then publish[^52][^47]. ## Step 11: Make later changes safely ### Do - Click Edit on the published flow, which creates a draft copy while the previous version stays published[^30]. - Make the changes, then save, validate and publish again[^47]. - If several flows need the same logic, consider a Studio Module, a reusable block of steps; editing a published module applies the change to every flow that references it[^39]. - Only published modules can be used in flows, and a module cannot be deleted while flows reference it[^40]. ### Verify - Place a test call to the assigned numbers to hear what callers will hear on the changed path[^63]. ### Rollback - Restore the previous archived version with Restore version, then publish it, which archives the version you are replacing[^52][^46]. ## Applicability Applies to: Talkdesk Studio and Talkdesk Explore API. Deployments: multi-tenant. Sources checked 2026-10-02. Phone numbers cannot be assigned to a Studio flow of the outbound call type, so this guide applies to the Incoming Call type only[^41][^66]. ## What remains uncertain - Whether saving a draft without publishing it changes what live callers hear is not covered by the sources below, so treat every save as possibly live until you have tested it. - The default Standard IVR Timeout value is not covered by the sources below. - How to branch a shared flow on the dialed number before Time Based Rules runs is not covered by the sources below. - Creating ring groups, creating or assigning attributes, configuring account Holiday Hours, and routing to individual agents are not covered by the sources below. - Whether your account's Studio interface matches the documented screens is not covered by the sources below. ## Sources [^1]: Account-level Business Hours and Timezone settings are used only for reporting, and only when a Studio flow has no Time Based Rules component. Source: [Account Settings that Impact Studio](https://studio.talkdesk.com/docs/account-level-settings-that-impact-studio), Account Settings that Impact Studio, Business Hours and Timezone rows. Checked 2026-10-02. [^2]: The account Inbound Call Recording setting applies to a Studio flow that has no Record component, and it does not work with Forward to external number. Source: [Account Settings that Impact Studio](https://studio.talkdesk.com/docs/account-level-settings-that-impact-studio), Account Settings that Impact Studio, Inbound Call Recording row. Checked 2026-10-02. [^3]: Assignment and Dial can ring at most 10 agents at the same time, and Talkdesk warns that ringing several agents at once can add latency. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, Agents to ring. Checked 2026-10-02. [^4]: The Alternative Exits section of Assignment and Dial gives queued callers keypress ways out of the waiting queue, for example back to the Standard IVR. Source: [Configuring Routing Settings](https://studio.talkdesk.com/docs/configuring-routing-settings), Configuring Routing Settings, Alternative Exits. Checked 2026-10-02. [^5]: With Attributes assignment, the admin selects the attributes an agent must have, plus proficiency where configured, and can combine them with AND or OR conditions. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, Assignment by Attributes. Checked 2026-10-02. [^6]: Agents must be in Available status to receive Studio-assigned interactions, and when several agents match, the most idle agent is chosen. Source: [Configuring Routing Settings](https://studio.talkdesk.com/docs/configuring-routing-settings), Configuring Routing Settings, agent status note. Checked 2026-10-02. [^7]: The Assignment and Dial maximum ringing time, after which an unanswered call goes back to the queue, accepts 30 to 600 seconds. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, Maximum ringing time. Checked 2026-10-02. [^8]: Assignment and Dial priority runs from 1, the highest, to 10, the lowest; it can be fixed or taken from a flow variable, and priority outweighs time in queue. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, Priority. Checked 2026-10-02. [^9]: Talkdesk's FAQ says ring group names can be stored in a flow variable and used with the Ring groups assignment type in Assignment and Dial. Source: [Studio FAQs](https://studio.talkdesk.com/docs/faqs), Studio FAQs, question on using variables with Assignment and Dial. Checked 2026-10-02. [^10]: With Single Attempt, Assignment and Dial tries one batch of agents once; with Exhaust it keeps looking for available agents until the maximum waiting time is reached. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, assignment strategy. Checked 2026-10-02. [^11]: Attributes assignment sorts agents by Idle time or Most proficient; Most proficient uses only the first attribute in the list and breaks ties by idle time. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, agent sorting criteria. Checked 2026-10-02. [^12]: Assignment and Dial has No answer, Maximum waiting time reached and No match found exits, and each can send the call to a component such as Voicemail. Source: [Configuring Routing Settings](https://studio.talkdesk.com/docs/configuring-routing-settings), Configuring Routing Settings, exit sections. Checked 2026-10-02. [^13]: Assignment and Dial offers Ring Groups, Attributes or Agents as assignment types, and only one type can be selected per component. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, assignment type. Checked 2026-10-02. [^14]: Assignment and Dial sets a maximum waiting time, waiting music and waiting messages, which can use Amazon Polly text-to-speech, an uploaded audio file or an external URL or variable. Source: [Preferences (Assignment and Dial)](https://studio.talkdesk.com/docs/assignment-dial-preferences), Preferences, Maximum waiting time and Waiting messages. Checked 2026-10-02. [^15]: To assign numbers, an admin opens the Studio app, clicks the No numbers dropdown on the flow's card, selects Manage numbers, ticks each number, clicks Save and confirms in the modal. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, numbered steps. Checked 2026-10-02. [^16]: The account Blocklist setting affects Studio flows. Source: [Account Settings that Impact Studio](https://studio.talkdesk.com/docs/account-level-settings-that-impact-studio), Account Settings that Impact Studio, Blocklist row. Checked 2026-10-02. [^17]: The Studio Calendar Based Rules component sets routing for particular periods or days, such as public holidays, with differentiated greetings and routing to another number or voicemail. Source: [Hours of Operations](https://studio.talkdesk.com/docs/hours-of-operations), Hours of Operations, Calendar Based Rules. Checked 2026-10-02. [^18]: An agent assigned a queue callback sees the caller's name and number, the request time, the originating queue and the dialed number, and can accept or decline it. Source: [Request Callback from Queue](https://studio.talkdesk.com/docs/request-callback-from-queue), Request Callback from Queue, agent experience. Checked 2026-10-02. [^19]: Callback and voicemail from queue are set up as Assignment and Dial Alternative Exits: pick a keypress, name the exit and choose Request callback from queue or Voicemail in Send to. Source: [Callback and Voicemail from Queue](https://studio.talkdesk.com/docs/callback-and-voicemail-from-queue), Callback and Voicemail from Queue, configuration. Checked 2026-10-02. [^20]: Request Callback from Queue takes its Invalid Inbound Phone Number exit for anonymous callers, and Talkdesk suggests collecting a number with Input IVR and requesting the callback again from that variable. Source: [Exits (Request Callback from Queue)](https://studio.talkdesk.com/docs/exits-request-callback-from-queue), Exits (Request Callback from Queue), Invalid Inbound Phone Number. Checked 2026-10-02. [^21]: Request Callback from Queue lets a caller keep their place in the assignment queue without staying on hold; after confirmation the caller hears the Request successful message and the call hangs up. Source: [Request Callback from Queue](https://studio.talkdesk.com/docs/request-callback-from-queue), Request Callback from Queue, overview and process. Checked 2026-10-02. [^22]: Talkdesk states that queued callbacks are not charged while waiting in the queue, only when they are served. Source: [Request Callback from Queue](https://studio.talkdesk.com/docs/request-callback-from-queue), Request Callback from Queue, cost note. Checked 2026-10-02. [^23]: To call back a number the caller chooses, an Input IVR stores the digits in a flow variable, and Request Callback from Queue uses it through From variable in the flow context under Number to dial. Source: [Number Capture for Request Callback from Queue](https://studio.talkdesk.com/docs/number-capture-for-callbacks), Number Capture for Request Callback from Queue, components. Checked 2026-10-02. [^24]: A queue callback can dial the caller's original number, another number defined earlier in the flow, or the original number plus an extension. Source: [Request Callback from Queue](https://studio.talkdesk.com/docs/request-callback-from-queue), Request Callback from Queue, number to dial. Checked 2026-10-02. [^25]: Request Callback from Queue also has Invalid Outbound Caller ID, Duplicate Request (when multiple requests are disallowed) and Call Finished exits. Source: [Exits (Request Callback from Queue)](https://studio.talkdesk.com/docs/exits-request-callback-from-queue), Exits (Request Callback from Queue), exit list. Checked 2026-10-02. [^26]: If no agent becomes available within the callback time limit, an optional timeout message can play, and the missed callback is marked as an Abandoned Call. Source: [Request Callback from Queue](https://studio.talkdesk.com/docs/request-callback-from-queue), Request Callback from Queue, timeout. Checked 2026-10-02. [^27]: Chained routing sends a call that a first ring group does not answer to another ring group by placing a further Assignment and Dial component on the first one's exits. Source: [Chained Routing - ring groups](https://studio.talkdesk.com/docs/chained-routing), Chained Routing - ring groups, configuration steps. Checked 2026-10-02. [^28]: Studio is opened from Admin > Studio, and Create flow offers Empty flow to build from scratch or Import flow to create a flow from a JSON file. Source: [Getting Started](https://studio.talkdesk.com/docs/getting-started-studio), Getting Started, creating a flow. Checked 2026-10-02. [^29]: The Flow Statuses and Versions page states that no calls can be made or directed to a Studio flow version with draft status (disputed). Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Draft. Checked 2026-10-02. [^30]: Clicking Edit on a published Studio flow creates a draft copy, and the previous version stays published while the draft is worked on. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Editing a published flow. Checked 2026-10-02. [^31]: The default error behaviour of Assignment and Dial is End flow, and Talkdesk strongly advises admins to configure its error handling so the call can continue. Source: [Error Handling](https://studio.talkdesk.com/docs/error-handling), Error Handling, default behaviours table and recommendation. Checked 2026-10-02. [^32]: Studio components other than the start and end steps have an Error handling section with four choices: use default behaviour, end flow, follow an existing exit, or define a custom exit. Source: [Error Handling](https://studio.talkdesk.com/docs/error-handling), Error Handling, configuration options. Checked 2026-10-02. [^33]: A single Talkdesk Studio flow can be assigned to several phone numbers. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, rules paragraph. Checked 2026-10-02. [^34]: Account-level Holiday Hours determine routing before a flow's Time Based Rules component runs, and are used for reporting if the flow has no such component. Source: [Account Settings that Impact Studio](https://studio.talkdesk.com/docs/account-level-settings-that-impact-studio), Account Settings that Impact Studio, Holiday Hours row. Checked 2026-10-02. [^35]: Each Standard IVR custom exit sets the key the caller presses, a display name and the next step the flow runs when that key is pressed. Source: [Exits (Standard IVR)](https://studio.talkdesk.com/docs/exits-standard-ivr), Exits (Standard IVR), Custom Exits. Checked 2026-10-02. [^36]: An IVR whose Timeout or Invalid Input exit loops back to itself will probably hit the 500-step execution quota if a caller never responds, so loops should be bounded or end at an agent or voicemail (inferred). Source: [Service Quotas](https://studio.talkdesk.com/docs/service-quotas-studio), Service Quotas, Maximum executed steps per Flow Execution row; read with Exits (Standard IVR), Timeout. Checked 2026-10-02. [^37]: Talkdesk notes that errors appear on each save while an IVR flow is being built, which is expected until all steps are configured. Source: [Setting up IVR Menu Options](https://studio.talkdesk.com/docs/setting-up-ivr-menu-options), Setting up IVR Menu Options, note. Checked 2026-10-02. [^38]: A Standard IVR has a Timeout setting for how many seconds to wait for a selection before redirecting, and an Invalid Input exit for unconfigured keys. Source: [Exits (Standard IVR)](https://studio.talkdesk.com/docs/exits-standard-ivr), Exits (Standard IVR), Timeout and Invalid Input. Checked 2026-10-02. [^39]: A Studio Module is a reusable block of steps that several flows can reference, and editing a published module applies the change to every flow that references it. Source: [Modules](https://studio.talkdesk.com/docs/modules), Modules, overview and editing a published module. Checked 2026-10-02. [^40]: Only published Studio Modules can be used in flows, and a module cannot be deleted while flows reference it. Source: [Modules](https://studio.talkdesk.com/docs/modules), Modules, statuses and limitations. Checked 2026-10-02. [^41]: Phone numbers cannot be assigned to a Talkdesk Studio flow of the outbound call type. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, rules paragraph. Checked 2026-10-02. [^42]: A Talkdesk phone number can be assigned to only one Studio flow at a time. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, rules paragraph. Checked 2026-10-02. [^43]: A Studio flow can have only one draft version, and a flow can be built or changed only in its draft version. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Draft. Checked 2026-10-02. [^44]: Studio roles have View, Manage and Publish permissions; Manage allows editing, saving, restoring and duplicating flows, and Publish allows publishing flows and managing phone number assignments. Source: [Permissions to Use Studio Flows, Modules, and Governance](https://studio.talkdesk.com/docs/permissions-to-use-studio-flows-and-modules), Permissions to Use Studio Flows, Modules, and Governance, permission levels. Checked 2026-10-02. [^45]: The Studio Publish permission requires the View and Manage permissions as prerequisites. Source: [Permissions to Use Studio Flows, Modules, and Governance](https://studio.talkdesk.com/docs/permissions-to-use-studio-flows-and-modules), Permissions to Use Studio Flows, Modules, and Governance, access requirements. Checked 2026-10-02. [^46]: A Studio flow has only one published version, so publishing a new draft automatically archives the previously published version. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Editing a published flow and Archived. Checked 2026-10-02. [^47]: To publish a Studio flow, the admin saves and validates the draft and then clicks Publish in the top-right corner. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Publishing a flow. Checked 2026-10-02. [^48]: A Studio flow must be published before it can be assigned to one or more phone numbers. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Publishing a flow. Checked 2026-10-02. [^49]: The Studio service quota is 500 flows per account. Source: [Service Quotas](https://studio.talkdesk.com/docs/service-quotas-studio), Service Quotas, Flows per account row. Checked 2026-10-02. [^50]: A single Studio flow execution can run at most 500 steps. Source: [Service Quotas](https://studio.talkdesk.com/docs/service-quotas-studio), Service Quotas, Maximum executed steps per Flow Execution row. Checked 2026-10-02. [^51]: A published Studio flow cannot be renamed directly; the workaround is Duplicate version to a new flow, rename and publish it, then reassign the numbers through Manage numbers. Source: [Studio FAQs](https://studio.talkdesk.com/docs/faqs), Studio FAQs, question on renaming flows. Checked 2026-10-02. [^52]: An archived Studio flow version can be restored with the Restore version button, which creates a draft copy of it; if a draft already exists, Studio shows a warning. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Restoring an archived version of a flow. Checked 2026-10-02. [^53]: Saving a Studio flow triggers automatic error verification, and errors must be resolved before the flow can be published. Source: [Flow Statuses and Versions](https://studio.talkdesk.com/docs/flow-status-and-versions), Flow Statuses and Versions, Draft and Publishing a flow. Checked 2026-10-02. [^54]: The Assigning a Flow to a Number page states that once a flow is validated and saved, any numbers assigned to it reflect the changes (disputed). Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, closing paragraphs. Checked 2026-10-02. [^55]: Numbers that share one Studio flow will probably share the same Time Based Rules schedule unless the flow branches before that component, so numbers that need different hours are simpler to give separate flows (inferred). Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), introduction; read with Assigning a Flow to a Number rules. Checked 2026-10-02. [^56]: The Single Device Mode account device setting must be enabled for Talkdesk Studio to work. Source: [Account Settings that Impact Studio](https://studio.talkdesk.com/docs/account-level-settings-that-impact-studio), Account Settings that Impact Studio, Device Settings row. Checked 2026-10-02. [^57]: Each Time Based Rules exit has a name, a timezone, one or more time ranges and a Send to destination component. Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), exit configuration. Checked 2026-10-02. [^58]: Time Based Rules exits apply only to the phone numbers associated with the flow that contains them. Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), introduction. Checked 2026-10-02. [^59]: When several Time Based Rules steps run on the same flow path, the last one executed decides whether the call is reported as inside or outside business hours. Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), notes. Checked 2026-10-02. [^60]: A call that leaves a Time Based Rules component through the No match exit is reported as outside business hours. Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), No match. Checked 2026-10-02. [^61]: The Studio Time Based Rules component routes interactions to agents during defined business hours and can send contacts to voicemail outside them. Source: [Hours of Operations](https://studio.talkdesk.com/docs/hours-of-operations), Hours of Operations, Time Based Rules. Checked 2026-10-02. [^62]: A Time Based Rules exit must be set to Report as: Inside Business Hours for calls through it to be counted as inside business hours. Source: [Exits (Time Based Rules)](https://studio.talkdesk.com/docs/exits-time-based-rules), Exits (Time Based Rules), Report as note. Checked 2026-10-02. [^63]: Talkdesk recommends placing test calls to the numbers assigned to a Studio flow to hear what callers will hear. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, closing paragraphs. Checked 2026-10-02. [^64]: A number can be unassigned from a Studio flow at any time by unchecking it in the Manage Numbers side panel and clicking Save. Source: [Assigning a Flow to a Number](https://studio.talkdesk.com/docs/assigning-a-flow-to-a-number), Assigning a Flow to a Number, closing paragraphs. Checked 2026-10-02. [^65]: A Studio Incoming Call flow covers an interaction from the moment the inbound call arrives until the call ends or its post-call actions, such as surveys, finish. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, Incoming Call section. Checked 2026-09-25. [^66]: Talkdesk Studio has four flow types: API Request, Incoming Call, Incoming Message and Outgoing Call. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, overview list. Checked 2026-09-25. [^67]: Step-level Studio execution data is available through the Explore API as the studio_flow_execution report type, with at most one month of data per request. Source: [Studio Flow Execution Report](https://docs.talkdesk.com/docs/studio-flow-execution-report.md), Studio Flow Execution Report, overview and data availability notes. Checked 2026-09-25.