ArkCase Complaint Management Solution Demo

Your Title Goes Here

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.

See Video Transcription

So what i’d like to do is to go ahead and set the stage. Before we actually get into the actual demo of the application, let’s talk about the story we’re going to show today. It makes a bit more sense to show really the day in the life of processing a case in the ArkCase application especially for those that will be utilizing this application. You want to kind of see how the story plays out so we’re going to actually show case management, but it’s going to be handling an actual customer complaint.

ArkCase utilizes an actual user interface that allows you to submit complaints from many different types of sources so whether you’re receiving complaints from a portal, email or simply a phone call. A case can be generated automatically or manually based on your business requirements.

Here is the high level workflow that we’re going to show today. Toby is going to be the person that is going to report a customer service issue with the organization. Once the complaint or case is created we’re going to have Owen from our services organization examine triage the initial case.

Once Owen trias the information he’s going to assign the case to an analyst Anne Smith, that will do further triage and collaboration and ultimately offer a resolution to the customer.

We’ll spend it quite a bit of time going through some of the day-to-day things that can be done on say documents, workflows or tasks or even finding it for information by searching or looking at reports.

With that said let’s jump into the demo of the system.

All right so let’s go ahead and navigate over to the customer portal.
So this is the our case customer portal users can do a lot of things directly on the portal, but the first thing is that there is a registration process in the event that the organization wants users to register and create an account.

If they hit the registration button down below this will walk them through a step-by-step process to create an account. Once the customer has an account directly on the portal they can log in and then they’re given access to many different types of things they can generate a new complaint or case with the organization. If they have existing complaints or you know cases with the organization they can see a status update in terms of where that complaint is within the workflow.

But let’s go ahead and generate a new complaint. So when the user clicks on the new complaint there is a custom web form that pop that appears. This is a completely customizable web portal so that the organization can modify the content they can add different metadata pieces to really capture all the information in relation to the complaint.

So let’s go through the processing of this form. So the very first thing that the user would do is select the complaint category since it’s a required field they can select essentially maybe a method of communication in terms of delivery right and so multiple ways in terms of how a customer can communicate with different individuals within the organization.

Section two on the form is the profile information about the customer so this is the information that the customer used to register to create an account. If any of this information is outdated the customer can go back into their profile an they can update their contact information their phone number their email address if it’s outdated.

Section three on the form is the information about the complaint so maybe this is a customer complaint that for benefits right and so my benefits were denied right and so the description box allows the customer to put in as much information into the complaint. So that it allows the organizations to be able to quickly triage and understand what the complaint is about.
We also support the capability of adding supporting information so any customer can add different pieces of information it could be say for example maybe the benefits package, maybe the information that they got from the vendor right and so. All of this information can be attached they can validate and view that information as needed.

Once the form is essentially filled out the next is what we call preview complaint information dialog box. This allows the customers just to validate all the information they entered on the form. The phone number, the information about their description, the title right. But essentially once the form is is verified they can then go ahead and submit this complaint or case over to the organization. A few things are happening at this point, one is that a complaint or case is getting generated within the ArkCase application and second is a correspondence template is being delivered back to the customer, just to validate that they’ve created a case giving them the case number when the complaint was created just for their records.

All right so now we’re going to transition over to the internal application and this is where the internal users of the system are going to manage all the complaints and cases that are received by the organization.

Users interface with our case simply through any of the major browsers out in the market and so they just essentially navigate to the ArkCase platform there’s multiple ways that we support and allow users to authenticate into the application they can type in their username, password we support single sign-on capabilities if the organization wants to enable or configure that within the system.

Once the user logs into the system, before we get into the use case in processing this complainer case I just want to kind of start off by giving you a holistic view of the system. On the left hand side we have all the different modules within the system including the dashboard which is essentially the landing page of the application. We actually use widgets within our dashboard that allows users to actually view different pieces of information directly from their dashboard they can see cases that they have access to see or that they’re assigned to, if they have tasks associated to different complaints in terms of collaboration they’ll be able to see many different tasks.

We also have reporting widgets that allow users to actually view different types of reports, how many cases are open and closed, what type of cases they are right. All of these different widgets are configurable within our application so you can actually enable many different types of widgets directly in the platform.

At the top we have our global new which allows us to create a manual case, a task or person and then associate those different objects to a particular case or a complaint. We also have our simple search which ultimate leads leads to our advanced search module that will allow users to search the entire application whether it’s metadata information related to a case or complaint or a particular document within the system. We ocr index all of that content and make that searchable directly within our platform.

Okay so I’m logged in as Owen jones let’s get into the use case. So when I go ahead and click on the particular case directly on the dashboard you’ll notice that it actually navigates me out to the initial complaint or the case directly from the complaint that I’m viewing you’ll notice that I have access to see a lot of different pieces of information, I can see the details, I can see the initiator meaning who created, who is the customer that created the complaint.

If there were documents that were attached to this or emails that were sent out by the system I have information about all of those uh pieces of content that’s in there I also have case summary notes where I can see exactly where this is in the current stage of the process right and so I can add many different notes and tasks directly into the complainer case.

So, Owen’s going to go ahead and he’s going to go ahead and validate all their information so when you know owen actually expands a particular complaint you’ll notice there’s a tree level of metadata information that’s attached to every complaint and case within our application. You can see the details, I can jump into say for example Toby Anderson’s information and in the event that I need to speak with Toby again another tree level of information but I can see phone numbers, I can see email addresses, a lot of information can be viewed.

So let’s go ahead and do the initial triage for this new case or complaint. So the very first thing that Owen may do is he may actually come in and look at some of the documents that were sent by Toby as part of the creation of the case.

He can come down and see any of the supporting documents, he can open up and view that information maybe there are certain pieces of information that will help toby make a decision, so he can actually open up a particular document in in the ArkCase viewer and the ArkCase viewer will allow them to view the contents of that information. We also keep the file association to every single document that’s imported, so if the user prefers to open a particular document in the native adobe application, they can also launch a particular document in adobe to view that content directly uh within a pdf viewer.

So a lot of things can be reviewed based on Owen’s responsibilities and tasks. He may go out and need to get additional content and so we do have the capability directly out of the box to send emails directly from a case and so I can go in and I can set up a particular email reference to Toby, add him as a recipient say: Hi Toby can you please send us the benefits information that is missing all right thank you.

And so once this email is essentially sent out uh Toby will get an email directly from the customer service analyst Owen saying that you know they’re looking for additional content right. All the emails that are delivered directly from the ArkCase system is archived in the outgoing folder so users can actually see a history of all the different emails that have been sent directly from the application and you have complete flexibility in controlling you know what you view from a title perspective directly from the ArkCase viewer.

Once Toby gets that information, Toby can actually reply directly to that email and once that attachment comes in, the benefits package can be updated into the supporting documentation. So now you know Owen has a lot of information he’s ready to actually move this through the process. Owen can actually assign this case to many different individuals to make a decision on the case.

So you know we’re going to go ahead and assign this case to Ann Smith and we’re going to actually have Ann go out and say for example. We’re going to go ahead and assign this uh case to Ann Smith to really you know review the information to do more analysis and maybe make a decision in terms of what needs to occur with this essential case that was created.

All right, so now since we assigned it to and we’re going to go ahead and log out of the system as Owen and I’m going to actually log into the system as essentially Ann Smith who is essentially the analyst or essentially a supervisor that can make a decision on on this particular case.

Once I log in with Ann Smith you’ll notice that there’s a big difference in terms of the interface, in terms of what owen and anne have the capability. The reason why I wanted to show owen is i wanted to show the roles based access controls within our application that we have the capability of controlling many different capabilities based on a particular user or group of users within the system.

You’ll notice that when I logged in with Ann Smith all the modules in terms of what she has the capability of doing is a lot different, as well as all the information within the system in terms of data and will have a different set of information whether it’s cases, complaints, it could be tasks that are associated and so a lot of this information can be controlled through our roles based access controls.

Once Ann actually opens up the individual case, she can go in and see the customer complaint, she can see all the notes that you know was done by Owen and so she can add an additional note reviewing you know additional content for resolution right and so she can put in many different types of different notes.

The notification the notes notification also serves as essentially notifications as well so if she wanted to send essentially Owen a note and saying got it reviewing now, the system will automatically send Owen all of that case information as as well as an email including the information that she put in as a note. And can go in she can review all the supporting documentation, she can select many different evidence, she can open up the documents and open this up in a document viewer so that she can review the content and so I showed you the ArkCase viewer but the ArkCase viewer has a lot of different capabilities from a functional standpoint, users can navigate through the many different pages of the document itself.

You’ll notice on the right hand side is that we keep many different versions of the document so in the event that Ann needs to modify this document as part of her triage, anytime she makes change it will create a new version always keeping the original version intact. We also have a lot of editing capabilities directly within our viewer, so essentially ann can come in and she can put in an annotation on a particular document saying hey i’ve reviewed it right, she can change the font colors and and different features of the annotation.

We also support many different types of redaction so maybe she needs to redact a particular area or search for different keywords based on expressions within the within the document and so, the application will highlight that information and she can determine if she wants to redact all matches or essentially maybe she wants to only redact one other two right so really depending on the features and functionalities of what she’s doing them application can support all different uh capabilities.

Once a document has been completely reviewed and can then go ahead and save and she can burn in the annotations and what the viewer will do is that it will take all the annotations and create a new version of embedding the annotations as well as any of the redactions directly into the file.

So once the reversion of the new version is created, the application will automatically open up that version allowing ann to see all the different edits that she made inside of the document.

And here you can see all the different versions that were created directly within the system. There’s a lot of things that can be done from a document perspective and might need to go back to the benefits organization and collaborate with many different individuals. She may actually want to create a new task in relation to this document and assign it to essentially the you know benefits review team right and so um she can assign the task to a particular individual or she can assign a task to a group of different users uh within that department and so if she assigns you know the the task to John saying: can you please review and give feedback all right. She can put a start date a due date behind you know a particular task uh within the system, she can run essentially many different types of business processes based on the requirement of this workflow, so if she wants to run it through a document review process and have multiple people validate well you can build many different processes within the application and then you can select which documents or cases or complaints follow a particular workflow.

Once the task is essentially created, this will assign a task to John, John will you know go in he’ll review that information and he’ll he will basically reply back to Ann that all the information is complete.

Okay so let’s go ahead and move this case through the rest of the workflow. The next step in the process is for Ann to actually go back to Toby and communicate any type of final decision or responses from the organization in relation to the case or complaint. This can happen in multiple ways one method is what we call correspondence templates. ArkCase includes an out of the box correspondence management system that allows the organizations to create predefined templates based on most common responses. If you right click on a particular folder you’ll notice that if you browse up to new correspondences, you’ll see different types of correspondence templates that Ann has the capability of using within the process. She can click on say for example customer complaint response.

Once the response is actually created within the case and can then go ahead and she can open this template up in microsoft word giving her the capability of seeing the communication she can say for example make any edits so if she wanted to add and say you know we will refund price. She can make any edits to the correspondence template.

We also have the capability of auto populating the correspondence template with any metadata information related that’s part of the case. So we can gather the date, we can gather their contact information, we have over 10 000 different metadata terms that can be added as part of the correspondence template. Once ann is happy with the correspondence template, she can then go ahead and save this template and it will essentially update the template directly within the ArkCase platform.

The other method that Ann can essentially communicate with essentially the customer is through the embedded sent to email functionality. We have the capability as i showed before is that users have the capability of sending emails to multiple different individuals. But we also have templates that can be generated based on certain responses so if there’s commonly used emails the organization can create predefined essentially templates that users have the capability of using as they kind of begin or work through the workflow.

Once they add the template they can then go ahead and enter the recipient’s email address down below and once the recipients are added the application will send an email directly to those individuals providing all the information as part of the case.

Once the customer receives the email or the correspondence template, you can actually then make a decision and determination on the next steps of the case, so if the customer comes back they accept all the terms of the resolution we can then go ahead and close the case out or escalate this case to a supervisor for further review.

Let’s go ahead and close the case out, at the top you’ll notice that there’s a change case status user can actually click on the change case status here and they can see a drop down so they can then you know set the status to close maybe it was a full resolution to the original complaint and Ann can actually type in her information, so that she’s actually approving this case to be closed.

She can put any details into the description for case closure and this will mark essentially this case officially closed at this point. We also have the capability within the application to run a particular case closure through a workflow, so say for example supervisor needs to kind of approve the case to be closed. Well essentially you know we can create a task and assign it to a supervisor and they can come in and they can review all of the information as part of the case they can go through the parent documents they can you know go through the details of the case all the information that’s really added you know into the case details.

Once the supervisor approves the case to be closed this will officially close out the case again this is an optional step most organizations don’t need if you don’t have an approval process you don’t need to run through this step but essentially this is a different option in terms of the workflow capabilities directly within ArkCase platform.

All right so now you know we showed how a customer complaint was sent in through a customer portal we went through initial triage with Owen and we assigned the case to Ann smith and actually approved a resolution she communicated back to the customer, the customer accepted the resolution details and we’ve actually closed the case out.

There’s a lot of other features directly within the our case platform from a reporting perspective as well. We have over 30 different types of different reports directly out of the box we can do case summaries, complaint disposition counts, but essentially you know you can use any of the different case reports within the system to really show and reflect how the organization is processing on a particular case. This is just a very quick case summary within the application that will show you essentially all the different cases and their current statuses but essentially you know there are a lot of different methods in terms of being able to run different types of reports.

We also have an Adhoc report module that will allow the organization to create customized reports if you’re very experienced with power bi or other reporting applications, pentaho is an application that will allow you to create many different types of reports, you can create bar charts, you can create leading product lines you can do heat maps tons of different metadata information can be combined from different data sources to actually generate a very sophisticated report directly within the application.

And then finally the admin settings is really the brains of the application this allows you to control all the roles based access controls, configure how users are sync from active directory you can actually determine which reports are configured or have roles based access controls in in terms of who has access to run certain types of reports.

We also have the capability directly within the system is to change all the labels out of the box, so essentially if there’s a particular label within the system for example if we wanted to take complaint and convert that to essentially cases we can do that, so I can actually navigate over and i can say well these are all the cases directly in the system. Once I actually make that change the label within the complaint module will change the cases and so you have complete control over all the labels within the system.

We also give you access to add different types of metadata fields and drop-downs directly within the application. We also give you access to modify all the dropdowns directly in the application so if there’s different complaint types or persons types or statuses you can modify that directly within the system as well.

All right, so if there’s any questions in terms of the presentation today please feel free to reach out to a sales member at

Thank you and have a great day.