Next Steps

Current Status

AWS Hosted codebase that is accessing a static data file for detailed questions and answers.

Evaluating Capabilities

Responsibility: LocalClarity Business Team

Hitting the hosted UI with questions about the data set. (A number of notes provided in Upwork chat).

Field List

Responsibility: LocalClarity Business Team

An initial list of all the proper fields to use in the API pull needs to be provided to Nikesh.

"readMask": "storeCode,title,locationName,locationKey,locationId,regularHours,specialHours,primaryCategory.displayName,primaryCategory.categoryId,healthScoring,metadata,totalReviews,placeKey,locationState,profile,lastSyncTime,primaryPhone,isTokenExpired,totalMediaItemCount,latlng,totalReviews,voiceOfMerchantState,profileDescription,locationSpecialHours,storefrontAddress,websiteUrl,locationScoring"

Need:

additional categories - but the output needs to be changed

direct in-platform links - need output change

LC ID numner - needs output change

Template Creation

Responsibility: LocalClarity Business Team

Build a list of sample and expected data questions so that we can funnel end-users into conversations we expect to provide the expected results.

Conversation Memory

Responsibility: Vivek & Team

While it is not necessary to have a major update to the simple interface, it is expect that each query is part of a conversation thread. These full thread must be part of the email/notice deliverable to the LocalClarity business team.

Default Comment Sets

Responsibility: LocalClarity Team

Provide the basic sets of commentary required for effective client-base communication. For example, when the system is given instructions to do something.

Require a confirmation step such as “OK, you would like to {{add all of the locations in this list to a new group called ‘5th Percentile’. Please confirm.

Provide a timing notice "This request will be validated before execution. You should receive a notice within 24 business hours."

Full Cycle Test - Multiple Clients

Responsibility: Vivek & Team

Update the current simple UI to allow for a full cycle test. I’m thinking someone like, the user selects from a client drop-down and then clicks a button to retrieve the data via the LocalClarity API for that client (we would make certain you have access to the data for those clients). The UI responds when the data is available to query. The LC team can then “talk” to this data set to compare results to the platform data.

This test would emulate exactly what would be happening in the platform for private, alpha launch.

Clients you have access to via API (with the required ID)

BANDL - small, 9be8687429dc971a4b4ba222943391bc

Bar Burrito - medium, 189bbbe38640a186bbdad780833f240a

Boticario - large, dc1596de163fead4c162ed8949dba94f

Overall Architecture of Approach

Responsibility: LocalClarity DEV Team

Status: Team is currently tasked with the single most important launch of the year targeted for next Thursday (October 3rd) and cannot be interrupted until then .

Public Interface Design - Concepts

Responsibility: LocalClarity Business Team

Build out the html/css/javascript for the exact look, feel and design of the user interface that can then be build in react to support first the private access (just LocalClarity employees) and then the public beta..

Phase 1.5

Code Creation Details

Responsibility: LocalClarity Business Team

Provide the json file requirements for creating the code necessary to edit the content for the most common set of expected instructions.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.