{"id":130,"date":"2021-08-20T11:53:04","date_gmt":"2021-08-20T16:53:04","guid":{"rendered":"https:\/\/support.evs7.com\/?post_type=ht_kb&p=130"},"modified":"2021-08-20T11:53:04","modified_gmt":"2021-08-20T16:53:04","slug":"using-fields-variables-in-scripts-messages","status":"publish","type":"ht_kb","link":"https:\/\/support.evs7.com\/knowledge-base\/using-fields-variables-in-scripts-messages\/","title":{"rendered":"Using Fields & Variables in Scripts & Messages"},"content":{"rendered":"\n

Collecting information via fields is critical for operators. Fields allow unique information to be collected in the script and then sent via messages.<\/p>\n\n\n\n

Default Fields<\/h2>\n\n\n\n

You can view default fields and any other fields you’ve created by navigating to the “System Settings” under the gear icon on the top right of the admin portal.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

You’ll notice that there are 6 default fields created for you as a standard. These allow operators to gather basic information (such as Name or Call Back Number) about the caller without having to create any new fields.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Creating New Fields<\/h2>\n\n\n\n

There are two way you can create new fields. <\/p>\n\n\n\n

The first way is to click the “+ Add Field” link within the Field Manager. <\/p>\n\n\n\n

Alternatively, you can also add a new field from the edit script page when editing a client script.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This will prompt a modal with some options for your new field:<\/p>\n\n\n\n

  • Name – This is the name of the field you’ll insert into the script using brackets such as {{field_name}}. <\/li>
  • Description – Description of what should be inserted into the field. The agent will see this before they complete the field.<\/li>
  • Field Type – Select from text-field (standard), text-box (bigger box for notes type fields), checkbox (click to select), or dropdown (choose from preset options)<\/li><\/ul>\n\n\n\n

    <\/p>\n\n\n\n

    \"\"
    Note that when adding an items list in a dropdown type, hit the TAB button after each option you type.<\/figcaption><\/figure>\n\n\n\n

    Adding Fields to your Scripts<\/h2>\n\n\n\n

    Navigate to edit your script. By default, a few fields will already appear in a script if you haven’t edited it yet.<\/p>\n\n\n\n

    \"\"
    The {{brackets}} represent fields the operator can collect during calls.<\/figcaption><\/figure>\n\n\n\n

    When in editing mode, hover your mouse over the icon below the script that reads “User Defined Fields” then click to view available fields. Then click the clipboard icon beside the field you want to insert to copy it to your clipboard.<\/p>\n\n\n\n

    \"\"<\/figure><\/div>\n\n\n\n

    Once it’s been copied to your clipboard, paste it into the script where you want it.
    (Ctrl+V or Right click then Paste)<\/p>\n\n\n\n

    \"\"<\/figure><\/div>\n\n\n\n

    Once you get this process down it’s pretty easy and quick to create and paste fields any where in your scripts. <\/p>\n\n\n\n

    Adding Variables to the Greeting, Special Instructions, or Scripts<\/h2>\n\n\n\n

    Variables allow you to add pieces of information that “vary” depending on the situation. Some examples could be the agent’s name, the client name, the caller ID of the caller, etc. These can be useful for adding some context and can be inserted not only in the Script and Message, but also in the Greeting or Special Instructions sections.<\/p>\n\n\n\n

    In this example, we’ll add the agent’s first name to the Greeting using the {{agent.firstname}} tag.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    From the operator’s perspective this is how it would appear:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Here’s an example of variables being used in a Message template:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    In this scenario, it would automatically grab the caller’s caller ID number along with the agent’s name so they don’t have to manually type these things.<\/p>\n\n\n\n

    Collected Fields in the Message<\/h2>\n\n\n\n

    When the agent collects information in fields in the script, these can also show up in the Message automatically.<\/p>\n\n\n\n

    Navigate to the Message template via the Drop Drop navigation inside the Client account page.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    The {{gathered_information}}<\/strong> tag automatically formats and displays any collected fields from the script. This takes the hassle out of recreating all the fields in the message template.<\/p>\n\n\n\n

    This simple message template will actually display ALL fields collected by agents:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Assuming fields are collected, here’s how it could look for the agents before it’s emailed or texted:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    You can also insert fields or variables manually into the message as needed.<\/p>\n\n\n\n

    Pro-tip:<\/strong> Use the default “Caller_Name” field when possible because it’s used reports and other areas to quickly see the person’s name.<\/p>\n\n\n\n

    You should now have a good understanding of fields and variables and how to effectively use them when building scripts and messages.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Collecting information via fields is critical for operators. Fields allow unique information to be collected in the script and then sent via messages. Default Fields You can view default fields and any other fields you’ve created by navigating to the “System Settings” under the gear icon on the top right…<\/p>\n","protected":false},"author":2,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[19],"ht-kb-tag":[],"class_list":["post-130","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-client-accounts"],"_links":{"self":[{"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb\/130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/comments?post=130"}],"version-history":[{"count":3,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb\/130\/revisions"}],"predecessor-version":[{"id":148,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb\/130\/revisions\/148"}],"wp:attachment":[{"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb-category?post=130"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/support.evs7.com\/wp-json\/wp\/v2\/ht-kb-tag?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}