Know

Before we can get to the philosophy of Know itself, lets understand Solve in context with Know. As a product consumr.ai does 2 key things for its users, besides all the ancillary capabilities that it has. It is a Consumer Intelligence Platform and hence with its insights it helps answer and resolve the doubts and questions that a user has about his brand's consumer landscape.

We built the Omnibox for a particular kind of audience that knows the use cases that can achieved using consumr.ai and how? Over a period of time we realized that it is just 1 out of 20 people who would be able to get there in the first 3 months of usage.

Solve was built for the remaining 19 users who may not know how to find their way around Omnibox. With Solve, you can just enter the questions, you are seeking answers to and it will give you a chain of reports to work with.

The problem statement we now face at the other end of this process. We have done everything that is needed to get a user to simply enter a question and get the combinations of inputs. But what about:

1. Searching a report once he has executed it. Who remembers the name and number of the report? The chances of a user remembering the inputs is 10x higher than then remembering the report id or name (unless he has renamed the report to something he remembers).

2. Once a user locates the report, whats next? How do we train them in drawing the right inferences from these reports? How do we get our reports to answer their questions, correctly?

These are the 2 problem statements that we will tackle through these big releases:

Input search will handle the first problem statement, while Ask me a question will handle the second one through our Know section