What was said
What this says
As at Fri 9 Oct 2026Onboarding call on 23 Dec 2024 with Nathan Booth only; the business owner was out. The order system loaded cleanly, a couple of dozen part exceptions are held out, and older tickets join patchily.
What happened: Callie Brennan reported the order system load matched the export, with a couple of dozen old part references held out for Nathan to decide. The helpdesk connector is live and most tickets joined to an order.
Customer view: Nathan accepted that the brain keeps current values only and has no audit trail. He wants it stated in the setup note so nobody expects one.
Watch: Older tickets have empty or free-text order references, so answers on older material need care. Nathan said the other category is a big bucket.
Next: Invitations are held until the first data look is done. Nathan will check the refresh status page, watching for flat counts.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Callie Brennan to send the held-out parts sheet and write the setup note with the audit trail and older ticket caveat.
- Nathan Booth to decide as many held-out parts as he can and check the status page on a couple of mornings.
- Callie to send an invite for the first call after the holiday that suits Nathan and the business owner.
Risks
As at Fri 9 Oct 2026- The business owner was absent and relies on a written setup note to see the audit trail and ticket caveats.
- Older tickets join to orders patchily, so answers on older material may disappoint.
- Flat record counts over the holiday could go unnoticed if the morning checks are missed.
Opportunities
As at Fri 9 Oct 2026- The large other ticket category could justify a category of its own once the business owner sees it.
- A clean first look at the data before invitations should help adoption among the first users.
Transcript
- Callie BrennanAfternoon, Nathan. Can you hear me alright? I've got a bit of an echo on mine.
- Nathan BoothClear as anything. Afternoon. It's quiet here today, half the building's gone already.
- Callie BrennanSame here. Plan for the next hour or so, then we can both go and have Christmas. First, the order system load and the part mapping. Second, the helpdesk connector. Third, what happens over the break.
- Nathan BoothSounds good. Ruth's out already, she's back after the holiday, so it's just me.
- Callie BrennanThat's fine, I'll write it up for her. Right, the order system. The load ran out of hours as we planned, and it completed. I've got the counts for you.
- Nathan BoothGo on.
- Callie BrennanCustomers came in matching your export. Orders, the same. On the parts, using your revision rule, the base part grouping worked for almost all of them. A small handful of the old ones didn't follow the rule, which is the exceptions list you gave me, and I've held those out for you to look at.
- Nathan BoothOkay. How many are in that held-out set? Just roughly.
- Callie BrennanA couple of dozen. I've put them in a sheet with the order lines they came from. I'll share it. What I need from your side is a decision on each: is it a different part, or the same part written differently?
- Nathan BoothI can do some of them myself. A few I'd need to check with the planners.
- Callie BrennanThat's fine. Do what you can, and mark the rest as unknown. I'd rather an honest unknown than a wrong answer.
- Nathan BoothAgreed. Can I ask something? When a part is corrected in the order system afterwards, does the brain keep the old value or overwrite it?
- Callie BrennanIt takes the current value at each nightly refresh. So if a planner corrects a part reference on Tuesday, Wednesday morning it reflects that. The history of the change itself isn't kept unless the source system holds it.
- Nathan BoothThat's fine for us. I just wanted to be sure nobody expects an audit trail from it.
- Callie BrennanWorth saying out loud, and I'll put it in the setup note so Ruth sees it too.
- Callie BrennanNow the helpdesk. Your access note arrived, thank you. I started the connector yesterday afternoon, and the tickets are in. The order reference join, the one we talked about, I've run it.
- Nathan BoothAnd?
- Callie BrennanMost tickets joined to an order. Some didn't, because the reference field was empty, or had text that isn't an order number. Notes like see email, that kind of thing. I've listed those so you can see which ones they are.
- Nathan BoothI know the sort. It's mostly the older ones, before we made the field expected. Newer ones are better.
- Callie BrennanThat matches what I see. The recent tickets join well, and the older ones are patchy. So for questions about the last few months you'll get good answers, and for older material I'd treat it with care.
- Nathan BoothCan the free text be used to fill the gaps?
- Callie BrennanIt can be searched, and the brain can read it. I wouldn't want to promise it'll find an order number reliably from free text. It might. I'd call that a second pass, once the first is settled.
- Nathan BoothFair. Let's do it properly first.
- Callie BrennanAgreed. Now, categories. You have a category field on tickets. I'd like to check I understand them. Can you talk me through what the main ones mean?
- Nathan BoothSure. There's a dimensional one, for out of tolerance. A surface finish one. Paperwork, which is certificates and documentation. Late delivery gets raised by customer ops, not quality, but it ends up in the same system. And an other.
- Callie BrennanGood. I'll map those as they stand, so the names people use are the names they see. The other one I'd flag. If it's a big bucket, it's a sign something needs a category of its own.
- Nathan BoothIt is a big bucket, to be honest. Ruth knows. I think it'll come up once she sees it.
- Callie BrennanThat's a good outcome for the brain, if it helps her see it. Okay. Now users.
- Nathan BoothRuth gave me two names for the first people. I've got them added, as invited users, not yet logged in.
- Callie BrennanLovely. I'd hold the invitations until the first look at the data is done. If the first thing they see is half-mapped, they'll form a view and it's hard to change.
- Nathan BoothAgreed. I'll hold them until after the holiday. Ruth wants to look first anyway.
- Callie BrennanThat fits. So the plan over the break: the nightly refresh runs on the two sources as they are. Nothing new connected until we're back. Nathan, could you do a quick look on a couple of mornings to check it ran? I'll show you where.
- Nathan BoothYes, show me. I'd rather check than assume.
- Callie BrennanSo, share your screen and I'll walk you through the refresh status page. On the left you'll see the connectors, each with a last-run time and a records count.
- Nathan BoothI've got it. Order system, last run overnight. Helpdesk, same.
- Callie BrennanRight. What you're looking for is the time being this morning and the count not being lower than yesterday. If the count's the same for days on end, that's the sign the source has stopped feeding through, even if nothing's flagged red.
- Nathan BoothFlat counts, got it. And if it is?
- Callie BrennanEmail me. Don't wait. I'll be offline for a couple of days, but I'll look when I'm back, and you'll also have the support route.
- Nathan BoothI will.
- Callie BrennanActions. Nathan: decisions on the held-out parts, as many as you can, and a look at the status page on a couple of mornings. Me: the setup note, with the audit trail point and the older ticket caveat, and the held-out sheet to you before I sign off today.
- Nathan BoothSounds right. When's the next call?
- Callie BrennanThe week after the holiday. I'll send an invite for a day that suits you and Ruth. Have a good Christmas, Nathan.
- Nathan BoothAnd you. Cheers, Callie.