{"id":1615,"date":"2026-03-24T13:54:29","date_gmt":"2026-03-24T13:54:29","guid":{"rendered":"https:\/\/onesystemcrm.com\/help\/?post_type=docs&p=1615"},"modified":"2026-03-24T13:54:29","modified_gmt":"2026-03-24T13:54:29","password":"","slug":"interactive-voice-response-ivr-guide-triggers-actions","status":"publish","type":"docs","link":"https:\/\/onesystemcrm.com\/help\/docs\/interactive-voice-response-ivr-guide-triggers-actions\/","title":{"rendered":"Interactive Voice Response (IVR) Guide – Triggers & Actions"},"content":{"rendered":"
\n

What is the IVR System?<\/strong><\/h1>\n

An Interactive Voice Response (IVR) is an automated phone system that interacts with callers through pre-recorded messages, text-to-speech prompts, and keypad inputs. It allows businesses to guide callers to the right department, collect information, or provide self-service options without human intervention. In OneSystemCRM, IVR is set up using workflows, enabling automated call routing and customer engagement.<\/p>\n

To better understand how IVR works within workflows, refer to the table below, which outlines the key triggers, actions, and conditional logic used to build an IVR system.<\/p>\n\n\n\n\n\n\n\n\n\n\n
IVR Component<\/strong><\/td>\nFunction<\/strong><\/td>\nUse case<\/strong><\/td>\n<\/tr>\n
Trigger – Start IVR<\/td>\n\n

Activates the IVR system when a call is received on a designated number.<\/p>\n<\/td>\n

A customer calls the business number, and the IVR workflow begins.<\/td>\n<\/tr>\n
Action – Say\/Play Message<\/td>\nPlays a recorded or text-to-speech message to guide the caller.<\/td>\n\u201cWelcome to XYZ Company! Press 1 for Sales, Press 2 for Support.\u201d<\/span><\/td>\n<\/tr>\n
Action – Gather Input<\/td>\nCollects user keypress responses for navigation within the IVR menu.<\/td>\nCaller presses 1 for Sales, 2 for Support.<\/td>\n<\/tr>\n
Condition – Map Caller Input<\/span><\/td>\nDirects the caller to the appropriate action or team based on input.<\/td>\nIf 1 is pressed \u2192 Route to Sales Team, if 2 \u2192 Route to Support.<\/td>\n<\/tr>\n
Action – Connect Call<\/td>\nTransfers the caller to a selected agent, department, or external number.<\/td>\nAfter pressing 1, the call is forwarded to a sales rep.<\/td>\n<\/tr>\n
Action – Record Voicemail<\/td>\nAllows callers to leave a voicemail if no one is available to take the call.<\/td>\nIf agents are unavailable, the IVR prompts the caller to leave a message.<\/td>\n<\/tr>\n
Condition – Call Status Check<\/td>\nDetermines what happens based on call outcome (answered, missed, or disconnected).<\/td>\n\n

If unanswered, play a message and offer a callback option.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\n

Key Benefits of IVR<\/strong><\/h2>\n
    \n
  • Enhanced Call Management:\u00a0<\/strong>Automatically directs callers to the appropriate team, reducing wait times and improving customer experience.<\/li>\n<\/ul>\n
      \n
    • Improved Efficiency:\u00a0<\/strong>Eliminates the need for manual call handling, freeing up staff for higher-value tasks.<\/li>\n<\/ul>\n
        \n
      • 24\/7 Availability:<\/strong>\u00a0Enables businesses to handle customer inquiries at any time, even outside business hours.<\/li>\n<\/ul>\n
          \n
        • Customizable Interactions:\u00a0<\/strong>Supports text-to-speech messages, call routing, voicemail collection, and data gathering based on caller input.<\/li>\n<\/ul>\n
            \n
          • Seamless Workflow Integration:\u00a0<\/strong>Works within OneSystemCRMautomation system to trigger actions like follow-ups, appointment scheduling, or lead categorization.<\/li>\n<\/ul>\n
            \n

            Configuring IVR Using Workflows<\/strong><\/h2>\n

            Setting up IVR in OneSystemCRM can be done in two ways: using a workflow recipe for quick setup or creating one from scratch for full customization. Below, we explain both methods:<\/p>\n

            Method 1: Using the IVR Workflow Recipe (Faster Setup)<\/strong><\/u><\/h3>\n

            If you want a prebuilt IVR structure to save time, you can use the IVR Workflow Recipe, which includes predefined triggers, actions, and conditions.<\/p>\n

            Navigate to\u00a0Automation<\/strong> from your OneSystemCRM dashboard. Click Create Workflow<\/strong>, then click\u00a0Select a Recipe\u00a0<\/strong>option to quickly set up a preconfigured IVR system with minimal adjustments.<\/p>\n

            <\/p>\n

            S<\/strong>electing the IVR Workflow Recipe<\/strong><\/p>\n

            Once inside the workflow creation section, use the recipe selection option to simplify setup. This recipe includes essential triggers, actions, and call routing logic, reducing the need for manual configuration. Select the IVR Workflow recipe and proceed to customize it based on your business needs.<\/p>\n

            <\/p>\n

            Customize the Trigger<\/strong><\/p>\n

            Phone Number:<\/strong>\u00a0In the workflow trigger settings, select the phone number that will be used for the IVR system. This ensures that incoming calls are properly routed to trigger the IVR workflow. If the number is not correctly mapped, the IVR system will not function. Subsequent IVR actions will rely on this configuration to guide callers through the automated process. When you click the dropdown, It shows all the available phone numbers of the users. you can choose one or more phone numbers.<\/p>\n

            <\/p>\n

            Say\/Play Messages<\/strong><\/h4>\n

            Modify the text-to-speech or uploaded audio file in the workflow action settings to ensure the IVR delivers accurate and professional prompts to callers. This step allows you to customize greetings, menu options, and instructions for a seamless caller experience.<\/p>\n

            <\/p>\n

            Call Routing Logic<\/strong><\/h4>\n

            Modify the input conditions within the IVR workflow to ensure callers are directed to the correct department or individual. Based on the keypress selections made by the caller, you can define specific routing paths, such as transferring calls to customer support, sales, or voicemail. This setup ensures an efficient and seamless caller experience. When you are done with the set up, Save and Publish the workflow to activate the IVR.<\/p>\n

            <\/p>\n

            Method 2: Creating an IVR Workflow from Scratch (Full Customization)<\/strong><\/u><\/h3>\n

            For businesses with specific call routing needs, building an IVR system from scratch allows complete control over workflow design.<\/p>\n

            Step 1: Access Workflow Builder<\/strong><\/h3>\n

            Go to\u00a0Automation<\/strong> in your OneSystemCRM account and click on “+ Create Workflow”<\/strong>\u00a0then click\u00a0\u201cStart from scratch”<\/strong>\u00a0This will open the workflow builder, where you can configure your IVR system either from scratch or by using a prebuilt IVR workflow recipe.<\/p>\n

            <\/p>\n

            Step 2: Add the IVR Trigger<\/strong><\/h3>\n

            Click on\u00a0\u201d+ Add New Trigger\u201d<\/strong>\u00a0in the workflow builder and search for\u00a0\u201cStart IVR\u201d\u00a0<\/strong>from the list of available triggers. Selecting this trigger will enable the IVR workflow to activate when a call is received on the assigned phone number. This is the first step in configuring an automated IVR system to handle incoming calls efficiently.<\/p>\n

            <\/p>\n

            Step 3: Configuring Start IVR Workflow Trigger<\/strong><\/h3>\n

            <\/h4>\n

            Assigning a Phone Number<\/strong><\/h4>\n

            In the workflow trigger settings, select the phone number that will be used for the IVR system. Keep in mind that a phone number can only be assigned to one IVR workflow at a time. Once selected, click Save to confirm the configuration. This ensures that incoming calls to the assigned number will activate the IVR workflow.<\/p>\n

            <\/p>\n

            Step 4: Configure IVR Actions<\/strong><\/h3>\n

            After adding the trigger, set up the actions to define how the IVR interacts with callers. Below are the available IVR workflow actions you can use for your workflow. In the next few steps, we will go through each IVR workflow action one by one.<\/p>\n

            <\/p>\n

            Gather Input on Call Workflow Action<\/u><\/strong><\/h4>\n

            The Gather Input on Call action allows businesses to collect caller responses through keypad inputs, enabling seamless navigation within the IVR system. This action is essential for directing callers to the appropriate department, retrieving account information, or processing customer requests efficiently.<\/p>\n

            When setting up this action, you can configure the following options:<\/p>\n

              \n
            • Say or Play Message:<\/strong>Choose how the IVR presents the message to callers:\n
                \n
              • Say Message:<\/strong>\u00a0Type a text message that will be converted to speech.<\/li>\n
              • Play Message:\u00a0<\/strong>Upload a pre-recorded audio file for playback. Example, \u201cPress 1 for account balance, Press 2 to speak with a representative.\u201d<\/li>\n<\/ul>\n<\/li>\n
              • Text to Say:\u00a0<\/strong>Enter the specific message you want callers to hear before making a selection. This ensures clear instructions are given for the available options.<\/li>\n
              • Language & Message Voice:\u00a0<\/strong>When using text-to-speech, the default language is US English. You can choose between a Male or Female voice to personalize the caller experience.<\/li>\n
              • Number of Loops:\u00a0<\/strong>Determines how many times the message will be repeated before the system stops waiting for a response. This helps ensure callers have enough time to understand and react to the prompt.<\/li>\n<\/ul>\n

                Match Conditions<\/u><\/strong><\/p>\n

                The \u201cMatch Conditions\u201d Toggle is used to define how the system processes caller input and directs them to the appropriate workflow path based on keypress responses. When Match Conditions is enabled, it allows you to create multiple branches based on different keypress inputs from the caller. Each branch represents a possible response, guiding the caller through specific actions based on their selection.<\/p>\n

                Components of Match Conditions:<\/u><\/strong><\/p>\n

                  \n
                • Branch Name:\u00a0<\/strong>A descriptive label for the keypress action.
                  \nExample: \u201cCaller Pressed 1\u201d or \u201cCaller Pressed 2\u201d<\/li>\n
                • On Key Press:<\/strong>\u00a0Defines the key that a caller must press to follow a particular branch.
                  \nExample: If the caller presses 1, they will be directed to one action; if they press 2, they will follow another action.<\/li>\n
                • None Branch:\u00a0<\/strong>Defines what happens if the caller does not press a valid key.
                  \nExample: If the caller presses an invalid key (not 1 or 2), they can be routed to a default action, such as hearing the menu again or being redirected to a human agent.<\/li>\n<\/ul>\n

                  Advanced Settings for Input Collection<\/u><\/strong><\/p>\n

                    \n
                  • Stop Gathering After (Seconds):\u00a0<\/strong>Set the time limit for caller input, ranging from 5 to 30 seconds. If no input is received within this time frame, the system will proceed accordingly.<\/li>\n
                  • Stop Gathering on Key Press:\u00a0<\/strong>If enabled, input collection stops immediately after the caller presses a key. If disabled, the system will wait until either the time limit is reached or the expected number of keypresses is collected.<\/li>\n
                  • Stop Gathering After (Digits):<\/strong>\u00a0Specify how many digits the system should expect from the caller. Once this number is reached, the input is submitted automatically.<\/li>\n<\/ul>\n

                    <\/h4>\n

                    <\/p>\n

                    <\/h4>\n

                    Say\/Play Message Workflow Action<\/u><\/strong><\/h4>\n

                    The Say\/Play Message action allows businesses to provide instructions or important information to callers using either text-to-speech or a pre-recorded audio file. This action plays a crucial role in guiding callers through the IVR system by delivering automated messages before prompting them for input or directing them to the next step. This action ensures that callers receive clear instructions, whether through automated speech or recorded messages, improving the overall IVR experience.<\/p>\n

                    When configuring this action, you can customize the following settings:<\/p>\n

                      \n
                    • Say or Play Message:\u00a0<\/strong>Choose between two options:\n
                        \n
                      • Say Message:\u00a0<\/strong>Type a text message that will be converted into speech and played to the caller.<\/li>\n
                      • Play Message:\u00a0<\/strong>Upload a pre-recorded audio file that will be played instead of text-to-speech.<\/li>\n<\/ul>\n<\/li>\n
                      • Text or Audio File Input:\u00a0<\/strong>Based on the selection above, you can either type the message directly into the provided text box or upload an audio file.<\/li>\n
                      • Recommended Format:\u00a0<\/strong>For optimal performance, .wav files are recommended, as .mp3 files may not always be compatible.<\/li>\n
                      • Language Support:\u00a0<\/strong>Currently, the default and only supported language for text-to-speech is US English.<\/li>\n
                      • Message Voice:\u00a0<\/strong>When using text-to-speech, you have the option to choose from male voice and female voice.<\/li>\n
                      • Number of Loops:\u00a0<\/strong>Set how many times the message should be repeated before proceeding to the next step. You can use the + and – buttons to adjust the repetition count, with the default being 1 loop.<\/li>\n<\/ul>\n

                        <\/p>\n

                        Connect Call (IVR) Workflow Action<\/u><\/strong><\/h4>\n

                        The Connect Call action allows businesses to seamlessly transfer an ongoing IVR call to a selected user, department, or external phone number. This ensures that callers are quickly connected to the right person or team for further assistance.<\/p>\n

                        When setting up this action, you can configure the following options:<\/p>\n

                          \n
                        • Connect Call To:\u00a0<\/strong>Choose where to direct the call:<\/li>\n
                        • Select Users:\u00a0<\/strong>Pick from existing users within your system to receive the call.<\/li>\n
                        • Add Custom Number:\u00a0<\/strong>Input an external phone number if the call needs to be forwarded outside the organization.<\/li>\n
                        • Multiple Numbers:\u00a0<\/strong>You can add up to 10 numbers, allowing calls to ring on multiple lines for increased availability.<\/li>\n<\/ul>\n

                          Advanced Call Settings<\/u><\/strong><\/p>\n

                            \n
                          • Detect Voicemail:\u00a0<\/strong>Enabling this feature determines whether the call was answered by a person or sent to voicemail. This helps prevent calls from being directed to voicemail boxes unnecessarily. Note: Enabling this may cause minor delays and could result in additional charges.<\/li>\n
                          • Record Call:\u00a0<\/strong>Enable this option to automatically record the connected call for quality assurance or compliance purposes.<\/li>\n
                          • Timeout (Seconds):\u00a0<\/strong>Set the maximum amount of time the system should wait for the recipient to answer the call before redirecting or ending it. The default is 10 seconds, but you can configure it between 1 and 600 seconds.<\/li>\n
                          • Time Limit (Seconds):\u00a0<\/strong>Specify how long the connected call can last. By default, there is no time limit, but you can set a cap of up to 24 hours to ensure calls do not run indefinitely.<\/li>\n<\/ul>\n

                            <\/p>\n

                            End Call (IVR) Workflow Action<\/u><\/strong><\/h4>\n

                            The End Call (IVR) action is used to disconnect an ongoing IVR call. By default, the call will end immediately, but businesses have the option to provide a final message or play a custom sound before disconnecting. This ensures a smooth experience for callers, whether it\u2019s a closing statement or hold music before the call ends.<\/p>\n

                            Configurable Options<\/p>\n

                              \n
                            • Add Voice Instructions:<\/strong>\u00a0Allows you to play a message or sound before ending the call, giving callers a clear indication that the interaction is concluding.<\/li>\n
                            • Say or Play Message:\u00a0<\/strong>Choose between two options:\n
                                \n
                              • Say a Message:\u00a0<\/strong>Type a custom message that the system will convert into speech.<\/li>\n
                              • Play a Message:\u00a0<\/strong>Upload an audio file (recommended format: .wav) to be played before disconnection.<\/li>\n<\/ul>\n<\/li>\n
                              • Text to Say:<\/strong>\u00a0If using text-to-speech, enter the message that will be spoken to the caller before the call ends.<\/li>\n
                              • Language:\u00a0<\/strong>The IVR system currently supports English (US) for text-to-speech conversion.<\/li>\n
                              • Message Voice:<\/strong>\u00a0Select the preferred voice for the text-to-speech feature. Available options: Man, Woman.<\/li>\n
                              • Number of Loops:\u00a0<\/strong>Set how many times the message should repeat before the call disconnects. The default is 1, but you can increase this based on your needs.<\/li>\n<\/ul>\n

                                <\/p>\n

                                Record Voicemail (IVR) Workflow Action<\/u><\/strong><\/h4>\n

                                The Record Voicemail (IVR) action allows callers to leave voice messages when no one is available to answer. This feature is useful for businesses that want to capture important messages and ensure no customer inquiries are missed.<\/p>\n

                                Configurable Options<\/strong><\/p>\n

                                  \n
                                • Play Beep:\u00a0<\/strong>Enables a beep sound to inform callers that voicemail recording has started. This helps provide clarity and confirmation that their message is being recorded.<\/li>\n
                                • Stop Recording After (Seconds of Silence):\u00a0<\/strong>Defines the amount of silence (in seconds) before the system automatically stops recording. The default is 5 seconds, but this can be adjusted to any whole number based on preference.<\/li>\n
                                • Stop Recording on Keypress:\u00a0<\/strong>Allows callers to manually stop the voicemail recording by pressing a designated key. Accepted key values include 0-9, * and #. By default, no key is set, meaning the recording will stop only after the silence threshold is reached.<\/li>\n
                                • Max Recording Length:\u00a0<\/strong>Sets the maximum duration of the voicemail recording. The system allows a range between 1 and 14,400 seconds (4 hours), with the default set at 3,600 seconds (1 hour).<\/li>\n
                                • Add Voice Instructions:\u00a0<\/strong>Provides an option to play a message before the voicemail recording begins. This can be a text-to-speech message or a pre-recorded audio file, ensuring the caller understands the purpose of the voicemail.<\/li>\n<\/ul>\n

                                  <\/p>\n

                                  Implementing Conditional Branching (IF\/ELSE Logic) in IVR Workflows<\/strong><\/u><\/h4>\n

                                  Conditional branching allows businesses to route calls dynamically based on user input, ensuring callers are directed to the appropriate department or action. This is achieved using IF\/ELSE logic in the workflow, where different responses trigger different paths.<\/p>\n

                                  For example:<\/p>\n

                                  If a caller presses 1, the call is routed to Sales.<\/p>\n

                                  If a caller presses 2, the call is directed to Support.<\/p>\n

                                  If no input is received, the system can repeat the prompt or route to a default action.<\/p>\n

                                  Using Conditional Logic with IVR Gather<\/strong><\/p>\n

                                  The IVR Gather action is responsible for collecting user input through keypress responses. Once a caller selects an option, the system processes that input and follows predefined logic to determine the next step.<\/p>\n

                                  Steps to Configure Conditional Logic in IVR Gather:<\/strong><\/p>\n

                                  Add the IVR Gather Action: This prompts the caller to make a selection (e.g., \u201cPress 1 for Service, Press 2 for Appointments\u201d).<\/p>\n

                                  Set Up IF\/Else Condition Logic: Using the \u201cIF\/Else Condition\u201d action in the workflow, select IVR Gather as the condition source.<\/p>\n

                                  Define Key Press Responses<\/strong><\/p>\n

                                  If Press 1, route the caller to a service details message.<\/p>\n

                                  If Press 2, route them to a live agent for booking.<\/p>\n

                                  Handle Unresponsive Calls: If no input is received, configure a fallback action such as repeating the prompt or sending the caller to voicemail.<\/p>\n

                                  <\/h3>\n

                                  <\/p>\n

                                  \n

                                  Frequently Asked Questions<\/strong><\/h2>\n

                                  Q: What happens if a caller ends the call during an IVR workflow?<\/strong><\/span><\/p>\n

                                  If the caller ends the call at any point in the workflow, the contact will still move to the next step, but all IVR-specific actions (such as call transfers or voicemail recordings) will be skipped. Other workflow actions, such as tagging the contact or sending follow-up messages, will continue executing as configured.<\/p>\n

                                  Q: Can I use multiple phone numbers with the same IVR workflow?<\/strong><\/span><\/p>\n

                                  No, each phone number can only be assigned to one IVR workflow at a time.<\/p>\n

                                  Q: Can I connect IVR calls to external numbers?<\/strong><\/span><\/p>\n

                                  Yes, the IVR Connect Call action allows calls to be transferred to users within the system or external numbers.<\/p>\n

                                  Q: What happens if a caller doesn\u2019t respond in time?<\/strong><\/span><\/p>\n

                                  You can configure a timeout setting in the IVR Gather action to either repeat the prompt or redirect the call to a fallback action (e.g., voicemail).<\/p>\n

                                  Q: Where Can I Find the IVR Call Recordings?<\/span><\/strong><\/p>\n

                                  All voicemail recordings are stored and can be accessed in the Conversations tab within OneSystemCRM. This allows businesses to review, download, and manage voicemail messages efficiently.<\/p>\n

                                  Q: Are we able to perform a blind or warm transfer within an IVR call?<\/span><\/strong><\/p>\n

                                  No. Currently, when an IVR call is routed to the web app, blind and warm transfers are not supported.<\/p>\n

                                  Q: Are we able to perform a blind or warm transfer within an IVR call?<\/strong>
                                  \nNo. Currently, when an IVR call is routed to the web app, blind and warm transfers are not supported.<\/p>\n<\/div>\n

                                  \n
                                  \n
                                  <\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

                                  What is the IVR System? An Interactive Voice Response (IVR) is an automated phone system that interacts with callers through […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_category":[81],"doc_tag":[],"class_list":["post-1615","docs","type-docs","status-publish","hentry","doc_category-developer-resources"],"year_month":"2026-09","word_count":2781,"total_views":"38","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"usamasaeed219","author_nicename":"usamasaeed219","author_url":"https:\/\/onesystemcrm.com\/help\/author\/usamasaeed219\/"},"doc_category_info":[{"term_name":"Developer Resources","term_url":"https:\/\/onesystemcrm.com\/help\/docs-category\/developer-resources\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/comments?post=1615"}],"version-history":[{"count":1,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1615\/revisions"}],"predecessor-version":[{"id":1616,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1615\/revisions\/1616"}],"wp:attachment":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/media?parent=1615"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_category?post=1615"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_tag?post=1615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}