You've successfully subscribed to edrone Blog
Great! Next, complete checkout for full access to edrone Blog
Welcome back! You've successfully signed in.
Success! Your account is fully activated, you now have access to all content.
Success! Your billing info is updated.
Billing info update failed.

AVA in a Nutshell: Part III — R&D Scope

The virtual shopping assistant provided by AVA will conduct natural, unscripted conversations — using natural language, with all colloquialism and meaning understandable only by humans — with eCommerce customers.

Marcin Lewek
Marcin Lewek

AVA is dedicated to eCommerce and all the conversations its customer care department is engaged in — i.e. products (characteristics, prices, specifications, etc.). Simple questions, like "product availability", or terms, such as "returns", are also important; however, handling such queries is relatively easy and is not a challenge in itself. The assistant must handle the product knowledge as a human being would do to ensure a shopping experience similar to that we can find at physical stores.

To organize all of this knowledge is one thing. Therefore, people ask mostly about things that are not listed in the product description; to extract it from the descriptions, as well as from past and future conversations, are part of the deal.

R&D Challenges, Scope, Milestones

Besides talking about description or conversation with customers, AVA is meant to be a commercial product. What is even more important: it will be a product sold in the B2B model to online shops of any size.

AVA In a Nutshell
While trying to overleap competition, there is usually no point in desperate trials of doing something the same way but faster, better because it’s at least problematic, especially when you are developing your product in many directions.

Running an eCommerce business requires a lot of different specializations and practical experience. It is crucial to provide solutions that are easy to introduce and maintain. Therefore, we need to automate the process of "building" the assistant as much as possible, keeping in mind the quality of the end-product — operational Voice Assistant, specialized, and dedicated to a particular shop. So, AVA will be machine developing machines.

We will start by developing an algorithm responsible for creating a language model adapted to eCommerce, working on text corpus consisting of descriptions of products taken from various eCommerce businesses in various industries. It is the base for the next step: NLP algorithms, from which two are particularly interesting — they will be the core of the AVA platform.

gMAP & MAP

The most crucial aspect of the project is to adapt the platform to various shops and data structures we can find among them. For example, some eCommerce businesses work on highly structuralized data (consisting of a hierarchy of product categories); others don't. Also, we need the characteristics of the product to be structuralized as well. We called this piece "MAP": Map of Attributes describing Products.

MAP is the center of our assistant. It is a multidimensional vector space, organizing assistant's knowledge about products. Every product is automatically placed in this space, creating a unique model for each shop separately.

AVA in a Nutshell: Part II – Voice as a tool
In the previous part, we’ve briefly described the idea behind edrone AVA: a virtual assistant speaking the same way as a biological one. To speak - so simple, right? Looking at Siri clumsiness, we might get quite another impression.

The creation of such complex objects as MAP is time-consuming and requires technical knowledge. Simultaneously, as we mentioned above, eCommerce employees need easy-to-use, fast, and reliable solutions. For that, we are going to provide the "gMAP": generator of MAPs.

It provides the maximum possible simplification of the work necessary to create the MAP by applying machine learning algorithms and graphical interface for manual MAP modifications (active learning).

Fuel for AVA

gMAP uses data from three different sources:

  • edrone plugin tracks customers' behavior and passes it to the edrone platform.
  • eCommerce platform API is useful for fetching product data, but not all platforms provide its API.
  • Product Feed is widely used in eCommerce as a universal product list, used for multiple purposes, especially marketing, advertising, and stock monitoring.

The Product Feed is the most comprehensive source of product knowledge. It contains the product name, description, photos, category name, producer, price, availability, shipment, and other valuable information. AVA will extract from conversations all pieces of information not included in the product descriptions — available via the edrone plugin (API).

AVA Architecture

Following Challenges

On AVA's roadmap, there are milestones not included in the description above, also worthy of mention:

  • Search-recommender — consists of algorithms responsible for matching products to customers' requirements and asking additional questions if needed for effective product recommendation (also supported by collaborative filtering and affinity analysis).
  • Algorithm prototype for handling universal, eCommerce-specific product attributes — in various eCommerce industries, the products have some universal characteristics with which they are described; i.e. "size" in the fashion industry is an excellent example of such characteristic.
  • NLU module — capable of extracting the eCommerce clients' key requirements.

Are you interested in joining us in this challenge?

NCRD has already granted us USD 2.5M. Join our team of experts - we are currently looking  for:

Feel free to contact us via any preferred channel or apply via the landing page:

AVADeep learningMachine learningArtificial intelligenceNLP

Marcin Lewek

Digital marketer and copywrier specialized in Artificial Intelligence, design, and digital marketing itself. Science, and holistic approach enthusiast, after-hours musician, and sometimes actor.