The answer was in the manual. It was just faster to call.

A gym in regional NSW had done the work most businesses never do. Their procedures were written down. Membership types, cancellation policy, how to process a freeze, what to do when equipment went down, how to manage class and room bookings. Years of operational knowledge, typed up and saved.

Staff still called management for half of it.

Not because the answers weren't there. Because finding them — quickly, under pressure, with a member standing at the front desk waiting — was slower than picking up the phone.

The document problem

The gym's documentation had grown organically over the years. New procedures got added when something came up. Notes got appended to sections that already existed. By the time it covered everything it needed to, it was long — the kind of long that's fine to read on a quiet Tuesday afternoon, and completely unusable at 6:30am when the first wave of members is coming through the door.

Staff knew the answers existed somewhere. But knowing something is in a lengthy document and knowing where to find it under pressure are entirely different problems. With a member waiting at the counter, the mental maths wasn't complicated: search through the manual, or send a quick message to the manager.

The manager usually responded quickly. The shortcut kept working, so staff kept using it.

What this created

Two patterns emerged, and neither was good.

The first: management's phone rang constantly. Not for genuine emergencies — for things that were, as management would be the first to admit, clearly in the documentation. What a particular membership tier included. Whether a member could bring a guest. How to handle a direct debit that had bounced. Answerable questions, documented answers, still ending up as a phone call.

The second pattern was quieter but in some ways worse: deferring upward. When a question came up that couldn't be quickly resolved, and calling management felt like too much, the easiest path was to leave it. Tell the member you'd get someone to follow up, leave a note in the handover book for the manager to sort out. The problem got kicked upstairs rather than solved at the desk.

In a regional gym where most members are locals — where the person at the front desk probably knows the member by name, sees them three times a week — that kind of "I'm not sure, come back later" moment lands differently than it might in a big-city chain. It chips away at something.

The actual fix

What changed wasn't the documentation. The gym already had solid documentation. What changed was how staff could access it.

They uploaded their existing procedures to AskLore — the same content, unchanged — and shared the bot link with staff. Setup took an afternoon.

Now, when a member asks about freezing their membership or what's included in an upgrade, the staff member types the question in plain language. AskLore pulls the answer from the procedures and returns it in plain language. No scrolling, no hunting through pages, no calling management. Seconds, not minutes.

The manager's phone got quieter almost immediately. Not because staff suddenly knew more, but because the gap between knowing the answer exists and being able to find it right now had closed.

What management noticed

A few weeks in, the volume of incoming calls had dropped significantly. But something else stood out: new staff were handling things independently faster than they used to. The ramp-up period — that window where casual or newer staff need an experienced person nearby to fill in the gaps — had shortened noticeably.

"They're just getting on with it," was how management put it.

The handover notes shrank too. If the answer is a ten-second search away, there's no reason to leave it for the manager to deal with later.

The documentation that had been quietly sitting there, doing less than it should have been, was finally doing its job.