The version of your iService system is displayed at the bottom of the iService User Interface as shown below.
The version numbering is comprised of four sections.
1) The major release number (7)
2) The minor release number (6)
3) The build number (089)
4) The build date and time (2017.05.22 - 09:43:12).
New Features Release 7.8 continues the theme of minor changes to the user interface, but major changes to the backend related to performance, security, and interaction properties. Case Properties Prior to v7.8, interaction properties were available for questions, answers, and find answers articles. A new type of property, Case Property, was added to store a single value associated with an entire case. If you have question properties used to track a value associated with the overall discussion, like “Nature of Inquiry,” you’ll probably want to convert them to Case properties. This is because question and answer properties are associated with a specific interaction within a case (i.e., message thread), rather than the entire discussion. You can see this depicted in the example below. The case begins with a customer email, followed by an autoresponse and agent response. The customer then sends a follow up reply, and the thread continues. Within that case you might have two values saved if you were using a question property to track the nature of the question. You now have the option to use a Case Property that only has a single value stored for the entire conversation.
New Interaction Property Value Types We’ve added two new database field types for storing interaction property values: Integer and Number. As the name implies, use a property value type of Integer when you require the user to enter a whole number (-1, 0, 1, 2, 3 etc.). This would be used when storing a value for a property like “Quantity.” When you need to save a number that can include decimal values, like currency, use the new “Number” property value type. Both Integer and Number support mathematical operations. If you were previously using a value type of “Text” for numbers, you should consider one of these new formats. Integrating iService With Other Apps We’ve continued to expand on the Zapier integration, adding support for interaction property values within Zapier triggers and improving error handling. Customer Portal Did you know that you have a customer portal built into your iService tenant that allows customers to submit questions, view answers, and search your knowledgebase? Just append /f/customerportal-treeview to your iService URL to see yours. This is a built-in example that can be customized or used out of the box. The portal is designed so it can be easily branded to fit your website. Check out the example on our website at https://1to1.iservicecrm.com/f/customerportal-treeview. Some changes to the portal in this release are: •Added pagination to the My Inbox list of the user’s history •Revised the topic tree layout to make it more intuitive •Fixed an issue with displaying the article list after login •Revised the form to support including custom top level menus and incorporating chat New Customer Chat Form We’ve added another customer chat interface that’s responsive for mobile devices. You can use the form without changes, or as a template for your own custom chat form. Append /f/chat2 to your tenant URL to load the form.
Support for reCaptcha in iService Form We’ve added support for the Google reCaptcha service to prevent automated form submissions. We support reCaptcha v2, which you can learn about at https://www.iservice.info/guides/forms/index.html?adding-recaptcha.htm.
Small Features and Bug Fixes User Interface Changes Added filter name to the Interaction Status Audit - to make it easier to understand which filter was used. We previously only provided the Filter ID. 7.7 7.8 Remove GUIDS from displays - For tenants using Google login, we displayed the Google GUID as an email address in various forms. This fix ensures the GUID, which is just a string of values, and other non-email address logins are not shown in email listings or menus when composing email responses. Remove Answer button when quote is reassigned - After reassigning an open quote, the answer button continued to be displayed. This triggered an error when the agent attempted to modify the quote. Instead, the button now changes to a Get This button so it is properly assigned before presenting the forward actions. Certain characters parsed incorrectly - We had an issue with the characters =C2=A0 within email messages being converted to  in quoted-printable text. We also fixed an issue with emails from Yahoo inserting a stray character. "Resolved by" list of agents should be in alphabetical order – This drop down list was sorting on ID, instead of alphabetical. "Interaction is already resolved" when resolving an interaction in my queue – A timing issue was causing this error to display in some installations. The issue was caused by the auto save function running after the agent resolved the interaction.
Technical Changes During tenant creation, put Blob tables inside a separate filegroup – Prior to 7.8, during tenant creation we created all tables inside a single filegroup. We modified the tenant creation script to create the FilesRawMessages, FilesText, and Files tables in a separate logical filegroup. This allows for database administrators to have the option to decide where to store these large files, separate from the primary database mdf if they choose. Change InteractionsPropertyDefinitions table for property types - Schema level change:The following binary type columns: [isQuestionNotAnswer] and [isFindAnswer] were removed and rolled up into a single column named [purpose] to define property type attributes. This column is an nvarchar(32), with the following possible values as of 7.8: FindAnswer, Answer, Question, Case. Serve ckeditor.js locally rather than use CDN – The files required for the CKEditor rich text editor are now located within the iService website, and no longer loaded from a CDN. X-Frame-Options Header - The header within iService Forms is now set by default to DENY, which will make all forms unable to be displayed inside frames on other pages. Without the $header variable, iService forms cannot be embedded into any website as an iFrame. $header$ has been extended to allow frames on a case by case basis. NOTE: Because Chrome does not support this approach, we've not included an option for allow-from, which specifies the domain in which the form can be embedded. Add Non-clustered index on SmtpOut for mailpopper outbound thread - This was identified as a critically missing index which would be heavily used by iService mailpopper if it existed. Put index with unique constraint on name column in contactslogins – This index was lost on some tenants after 7.6 updates. It’s added back as part of the 7.8 update if missing. Security Updates – Certain aspects of the iService application were updated to eliminate vulnerabilities and improve security. Issue with images in Interaction Print form – We fixed some issues related to displaying images in the Print form that displays interactions in printer friendly format. Issue with zero byte message attachments – To reduce database size, some users with very large databases run a process to delete file attachment content after a certain amount of time has passed. In most cases these messages are already resolved, but if not an error was thrown when users tried to resolve them. Reports Customer Interactions by Interaction Properties report – Removed the page/tab separators generated for grouping properties. Pipkins Vantage Point 8.08.06 integration – iService can now generate a statistics file with email metrics for importing into Pipkins. Agent service level report – This new report calculates agent response times to help analyze how quickly each agent is responding to customer inquiries. |
New Features Most of the changes in release 7.7 are to the back end with minor changes to the user interface. Here a quick recap of what's in 7.7. Dynamic Form Display Not all customer questions are equal. Some are simple questions that need a simple answer, but others are the beginning of a complex workflow that can benefit from a special user interface. Release 7.7 includes changes that make it easy to present your agents customized views based on the type of question they're presented. Each section of iService that presents a view of interactions (history, search, my queue, etc.) can now automatically present a custom form based on attributes of the interaction. Part of these changes include a new interaction tagging process that puts a label on interactions used for triggering custom interfaces. The first built in example of dynamic form display is the new Quote and Follow up process described below. Quote and Follow Up Forms Sending and following up on quotes can be a high-volume and high-value process. The concept is simple - when a question arrives that's a quote request, the agent is presented a custom interface that streamlines the quoting process. When the quote is sent, the form generates a ticket for tracking and following up on the quote. We've included a configuration form that makes it easy to customize these two forms. This is just one example of presenting your agents the right interface at the right time. You can extend this example to any scenario where you need to present the agent a customized form when viewing an interaction. Read more about the quote and follow up process in our Quote Process Blog post. Integrating iService With Other Apps You can now integrate iService with over 1000 applications using our new Zapier triggers and actions. With our Zapier integration, you can connect your iService data to all the other tools your team uses like Salesforce, Marketo, Facebook, Google Sheets, Slack, and other apps without writing a single line of code. Zaps are set up in minutes, and you can use the to do things like add leads to Salesforce, create contacts in iService when a Salesforce contact is created, and add new iService contacts to Marketo campaigns. Customer Portal Did you know that you have a customer portal built into your iService tenant that allows customers to submit questions, view answers, and search your knowledgebase? Just append /f/customerportal-treeview to your iService URL to see yours. This is a built in example that can be customized or used out of the box. The portal is designed so it can be easily branded to fit your website. Check out the example on our website at https://1to1.iservicecrm.com/f/customerportal-treeview. Some changes to the portal in this release are: •Fixed an issue with the KB article count on topics •Fixed layout issues in the My Details tab (these pages are only available after you log into iService) •Simplified the view of history that customer see in the portal. There was no need for them to see various details originally designed for agents. •Added an article count to the list of KB articles Small Features and Bug Fixes •Updated to the latest version of Angular 1.5 to ensure we have all security patches. •The display of mailbox names was a bit too narrow in some views, so we expanded the Select input field so you can read more of the mailbox name. •The Customer Info page required the Message Queue access right. We changed it so it requires the Cust Info access right. •We found an issue with certain types of malware email crashing the email processor. We added fixes for the format in those emails, and changed the order of processing to process the newest messages first. If a message crashes the processor in the future this will ensure all new email is still processed. •We fixed a bug where replies to agent notifications were not accepted if the agent was the same person as the customer (responding to an agent notify when they submitted the original question as a customer). |
New Features •The old .Net customer info section has been replaced with new pages built using Angular JS and iService Forms variables and actions. We've introduced a new design theme that uses more icons, reduces the number of tabs, and is responsive. •We created new contact search form variables for the search page, and they can be used in other forms where you need to generate lists of contacts. •The search results can be customized to display any contact property. •The Contact Summary page is based on a new built-in form and can be customized for your needs. It now displays details about the last interaction with the customer and a summary of all unanswered questions. •The Manage Chats page has been replaced with two new tabs: Active Chats and Logged in Agents. They provide a real-time view of chat agent status and chat queues. Managers can now end an abusive chat from the Active Chats page. •The built-in customer chat form is now responsive for mobile users. •You can now search interactions using attachment names or the ID of a contact (in addition to a contact's login). •We simplified the stock response picker by removing the option to insert a variable. Just click the name of the response to add it to your message. •The layout of the My Queue page was updated with additional empty DIVs to make it easier to customize. •Select menus that often have long lists (forward to agent, forward to segment, pick FROM mailbox, etc.) were updated with a new search and auto complete function. •The Manage Message page and search results now include a button to show the full thread for any message. •Required interaction properties are only enforced when you resolve a message. Previously you were required to enter a value when changing the topic, forwarding to an agent, etc. •We now support OpenID, so your users can connect a Google or Microsoft account to their iService login. Both Google and Microsoft follow best practices for authenticating users and keeping their login safe, and using a single sign on approach improves security. •A new Response Time report replaces multiple reports and shows a break down of the life of a message (time to first assignment, time to final assignment, time from assignment to resolution, total time to resolve). You can either group by Agent or by Topic. •The Customer Interaction by Type report now includes the option to select specific contact types to return results for. •The indentation of quoted text got ridiculously large in the rich text editor when there were many back and forth messages. That's fixed now. •Some malformed messages failed processing and did not get into the iService database. We added a new process that retries them, and it appears to have fixed that issue. •Questions forwarded to another segment were using the original segment's mailbox on replies. This was changed to ensure the reply uses a mailbox from the new segment. •There was some funny behavior with IE that made it impossible to edit the subject or body in certain scenarios. That's fixed now. •We removed the logout function from the remaining .NET pages to fix a logout out issue with new forms. Most users will not miss the .NET logout button because it's in the Find Answers and Admin Tools pages. Users need to logout from Customer Info, Message Queue, or the home page. •Agents now load A-Z instead of Z-A in the Agent Admin page. •You used to get a crash when deleting an interaction property tied to a topic or service level. It's fixed now. •You used to get a crash when deleting a contact property used in a service level. Fixed it. •Deleting a skill used on a topic caused a crash. It works now. •Agent Interactions by Type report will now show results for former agents, even if they are not currently an agent in iService. •Time of Day by Date Range report sometimes returned incorrect results if selecting by hourly increments. •Topic Summary by Type report now sorts alphabetically.
|
Features
Bug Fixes
Reports Changes Not Affecting iService Core
|
New Features
Bug Fixes
|
|
|
|
|
|
|