WizPilot Overview

WizPilot is an AI assistant embedded in WizCommerce that answers questions and takes actions using the platform's existing data, so sales reps, admins, and sales leaders spend less time switching between systems.

---

Table of Contents

 

---

A. The Problem

Sales reps, inside sales reps, and admins at wholesale businesses lose 8-10 hours a week to low-value, repetitive work spread across systems that don't talk to each other — ERPs, WizOrder, email, catalogs, CRM, Ella.

None of it is selling. All of it is necessary. A rep looking up stock opens one system; checking a customer's payment history opens another; logging a visit means a third, usually at 7pm, usually badly.

The industries where this hurts most are the ones we serve: home décor, furniture, lighting, and adjacent wholesale categories.

Three people feel it differently:

---

B. What WizPilot Is 

WizPilot is a conversational assistant embedded in WizCommerce that answers questions and takes actions using the data already in the platform.

It is not a chatbot bolted onto a help centre, and it is not a general-purpose LLM with your data pasted into a prompt. WizPilot reads the same records your reps read, respects the same permissions, and works inside the same screens.

Four things WizPilot does:

1. Questions and answers. From your database, from uploaded documents, and from email or voice transcripts. "How's Sagebrook doing?" and "what's our return policy for damaged goods?" are both WizPilot questions, answered from different sources.
2. Actions. WizPilot creates, edits, and converts real records — orders, quotes, carts, catalogs, tasks, leads, visit logs. Everything lands in draft state and waits for a human.
3. Reports and AI reports. Tables, charts, and persistent dashboards built by asking, not by configuring. Saved queries re-run on every view, so a dashboard stays live.
4. Prompt and rule setup. A layered configuration model — WizCommerce base rules, then org-level definitions, then individual user preferences — so WizPilot reflects how a specific business actually works.

---

C. The Four Design Principles 

Everything in WizPilot is built against these. They are worth knowing because they explain why WizPilot behaves the way it does.

» Surface

The right data, in the right format, at the right time. WizPilot answers with typed widgets — a metric card, a data table, a chart, a product card — not with a paragraph describing numbers. Answer first, no preamble.

» Act

WizPilot executes, but only with consent, and it operates in three explicit tiers:

• Suggest: Surfaces the answer, gives you a deep link, writes nothing
• Draft: Fills the form, shows it to you, waits
• Execute: Proceeds only after explicit confirmation of that specific action

There is no autonomous mode that removes the check. That's deliberate.

» Traceability

Every substantive answer carries a chain-of-thought card — collapsed by default, one click to open — showing what WizPilot looked up and how it reached the answer. Behind the scenes, every query is logged end to end and scored on relevance, completeness, latency, and preference adherence.

» Reusability

Answers don't evaporate when the chat closes. Any report or dashboard can be saved, re-run, and shared. WizPilot's output is meant to become part of how the team works, not a one-off.

---

D. How Reps Reach WizPilot 

"Ask WizPilot" in the top nav. From the Dashboard, it opens a full-screen chat. From any other module — Sales, Products, Customers — it opens as a right-side quarter-screen panel that already knows what page you are on.

"WizPilot" in the side menu, with sub-items: New Chat · History · Artifacts & Dashboards · Knowledge Base · User Preferences

Action chips. Every time WizPilot opens, it offers three contextual, dynamically generated prompts drawn from the current page, session memory, or proactive insights. Three sets appear per session, then they stop once the user has sent three messages. Reps can't turn them off — they are load-bearing for adoption, not decoration.

---

E. What Ships in P1 

» Selling: product discovery

Product search across ID, name, attributes, order history, and customer preference · similar and alternative product recommendations · live inventory and stock lookup including allocated, backordered, and in-transit quantities

» Selling: Customer Intelligence

Customer and lead 360° summaries with rep-configurable emphasis · meeting preparation with history, open items, talking points, and web search · in-person visit logging with automatic follow-up task creation · CRM entity creation, editing, and deletion with confirmation

» Selling: Entity Lifecycle

Create, view, update, delete orders, quotes, wishlists, catalogs, carts — all in draft · repeat previous orders · cart building with price list switching and price overrides · order, invoice, and shipment status · payment transaction lookup · customer-specific catalog generation

» Selling: Outreach

Personalised email drafting, either generic for bulk or tailored per recipient · abandoned-cart recovery emails · persona and tone configuration with Custom Instructions override · voice-to-text input

» Operating: Intelligence

Business performance monitoring across sales, customers, team, and products · persistent dashboards with saved, auto-refreshing queries, shareable to selected reps or the whole org · knowledge base document upload with source citation

» Platform: Memory and Context

Short and long-term memory across sessions · user preferences and Custom Instructions · screen-aware contextual intelligence that reads the page you opened from · mobile and tablet access for chat and history

» Widget Library

Product Card (with custom attributes) · Chain-of-Thought Card · Status Badge · Navigation / Consent Widget · Customer360 Widget · Data Table with cross-entity columns, filters, and sort · Filter Chip Bar · Metric Card · Line, Bar, and Pie Charts

Any widget showing data supports click-through — SKU, rep name, product name, order or customer ID all deep-link to the relevant page.

» Platform and Observability

"Ask WizPilot" CTA and side menu in WizOrder · trace logging from query to outcome · Slack alerting on threshold breaches · a LangSmith-backed monitoring dashboard · AP Portal configuration so admins control which data sources and capabilities WizPilot can reach

---

F. What's Not in P1 

Stated plainly, because the gaps matter as much as the scope. Everything below is phased into P1.5 or P2 rather than unplanned — see the next section for which.

Admin and operations. Import and export assistance · integration sync queries and resolution · approval queues · claims management · refunds, credits and payment modifications · credit memo retrieval (invoices work, credit memos do not) · price list assignment · discount and promo code creation · customer and product segments · tag management · label and barcode generation · user and access management · customer re-assignment · de-duplication and merge · org settings, email template, and WizShop SEO configuration.

Selling. Image-based SKU search · discount and pricing eligibility recommendations · daily briefing · calendar invite creation · document upload and parsing via Ella · post-trade-show analysis.

Communication. Sending email directly from WizPilot — WizPilot drafts, the rep sends · email campaign and notification setup · email and calendar integration setup · WizPilot speaking back, since P1 is voice-to-text only.

Platform. Product creation via WizPilot · workflow setup · alert and monitoring configuration · inventory and warehouse tracking · files Q&A and asset retrieval · ERP and connector setup including WizStudio · WizPay reconciliation.

Mobile. File upload · User Preferences · Knowledge Base · Artifacts & Dashboards.

---

G. The Layered Configuration Model 

This is the part most worth understanding, because it's what makes WizPilot fit a specific business rather than a generic one.

Base Rules — set by WizCommerce, identical across every tenant. Defines the fundamentals: what "delayed" means, how order statuses move between states, which widget answers which kind of question. Not editable by anyone at the customer.

Org-level definitions — set by the customer's admin. Encodes how this business actually runs. Overrides Base Rules where they conflict.

Custom Instructions — set by the individual rep, under User Preferences. Their own layer on top of everything above.

The practical effect: an ops lead can encode company rules once, and every rep still gets to shape WizPilot around how they personally work — without either one breaking the other.

One important boundary: preferences change what WizPilot renders first, not what WizPilot fetches. If a rep asks for payment status at the top of every customer summary, WizPilot reorders the view. It still pulls the full picture. Nothing gets quietly hidden because of a setting someone forgot they made.

---