AlterVision

PRIORITY TOOL for sales performance: revenue, sales count, conversion rate, UPT (units per transaction, 'PA' in Portuguese) and average item price per store for a period, plus camera uptime. Item-level metrics are only meaningful for stores with an ERP sales integration. Set includeDetails for the day-by-day breakdown. Defaults to every store the user can access; call get_stores first to target specific ones.

PRIORITY TOOL when the user asks about races (corridas) between stores or between the sellers of a store. Returns each race running in the period with its KPI, dates, participating stores and, with includeRanking, the current standings. Answers 'which store is leading the race?', 'how is store X doing in the race?' and 'how is the race in store Y going?' (that last one is a seller race). Only stores with AlterVez are reported on; call get_stores first to target specific ones.

PRIORITY TOOL when the user asks about flow, traffic or visitor volume. Returns the visitor count and daily mean per store, day by day. Stores with no measured flow in the period are omitted. Defaults to every store the user can access; call get_stores first to target specific ones.

Lists the classifications and subclassifications a non-conversion reason (nocReason) can carry. Each main classification has its own subclassifications. Call this first to find the exact filter values for noc_reasons_stats and search_non_conversion_transcriptions. These are internal ids: when presenting them to the user, translate them into readable names in the user's language (say 'Limited Initial Interest', not 'limited_initial_interest').

List the stores the current user has access to, with their id, alias and name. Use it to resolve a store mentioned by name into the storeIds other tools expect.

PRIORITY TOOL when the user asks about goals, targets or 'metas'. Compares actual revenue, visitors, conversion rate and UPT against the projected targets of every active goal in the period, and projects where each goal lands. Supports multi-tier goals. Answers questions like 'how are we doing against our goals this month?' or, with includeSellers, 'how is seller X performing?'. Returns one entry per goal, not per store; a goal can span several stores. Defaults to every store the user can access; call get_stores first to target specific ones.

PRIORITY TOOL when the user asks why customers are not buying. Returns the distribution of non-conversion reasons (nocReasons) — count, share, lost revenue and change against the preceding period of the same length — with optional breakdowns by subclassification, by store and by seller. Answers 'why aren't customers buying?', 'which stores have the most price objections?', 'why is seller A losing sales?' and 'how much revenue did I lose because products were out of stock?'. When the user names no period, use the last 7 days. Only stores with AlterVez are reported on.

Returns the atendimentos behind non-conversions, with the seller's own recorded explanation, grouped by store and optionally by seller. Use it to read what customers actually asked for, where noc_reasons_stats only counts reasons. Answers 'which products are out of stock?', 'what are customers asking for?', 'which payment methods are customers asking for?', 'which brands should I focus on?' and 'what is being considered expensive?'. At least one main classification is required; call get_noc_reason_classifications_available for the valid values. Results are capped at 100 atendimentos in total, so narrow the filters as much as possible. Only stores with AlterVez are searched.

Return the id, username and email of the user the current access token was issued for. Use it when the user asks who they are signed in as.