Step 1 Log a returned kit
When a home impression kit arrives back, enter it here. This is the manual trigger — it starts the build clock and lets you instantly tell the customer their impressions arrived and are going into production. Online purchases also land here automatically as “Awaiting kit” — just mark the kit received to start their build.
Queue Updates ready to send
Weekly check-ins surface here automatically as each order reaches its next milestone. Open the email (pre-written & personalized), send it, then mark it done.
Board Orders in production
Every active build, its business-day progress against the 35–40 day window, and what’s coming next. Orders that pass 25 business days are flagged so you can stay on top of them.
How the automated update system works ›
This console runs the customer-facing communication for every custom build on one consistent cadence, so no one is ever left wondering where their order is.
The cadence (business days after the kit is received)
| When | Trigger | What the customer hears |
|---|---|---|
| Day 0 | You log the returned kit | Impressions arrived — going into production |
| Day 5 | Week 1 | Build is underway at the bench |
| Day 10 | Week 2 | Shaping your custom shells |
| Day 15 | Week 3 | Hand-building & fitting |
| Day 20 | Week 4 | Curing & finishing |
| Day 25 | Week 5 — internal alert | Final stretch — tuning & inspection |
| Day 30 | Week 6 | Quality check & polish |
| Day 35 | Week 7 | Final inspection — almost ready |
| Ship | You mark it shipped | Shipped — tracking inside |
Business days skip weekends automatically, so a weekly email lands every 5 working days. At 25 business days an order turns into a red alert at the top of this page so you can intervene before it slips past the 35–40 day promise.
To make it fully unattended (optional)
- Pick a sending platform — e.g. Mailchimp / Klaviyo (marketing flows) or Postmark / SendGrid + a scheduler (Zapier, Make, or a cron job).
- Create one trigger event: "Kit received". Fire it when you log an order here (or push the exported JSON to the platform).
- Build the flow with the cadence above: send Day 0 immediately, then a step every 5 business days through Day 35, plus an internal alert to your team at Day 25 and a final "Shipped" email on fulfillment.
- Paste the email copy this console generates into each step — the wording, tone, and timing are already done.
Getting it into your CRM correctly
Every order is stored as one clean, validated record — names are tidied, emails are lower-cased and format-checked, duplicate active emails are flagged, and an order number is generated if you don’t supply one. Use CRM CSV (top right) to export a spreadsheet that imports straight into HubSpot, Salesforce, Airtable, or Google Sheets, with columns mapped 1:1:
- Contact: First Name, Last Name, Email
- Deal / order: Order Ref, Product, Status, Kit Received, Ship Window Start/End, Delivery Method, Tracking, Shipped Date
- Timeline: Business Days Held, Calendar Days Held, Last Update Sent
For live two-way sync, point your automation tool (Zapier / Make) at the same “Kit received” trigger and map those exact fields — the names already match standard CRM properties.