building a voice assistant for enterprise
play

Building a Voice Assistant for Enterprise Manju Vijayakumar Lead - PowerPoint PPT Presentation

Building a Voice Assistant for Enterprise Manju Vijayakumar Lead Software Engineer, Salesforce @vmanju QConSF, Nov 2018 Agenda Why Voice? Demo of Einstein Voice Assistant Conversational AI Ecosystem Natural Language


  1. Building a Voice Assistant for Enterprise Manju Vijayakumar Lead Software Engineer, Salesforce @vmanju QConSF, Nov 2018

  2. Agenda ● Why Voice? ● Demo of Einstein Voice Assistant ● Conversational AI ○ Ecosystem ○ Natural Language Understanding (NLU) ● Challenges ● Future ○ Considerations ○ What’s next for NLP and AI

  3. Voice Recognition - A Story in 3 pictures Source on Twitter

  4. Computing is Evolving From programmatic to natural interactions Voice Touch Point & Click Command Line

  5. Deliver an intelligent assistant that leverages Voice and NLU capabilities to understand, and support users in accomplishing their goals

  6. Pilot EINSTEIN VOICE DEMO

  7. Meet Amy, a busy salesperson Amy needs to update Salesforce

  8. How did Voice Assistant help Amy? Unstructured data -> Structured data Productive ● No system expertise ● Accuracy & timeliness of data capture Visible to the team

  9. Building Blocks of Voice Assistant

  10. ASR Automatic Speech Recognition

  11. NLU Natural Language Understanding ASR Automatic Speech Recognition

  12. CRM Integration NLU Natural Language Understanding ASR Automatic Speech Recognition

  13. Conversational AI Ecosystem

  14. Conversational AI Ecosystem Automatic Speech Natural Language Salesforce Einstein Platform Recognition Understanding CRM Metadata Models Models

  15. Conversational AI Ecosystem Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification Automatic Speech Natural Language Salesforce Einstein Platform Recognition Understanding CRM Metadata Models Models

  16. Conversational AI Ecosystem Einstein Voice Einstein Voice Bots Voice Navigation* Smart Speakers* Assistant Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification Automatic Speech Natural Language Salesforce Einstein Platform Recognition Understanding CRM Metadata Models Models

  17. Conversational AI Service Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  18. Conversational AI Service Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  19. Named Entity Recognition (NER) The ‘O’ committee ‘O’ The committee of 30 government and of ‘O’ university scientists and engineers, led by McCleese, was asked to recommend to ... ‘O’ the space agency by the end of this McCleese ‘PER’ month a rationale and strategy for precursor flights and the sample-return the ‘DATE’ missions. end ‘DATE’ of ‘DATE’ this ‘DATE’ month ‘DATE’ *CoNLL format

  20. Named Entity Recognition (NER) The ‘O’ committee ‘O’ The committee of 30 government and of ‘O’ university scientists and engineers, led by McCleese, was asked to recommend to ... ‘O’ the space agency by the end of this McCleese ‘PER’ month a rationale and strategy for precursor flights and the sample-return the ‘DATE’ missions. end ‘DATE’ NER7 model recognizes 7 entities: of ‘DATE’ Person , Organization , Location , this ‘DATE’ Date , Time , Money , Percentage month ‘DATE’ *CoNLL format

  21. What are the entities in the text ? PERSON ORGANIZATION DATE MONEY Follow up call with Chris in two weeks DATE ( two weeks is normalized to 2018/07/15)

  22. Conversational AI Service Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  23. Entity Resolution - Is this entity in my CRM ? Salesforce Records matched CRM DB for ‘Acme’ Send records to user to disambiguate

  24. Conversational AI Service Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  25. Context Management - What data do we have so far ? { "context": { "Organization": { "id": "001XXXX", "name": "Acme Corp" }, }, ... } Do we have organization in the context?

  26. Conversational AI Service Entity Context Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  27. Text Classification - What are the intents ? Acme Corp’s timeline for purchasing Marketing software is set for Prediction request July 1st and may purchase up to $250K of product JSON Language API Intent model Follow up call with Chris in two weeks { "probabilities": [ { "label": "CREATE", "probability": 0.9904295 }, { "label": "UPDATE", "probability": 0.009345241 }, ... ] }

  28. Conversational AI Service Entity State Text Named Entity Conversational API Slot Filling Recognition Resolution Management Classification

  29. Slot Filling - What are the slots for each action item ? Fill in the date and money slots for Update action Fill in the date slot and person slot for Create Task action. Here, date is normalized : In 2 weeks => 10/7/18

  30. Challenges

  31. Data challenges How do you make it work for every AccountID Name Phone customer schema ? AccountID Name Phone Bank Account - Customers can define custom schemas Heterogenous - Schemas are not consistent database

  32. Data challenges Which Acme Corp. did you mean ? - Lots of duplicates - Identify the most relevant ‘Acme’ - Affects user experience Inconsistent data

  33. Automatic Speech Recognition is not perfect DOMAIN SPECIFIC AUDIO ACCENTS & JARGON ENVIRONMENT LINGUISTIC PROFILES

  34. Named Entity Recognition is not perfect Named Entity Recognition is easy for humans but hard for machines

  35. Named Entity Recognition is not perfect Today, JP Morgan and I spoke Is JP Morgan a company or a about... person ? ..the san juan center is led by a Cannot identify san juan as a location due to case sensitivity team of scientists.. ..Man joy and I met today at “Manju” misspelled as “Man Joy”. Starbucks to discuss.. Misspelled pronouns are hard to catch

  36. Future Considerations

  37. Voice Optimized Models Feedback - Capture Feedback - Guided user experience - Configurable - Retrain Models - Multi channel - Normalized

  38. What’s next for NLP and AI? ? Architecture engineering Deep learning Machine learning for single tasks with feature engineering

  39. What’s next for NLP and AI? To learn more: decaNLP.com Single multitask Architecture model engineering Deep learning Machine learning for single tasks with feature engineering

  40. Voice Recognition - A Story in 3 pictures Source on Twitter

  41. Voice Recognition - The Complete story Source on Twitter

  42. Key Takeaways Language understanding is AI Complete. Focus on solving customer pain points in your domain. Voice will become the new User Interface.

  43. Resources Einstein.ai - published papers, research etc. Einstein.ai/careers - We are hiring! @vmanju

Recommend


More recommend