Staff sign in

Real server-side PIN check — this actually locks the board.
0
Total jobs
0
Alerting now
0
Rush jobs
0
Emergency
0
Parts pending
0
Completed
0
In QA
0
Tools checked out
100%
📞 Incoming call

📥 Inbox

Alerts about your cars, tasks from calls, and anything assigned to you.

☎️ Call Log

Every call, including the ones with no car on the board.

Call

Ring them back on
Want someone told about this call?

🔔 Callbacks Due

Everyone owed a call back, soonest first.

📞 Phone System

RingCentral — caller ID on the board, click to call, and a log of every call.
Where do I get all this? — step by step

1. Make an app. Sign in at developers.ringcentral.com with the same login you use for your normal RingCentral account. Go to Console → Apps → Create App → REST API App.

2. Answer the setup questions like this. Auth type: JWT auth flow. Where will it be used: only my own account (a private app). Permissions: tick Read Call Log, Call Control, and Read Accounts. Call Control is the one that makes caller ID pop up on the board — without it nothing appears.

3. Client ID and Client Secret. Once the app exists, open it and look under Credentials. Both are on that page. Copy them into the boxes below.

4. The JWT. This one is not on the app page. Click your profile picture (top right) → Credentials → Create JWT. Pick production, and tick the app you just made. RingCentral shows the token once — copy the whole thing right then. It's very long and looks like three blocks of gibberish separated by full stops. If you lose it, just make another.

5. Account ID — you almost certainly don't need this. Leave it blank. It defaults to ~, which means "whichever account these credentials belong to", and that is what you want. Only fill it in if RingCentral support tells you to.

6. Shop phone number. The main number customers ring, in full international form: +15055551234. This is the number that shows on a customer's phone when you use "call them back".

7. Save, then press Test. Test tells you exactly what's wrong if something is off.

8. Last step, for the caller-ID pop. Copy the webhook address from the bottom of this screen into a RingCentral subscription for telephony sessions. Until that's done the call log and click-to-call work, but nothing pops up when the phone rings.

Not saved yet.
Not saved yet. You create this under your profile → Credentials → Create JWT.
Blank means "this account", which is right for nearly everyone.
Off by default. Each call costs one AI request, billed to you by Anthropic. You can always run it by hand on a single call.
Tasks the AI works out from a call get added on their own, with nobody checking first. Everything it does is written to the activity log, and any task it creates can be deleted like any other.
Off unless you turn it on, and worth thinking about. The transcript comes from a phone call in a noisy shop, where "Tuesday the twenty-second" comes back as "Tuesday the twelfth" often enough to matter. A wrong task is visible on a list. A wrong callback date fails silently — weeks later, when a customer says nobody rang them. Nothing is ever booked from a time the AI did not actually hear.
Turns the call recording into text, which the AI then writes notes from. RingSense needs no key. The others charge per minute of audio and need one below.
None of the non-RingSense engines has run against a real service — there is no internet where this was built, so they are written from each provider's documentation and tested against a mock. Watch the first real call: a 403 fetching the audio means the RingCentral app is missing the ReadCallRecording scope, which is a different fix from a bad key.
Calls from these never get attached to a customer's car, and stay out of the customer call log. The board tries to learn them from incoming calls, but it only sees the number a call arrives on — your main line is the number staff call from, so it was never learned. That is why the shop's own transfers kept landing on one Ford Fiesta.
Saving only affects new calls. Re-check goes back over every call already logged and removes the wrong car matches.
The address you open the board on. RingCentral needs it to know where to send calls — without it nothing can be connected. Must start with https://.
Are calls actually connected?
Not checked yet.
Credentials being correct is not the same as calls arriving. This is the part that tells RingCentral to send them, and it lapses on its own after a week if it isn't renewed — the board renews it for you, but this is how you check.
Webhook address
Save your settings to generate this.
Set automatically when you press Connect. It carries a secret key — treat it like a password.

⚡ Tekmetric flagged this car

The label says urgent, but not how urgent. That part is your call.
How urgent is it really?

Sound & voice

Personal to this device — everyone can pick their own tone and volume.
No custom sound uploaded yet.
MP3, WAV, or similar. Kept under 2MB, stored on this device only. Uploading sets "Custom" as your active tone automatically.
Only alert once the timer hits zero
Every 4 seconds
Voice call-outs
This is personal to you — everyone signed in picks their own.
Turn off RO timer alerts if you just want parts/tow/priority call-outs, or the other way around — the audible tone still rings either way.
Announce at 10 minutes remaining

New job

🚗 Vehicle & customer
Phone and VIN are what a customer types on your website to look up their own car. Fill these in and the lookup works without any integration.
🏷️ Priority & stage
🚛 Tow-in
🎨 Appearance
🔧 Work & parts
📝 Notes

Tekmetric integration

Built from Tekmetric's published API behavior — I don't have access to your actual Tekmetric account to test against, so use Test connection first and check the raw sample RO it shows you before trusting the sync. Credentials are stored on this server only, never sent back to the browser.
Uses {shopId} and {roId}, filled in per car. Leave blank to use Tekmetric's standard URL. If the button ever lands on the wrong page, paste the correct URL for one RO here (keeping those two placeholders) and every card follows.
Label → stage mapping
Tekmetric's per-RO "label" (not the fixed Estimate/WIP/Completed status) maps to your board's stages. Run a sync once to discover the labels currently in use, then map each one below.
seconds
Tip: 60s keeps the board fresh without risking Tekmetric's rate limit on a busy day. Faster than ~20s can get your requests temporarily blocked.
Tick the statuses that mean "this car is in the shop". Anything else stays off the board even if its label is mapped — that's how Estimates end up padding the count. Leave everything unticked to accept any status that isn't finished.
On by default. When a repair order reaches Complete or Posted, its card is archived off the board so the board matches what's actually in the shop. Cars added by hand are never removed by a sync, and anything archived stays searchable and restorable in Full History. If a sync can't see every repair order (a very large history), it won't remove anything that run rather than risk clearing a live car.

📅 Google Calendar

Pushes promised pickup times and parts ETAs to a shared shop calendar automatically — no manual entry, updates when the job does. Uses a service account instead of "Sign in with Google" — this server doesn't have a fixed public address until you deploy it, and Google's normal sign-in flow needs one registered ahead of time. A service account sidesteps that entirely.
One-time setup (5 minutes, in Google Cloud Console)
  1. Go to console.cloud.google.com, create a project (or use an existing one).
  2. Enable the Google Calendar API for that project (APIs & Services → Library).
  3. Create a Service Account (APIs & Services → Credentials → Create Credentials → Service Account). Any role is fine — it only ever touches the one calendar you explicitly share with it.
  4. Open the service account → Keys → Add Key → Create new key → JSON. This downloads a file — open it, you'll need client_email and private_key from it below.
  5. In Google Calendar, create or pick the calendar you want the shop to use → Settings → Share with specific people → add the service account's email (the client_email from the JSON) with "Make changes to events" permission.
  6. Still in that calendar's settings, scroll to Integrate calendar and copy the Calendar ID (looks like an email address, or ends in @group.calendar.google.com).
What to sync

✉️ Email Alerts

Sends alerts through SendGrid (a transactional email service) when a stage's automation includes a "Send email" step — set that up per-stage in Manage Stages → ⚙️. This is just the account credentials; which stages actually trigger an email is configured there.
One-time setup (SendGrid account)
  1. Sign up at sendgrid.com (free tier covers low volume).
  2. Verify a sender identity (Settings → Sender Authentication) — this is the "from" address below; SendGrid rejects sends from unverified addresses.
  3. Create an API key (Settings → API Keys → Create API Key), "Full Access" or at minimum "Mail Send" permission, and paste it below.
Comma-separated for multiple recipients.
📊 End-of-day summary email
Emails a recap of the day — cars completed, turnaround time, and the biggest bottleneck — to the same recipients above. Sent through the SendGrid setup above (no separate account needed).

🔒 Clerk Login

Every person signs in with their own real Clerk account instead of tapping a name and typing a PIN — built for a team where everyone has their own workstation, not a shared tablet.
One-time setup (Clerk account)
  1. Sign up at clerk.com and create an application (free tier is fine for this).
  2. In your Clerk Dashboard's API keys page, copy the Publishable key and Secret key and paste them below.
  3. On the server, run npm install once (this pulls in Clerk's SDK — the one real dependency this app has needed) and restart the server.
  4. Click Test connection below. Only once that succeeds should you turn login on — it's blocked from turning on otherwise, on purpose.
After this many seconds with no taps/clicks/keystrokes, the screen signs that person out. Enter 0 to turn it off completely — best for an always-on wall display that should never sign itself out. Otherwise, anywhere from 10 seconds up to 4 hours (14400s). Default is 4 hours.
Requires a successful "Test connection" above first. Turning this on for the first time will walk whoever's at the screen through creating the first account, which becomes the initial Super Admin. Manage the rest of the team afterward from ☰ Menu → Manage Team. This is a clean switch, not a hybrid — once it's on, the old name+PIN roster stops granting access immediately, even to a session that's already open.

☁️ Supabase Backups

Pushes a full snapshot of the board to Supabase (a hosted database) on a schedule, purely as an off-site backup. The board itself keeps working exactly as it always has, reading and writing its local data file — this doesn't change that, and doesn't depend on the internet for anything day-to-day. It's just insurance: if this server's disk is ever lost or corrupted, the data still exists somewhere else. Backups only upload when something has actually changed — if the board is quiet, it quietly skips the upload instead of piling up identical copies, so a short interval is safe.
One-time setup (Supabase account + table)
  1. Sign up at supabase.com and create a project (free tier is plenty for this).
  2. In the SQL Editor, run: 
    create table shopboard_backups (
  id bigint generated always as identity primary key,
  created_at timestamptz not null default now(),
  data jsonb not null
);
alter table shopboard_backups enable row level security;
grant select, insert, delete on shopboard_backups to service_role;
    The last line matters even if your project is older than mid-2026 — newer projects don't auto-expose tables to the API anymore, so this makes sure it works either way.
  3. In Project Settings → API, copy the Project URL and the service_role / secret key (not the anon/publishable one — this needs to bypass Row Level Security, and never leaves this server).
  4. Paste both below, click Test connection, and only then turn scheduled backups on.
Off by default until a test succeeds — same reasoning as the Clerk gate. A bad key should never silently mean "no backups are happening" without you knowing.
Backup history

📺 TV Display

Two separate, purpose-built displays — no one needs to be signed in for either; open the right link on the TV's browser once and leave it running.
The page customers use — share this link, put it on your website, or turn it into a QR code for the lobby. It shows first names and last-4 RO only. To look up their own car, a customer enters their phone number and VIN.
Slow-paced rotating showcase for a waiting-room TV.
Dense, persistent ops dashboard — everything visible at once, no waiting for a rotation. Open Manager Board escalations, parts status, and tow-ins waiting on intake, on top of the full job board.
Anyone with the bay/front-office link sees full customer detail with no login — treat it like a password, and only put it somewhere customers don't see. If a TV is ever lost, stolen, or the link leaks, regenerate it below; the old link stops working immediately.

🔧 PartsTech

This saves your PartsTech username and API key, but doesn't pull order data yet. PartsTech's endpoint-level API docs sit behind a partner agreement, and every integration guide I could find (Tekmetric's, and several other shop systems') describes a hosted checkout session model — your team shops inside a PartsTech-owned window, then PartsTech pushes the completed cart back — rather than a simple endpoint this board could just poll for order status. Building that handoff correctly needs the real integration guide, which isn't public. Ask your PartsTech rep for it, or reach out to PartsTech-Partner-API@oeconnection.com — once that's in hand, this is ready to wire up for real.

Layout Builder

Every stage can be placed and sized independently — drag a stage's header anywhere on the board to move it, drag its right edge to resize width, its bottom edge to resize height, or the corner to resize both. A stage can span multiple rows or sit alongside stages that don't line up with it at all.

The fields below do the same thing with exact numbers instead of dragging — Col/Row is the top-left corner, W/H is the size, all in grid units (1 unit = 30px). Handy for lining two stages up exactly.

Stage order (drag ⋮⋮) is always shared — everyone sees the same order. Position, size, collapse, and hide are set by a Super Admin and shared with everyone.
Want a new box on the board? This screen arranges the boxes you have — it doesn't create them. A box is a stage cars move through, so add one in Manage Stages and it'll appear here to position.

🔧 Parts Dashboard

Everything the parts team needs to chase, in one list — vendor, ETA, and status.

🚛 Tow-In Dashboard

Everything on a hook, expected or already here — company, ETA, condition, and status.

🚛 New Tow Request

Log who's bringing it in and when — link it to an existing RO if one's already open, or start a new job card.

📢 Announcement

Spoken aloud on every connected screen right now — not just yours. Use it for things everyone needs to hear immediately (a customer waiting up front, closing early, an all-hands heads up), not routine chatter.

💬 Team Chat

Group — everyone signed in sees this. Use 📢 Announce instead for something everyone needs to hear right now.

💬 Parts Chat

📝 Request a Part

Pick the job this part is for, then describe what's needed — this shows up in that job's Parts Chat thread too.

🧰 Tool Inventory

Specialty tools — where they are, what they cost, and which RO has them out.
+ Add a tool

📊 Import tools from CSV/Excel

Upload a .csv, .xlsx, or .xls file with one tool per row. CSV works with no internet needed; .xlsx/.xls need to load a library from a CDN first. The first row should be column headers — this will try to guess which column is which, but you can correct it below before importing anything.

This just notifies whoever runs the tool crib — no photo needed from you. They'll pull it, confirm its condition, and let you know it's ready at the parts window.

Print this and stick it on the tool — scanning it opens this tool straight to check-out/check-in.

🏷️ Print Tool Labels

Pick a layout and select which tools to include — everything selected prints together as one job, arranged to fit as many as possible per sheet.
Tools
Select all Select none

Each step fires once a card's been sitting in this stage for that long — on top of earlier steps, not replacing them. A car can end up recolored and rocking and flashing at once if it's been in here long enough. Timing is measured from the moment the card enters this stage, and resets if it moves out and back in.

Manage stages

Rename, recolor, reorder, or delete your board's stages. Set what customers see for each. Changes are shared by everyone immediately.

Manage vendors

Keep names consistent so parts tracking and stats actually add up — "NAPA" and "Napa Auto Parts" won't group together. Shared with everyone immediately.

Manage staff

Change this before going live — the starter logins (Jamie/Robert/Alicia, PINs 1111/2222/3333) are printed in the README that ships with this app, so they're not a secret. Reset each PIN to something private, or delete the demo names entirely once your real staff are set up. Changing a PIN or removing someone signs out any device currently using that login.
Add staff member

Manage team

Everyone here signs in with their own email and password through Clerk — there's no PIN to reset, since Clerk handles that (including if someone forgets theirs). Removing someone here only removes their access to this shop board; their underlying Clerk account isn't deleted.
Add team member

⚙️ Permissions —

Current role: . Each row defaults to that role's setting — switch one to override it just for this person.

⚙️ Role defaults

What each role can do and see by default. Individual people can still be overridden from their row in Manage Staff.

📜 Audit Log

Every stage move, staff/tool/vendor change, and Tekmetric sync action, newest first.

📋 Tech Comments

Notes pulled in from Tekmetric on each RO, all in one place — newest first.

Stat

🎯 Manager Board

Customer escalations and tasks for management, in one place. Set priority, assign, discuss, and attach files.
+ New item

🔧 Report a Maintenance Issue

Shop equipment, not customer vehicles — lifts, compressors, HVAC, the building itself. Maintenance gets notified right away.
How urgent is it?
My Reports

🛠️ Maintenance

Everything the team has reported — mark progress, assign, log receipts.

➕ New Work Order

Scheduled or preventive work — created directly, not waiting on a report.

Receipts
Comments

📊 Maintenance Stats

⚙️ Equipment

✅ Maintenance Today

Today's checks

My work

Overdue a service

⚙️ Maintenance Manage

Equipment, service schedules, daily checks and history.

💬 Ask the Shop AI

Ask about the board in plain English, or let it look for problems. Answers come from the live board only.

🏁 Shop Overview

Everything at a glance — who's on shift, what's due, where cars are, and a scannable list of it all.

Today's summary

Stage times & bottlenecks

Signed in now

Due today

Bay occupancy

All active jobs

✨ AI Summaries

Turns a car's notes, parts and history into plain English.
From console.anthropic.com. Billed per summary by Anthropic, not by this app. Stored on your own server and never sent to the browser.
Off by default. Every car that moves stage costs one API call, so on a busy board this adds up — turn it on knowingly.

🏅 Performance Scorecard

Measured against published industry benchmarks. Everyone can see their own.

🏠 Shop Details

Used on tow requests so the driver knows where to deliver the car.
Not needed. "Check on Google Maps" already works without a key — it opens the address in Maps so you can eyeball it. A key only adds type-ahead address suggestions, and Google bills you for those.

🔍 Display & Text Size

Fits more cars on screen without shrinking the buttons. Saved for this computer only.
0 counts every car in a review stage, which is how it behaved before. 120 means a car is only flagged once it has sat there two hours.
Use this instead of zooming the browser out — buttons and photos stay big enough to hit.
Separate from the board on purpose. If you shrink the board — or zoom the browser out — to see every stage at once, that shrinks the writing in pop-ups too. Turn this up and job details, ROs, parts and tool lists stay readable while the board stays small. The A− / A+ buttons in the corner change whichever of the two you're looking at.
Tidies notes when you click out of a box: capitals, double spaces, and common typos. Never touches names, VINs, plates or RO numbers.

🔧 Tech Resources

Look-up links shown on every car. Use {vin}, {ro}, {year}, {make}, {model} or {plate} and they'll be filled in per car.

🚦 Go-Live Check

Checks the board's actual state for anything that isn't safe to run live yet.
Only removes the sample cars this app shipped with. Cars you added yourself are never touched, and removed ones stay recoverable in Full History.
🔍
Searches the whole shop — current jobs, completed jobs, tools, parts, maintenance, and the Manager Board. Type at least 2 characters.

🩺 Diagnostics

Health checks, recent errors, and a one-click report to send to Claude when something breaks.
How this helps after launch: if something goes wrong, open this panel, click 📋 Copy report for Claude, and paste it into a chat with Claude. It contains what's needed to diagnose the problem — version, settings status, health checks, and recent errors — with no PINs, credentials, or customer data.
🩺 Health checks
⚠️ Recent errors
📋 Send to Claude

📄 RO Summary

Built from everything recorded on this car.

🎉 What's New

Recent improvements to your shop board.

💡 Suggest a Feature

Tell us what would make this work better for your shop. We read every one.
Your shop's previous suggestions

🕓 Full History

Everything that has ever happened — search by customer, vehicle, RO number, part, or staff name. Includes cars deleted from the board.

📒 Usage History & Reports

Tools, parts, tow-ins, and maintenance — with per-item counts over the period you choose.
📊 Usage counts
🕑 History

📊 Statistics

Active jobs and WIP are always "right now." Everything below the date controls reflects the period(s) selected.
Period

⚠️ Confirm delete

🔒 Super Admin required

🚨 Emergency

This immediately alerts every connected screen — the staff app, both TV displays, everywhere — with a full-screen alarm and instructions read aloud. No approval needed; if something's actually wrong, don't wait.
🔥 Fire
🔒 Lockdown — secure in place
Tells everyone to stay put and secure in place — the opposite of evacuating.

🔥 Fire / Evacuation Settings

What every screen shows and reads aloud during an alert — your actual exit routes, meeting point, and anything else the team needs to know. Be specific to this building; nobody can guess your floor plan for you.

This is a communication tool, not a substitute for real fire alarms, extinguishers, or a posted evacuation plan. Keep those in place regardless of this feature.