A unique application of deep learning in handling customer complaints and questions

Almost every site requests customers to submit their requests via a form. Most businesses can't afford a call center. Even the ones that do obscure their numbers because they want to minimize the number of calls and hence human operators. Which means that contact us forms are here to stay. However consider the default experience of contact us forms. The user sends a message "I want to know if you do a free pilot of your service?" Or maybe they write "how can I get access to my tax documents for 2015?".

The standard email response is that "we got your message and we are looking into this". But can we do better?

AI especially deep learning has been shown to have some success in automated email replies. Imagine applying the same principle to contact us or report an issue form. To train such a system you can simply feed in all the previous responses to all the previous questions asked. The deep learning system can then for new requests auto generate an email with the response as written by a computer.

So a sample response might contain a link to a relevant article, or might contain a follow up question.

It's important that in addition to automated response there should be a link saying I want the talk to a operator my issue is stilll not resolved. The benefit of this system is that it can significantly reduce the number of emails that need hand written response. All your previous responses will continue to grow big and the model should be updated on a regular basiss with new questions.

If you would like to test drive a solution like this please email at info@sublimeai.com

Comments

Post a Comment

Popular posts from this blog

Large SAP tables which are good candidates for partitioning

Image
Not all tables are good candidates for partitioning. The tool we have developed runs through multiple checks for large tables to identify the right candidate. Generally if the answer is yes to the following questions, table partitioning may be a suitable strategy for improving performance. 1. Is the database large enough? 2. Is the table large enough? 3. Do your reports and queries have distinguishable access patterns? 4. Are you experiencing slowness and performance degradation? 5. Is the skew factor for the data distribution under reasonable limits? Below are some of the large tables which have been candidates for table partitioning amongst our SAP customers. Large material master tables MARA                   Material Master Table MARC                   Plant Material Data MARO...
Read more

Partitioning in SAP HANA database

SAP HANA provides two ways of distributing data 1. Database Partitioning - different tables being distributed across several hosts (SAP Note 2044468 - FAQ:SAP HANA Partitioning) 2. Table Partitioning - splitting a column store table and distributing across several hosts (SAP Note 2081591 - FAQ: SAP HANA Table Distribution)  SAP HANA supports: 1. Hash Partitioning 2. Range Partitioning 3. Round-robin Partitioning In SAP HANA, we can create 1. Single-Level Partitioning 2. Multi-Level Partitioning The optimizing algorithm takes factors into account such as: - Balance tables equally in a way that they are spread over all the slave nodes and make optimal use of the available physical memory on each node - Ensure that tables/table partitions which are belonging to the same table groups (see tables _SYS_RT.TABLE_PLACEMENT, SYS.TABLE_GROUPS) are located on the same nodes, as they are logically frequently queried from application side via joins and if t...
Read more

SAP HANA exploits partitioning in SAP BW for optimization

Image
Partitioning significantly improves query performance, based on the types of queries and on your hardware configuration as the system will find faster the requested information, because it will filter out all the irrelevant partitions and thus reduce the data volume to be read. This is a standard feature in most databases but SAP did not truly exploit this feature being database agnostic until HANA. In SAP/R3, SAP provided partition keys for BW but did not partition data during installation. With HANA the table partitioning/distribution is automated for SAP NetWeaver Business Warehouse. Database tables created for InfoCubes or classic DataStore objects are partitioned on the database. While the technical partitioning of data at database level helps optimizing the runtime of BW processes to a great extent, they alone are inadequate in building and maintaining data warehouses that scale easily with growing data volumes. Hence, to address some of the aspects of dealing with ...
Read more