Get your lab running in Pilot.
7 short chapters take you from planning the move to processing cases, billing, customer support, work tracking, analytics and customizing Pilot. Start with chapter 0: it covers how onboarding works and what to bring.
Preparing to onboard
How a move to Pilot works, what data to bring and why, how your team learns Pilot, and how to keep the change on track.
5 sections
Start processing cases
Load your products and customers, set up shipping, bring your team in and, if you want it, your case history.
4 sections
Start billing out of Pilot
Carry your customer balances over, choose when invoices lock, send statements and take payments.
5 sections
Set up Customer Support
Answer doctors’ emails and portal messages from one Inbox, from your own address, with templates and response targets.
4 sections
Set up Work Tracking
Describe how work moves through your lab once. Pilot then schedules every case and gives each technician a queue.
6 sections
Analytics
See what Pilot records, ask questions of it with insights and dashboards, and group customers into cohorts.
4 sections
Customizing Pilot
Custom fields hold what your lab needs to know. Workflows do the work your team would otherwise repeat.
2 sections
Every CSV template Pilot imports, grouped by what it lets you do, with the section that walks you through it. The same templates are in each section and in the appendix.
Required to start using Pilot
The baseline for processing cases. Every case is for a customer, and uses products priced on that customer’s price list.
Products
Your whole catalog in one file: one row per product with its settings, one column per price list with the product’s price on it, and one column per product custom field.
Customers
One row per doctor at an office: the office and its shipping address, the billing account, the price list, and one column per customer custom field.
Custom prices
Prices a customer pays that are different from their price list.
Historical case data
OptionalLets Pilot spot remakes and pick up treatments that run in stages, and search and reports work from day one.
Cases
One row per case: customer, status and dates, and one column per case custom field.
Case line items
The products on each case, with quantity, rate, teeth and shade, and one column per line item custom field.
Production tasks
The production steps on each case, with workstation, technician and dates, and one column per production task custom field.
Customer balances and billing
OptionalCarries every customer balance over, so Pilot’s first statement opens where your old system’s last one closed.
Financial transactions
Every invoice, payment and credit up to your cutover date, one per row.
Expected statements
Optional. Each account’s opening and closing balance for each month, from the statements your customers got.