Steve: A couple of [0:00:06] of cross cutting and areas of the UI is that it has a full text search in there. If I do say the printer is broken, I get all the ability of the [0:00:25] for a full text search. I'll be able to do phrases and if I meant to hint that my printer's being broken, I guess it wasn't broken but it has something to do with the printer effects [0:00:38] tabs.
And I can search within the comment history and body there are all these types of objects in the systems. So as people add comments in history against objects in the system, it's all full text searchable.
So you can look for error codes. You can look for companies and also do "sounds like". So I can say, "Sounds like sunny," but it's actually called [0:01:06], which is good.
So if you can't remember contacts' names and so forth, then it's actually quite helpful.
Jimmy: It is. Because in the end, you end up with so much information that filtering it usually becomes a problem.
Steve: Exactly. It's kind of the same thing Google has to do. They have way too much information. You've got to be able to narrow the data down and have the tools to be able to narrow or hit it down as well as you can.
So, that's what we do. You give the tools and therefore it can also do things like how close words are to other words and that sort of filtering to try to get rid of the noise.