What was said
What this says
As at Fri 9 Oct 2026Laura reviewed two tickets: a slow high priority search caused by a full-history connector setting, now a rolling window, and a how-to. Erin wants usage evidence for the supervisors, including who asks the questions.
What happened: The high priority ticket came from the connector pulling full history on its first run. Jared owned that, and the default is now a rolling window.
Customer view: Erin said the slow answer hurt because a supervisor needed it before a shipper call. She wants to answer properly whether the tool is being used.
Commercial: Usage proof is the base for the review and later renewal. Laura proposed measuring questions asked, not logins, and breaking them down by person to test key-person risk.
Watch: Erin suspects use is spread out, but the breakdown is not yet pulled. Jared only started in March, so history is short.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Jared to pull questions asked for the last month, compared with the month before, with a breakdown by person.
- Laura to send the final one-page guide on Friday.
- Run the second supervisor training session at twenty minutes with live searches only.
Risks
As at Fri 9 Oct 2026- Supervisors are questioning whether the tool is used, so value needs evidence at the review.
- Usage may be concentrated in one person, which would be a key-person risk.
Opportunities
As at Fri 9 Oct 2026- More how-to tickets as users join show adoption, and a first-view guide can absorb them.
- A second supervisor training session widens use beyond the core team.
Transcript
- Laura PenhaligonRight, let's go through the tickets first, because I've looked at them and I want to be straight with you about the high priority one.
- Erin GallantGo on. That was the one that hurt. A supervisor needed an answer before a shipper call and couldn't get it.
- Laura PenhaligonYes. It was flagged high priority, and we picked it up quickly. The answer came back slowly because the search was pulling the full history, not the last few weeks. We've changed the default.
- Jared PelletierThat was partly my fault. I'd set the connector to pull everything on the first run, and I didn't tell anyone.
- Laura PenhaligonIt's fine, we caught it. It's sorted now. The default is a rolling window, and you can widen it when you need to.
- Erin GallantAnd the other ticket? I can't remember what that was.
- Laura PenhaligonA how-to. Someone wanted to know how to save a search. It's a normal question and it's answered in the guide we sent.
- Erin GallantRight. Are we going to see more of those as more people join?
- Laura PenhaligonProbably, yes. That's a good sign, actually, because it means people are using it. Let's make the one-page guide the first thing they see.
- Jared PelletierI can add it to the internal page. Can you send me the final version?
- Laura PenhaligonYes. I'll send it on Friday.
- Erin GallantGood. Now, I want to check the numbers. The supervisors are asking whether it's being used, and I'd like to answer that properly at the review.
- Laura PenhaligonFair. The sensible thing is to look at questions asked, not logins. Jared, can you pull that for the last month?
- Jared PelletierI can. What should I compare it to?
- Laura PenhaligonThe month before, since you only started in March. It won't be a long history yet, but it's a fair start.
- Erin GallantOkay. And whose questions? I want to see if it's just me asking.
- Laura PenhaligonGood question. We can break it down by person. If it's mostly one person, that's a risk we should talk about openly.
- Erin GallantFair. I think it'll be spread out, but let's look.
- Jared PelletierI'll pull the breakdown and send it to both of you.
- Laura PenhaligonLet's do that. Next, the training for the supervisors. Erin, is the second session still happening?
- Erin GallantYes, it's in the diary. Could we keep it short? They're busy.
- Laura PenhaligonTwenty minutes, max, with live searches only.
- Erin GallantPerfect. Thanks, Laura.