The date nobody remembered agreeing to

An operations lead in a Singapore office wearing earbuds, on a video call on her MacBook, a paper notebook open beside it

Priya runs operations at a small logistics company in Singapore. Most of her job happens on Zoom. On a normal Tuesday she has six calls: the warehouse team at nine, two vendors before lunch, a delivery partner in Johor, the weekly review with her boss, and whoever books the last slot of the day.

I'm David, and I work on VoxStudio. Priya isn't a real person, but her week is close to what people with back-to-back calls have told me. The calls themselves are fine. The trouble starts a week later, when someone asks what was decided in one of them.

Thursday, 4:40 p.m.

Her boss messaged her on a Thursday afternoon. "The scanner vendor says we agreed to go live on the 18th. Did we? Who agreed?"

Priya remembered the conversation. She did not remember which call it was in. The vendor had been on three calls in two weeks, and the date had come up in at least two of them. Her notes from those calls said things like "vendor - date?? check w/ Ken" and "QA first". She had typed them while also trying to talk, which is how her notes from every call look.

She spent the next forty minutes going through her notes, her calendar and a chat thread with Ken from the warehouse team. She found the 18th mentioned twice. She couldn't tell if it had been a proposal or a promise. In the end she wrote back, "I think it was conditional, let me confirm with Ken," which is the kind of reply nobody likes sending to their boss.

That evening she decided that next time she wanted the actual words, not her version of them.

A woman at a shared office table between meetings, looking through handwritten notes in a notebook with her laptop pushed to one side

Recording the call without adding anyone to it

The obvious fix was a meeting bot. Priya didn't love that. Some of her vendors are touchy about a stranger called "Notetaker" appearing in the participant list, and two of her calls are with people who would ask what it is before saying anything useful.

She installed VoxStudio for Mac on her MacBook Air instead. It records the meeting app on the Mac itself, so nothing joins the call. On Monday morning, with Zoom open, she went to Meeting Recorder. Zoom showed up under Record the meeting locally. The Zoom recording guide suggests one test before the first real call, so she made a short recording with app audio and her microphone both on, played it back, and checked that she could hear both sides. App audio picks up the other people on the call. The microphone picks up her.

She also started every call the same way: "I'm recording this so I don't have to take notes, is that okay?" Nobody minded. A couple of people said it was a good idea. Not adding a bot doesn't remove the need to ask.

Listening instead of typing

For the vendor call at eleven, she chose Record with live assistant instead of Record only. A window opened next to Zoom with the conversation appearing as text a moment after people said it, labelled Me and Others.

The difference was mostly in what she stopped doing. When the vendor said they could do the go-live "around the 18th, if your QA signs off by the 11th," she didn't try to write it all down. She typed "golive 18 if QA 11" and pressed Return. With Live Enhance on, the note grew into a proper sentence taken from what had just been said, with a timestamp pointing back to that moment in the recording. The live transcription guide shows how this looks.

Ten minutes in, she lost track of which of two warehouses the vendor meant. She asked the chat in the same window, read the answer, and checked the line it pointed to before saying anything. It was the Tuas one.

The live view only says Me and Others. Separate speaker labels come later, in the full transcript.

After the call

When the call ended, she clicked the VoxStudio timer in the menu bar and chose Stop Recording. She trimmed the two minutes of small talk at the start, sent it on to Transcribe, and named the session "Scanner vendor - go-live - 3 Nov" so she would know it later.

Transcription runs on the Mac once the speech models are downloaded, which she had done the day before. The transcript came back with speakers separated. Ken is on almost every one of her calls, so she asked him first and then saved a clear half-minute of his voice to the voice library. Now when she transcribes a new call and ticks Ken under Recognize people, his lines come back with his name on them. Voices she hasn't saved stay as Speaker 2 or Speaker 3, which is how the voice library guide says it should work. She fixes vendor names by hand.

By the end of the week she had fourteen sessions. Each one took a minute of her time after the call.

A woman at her desk in the early evening with earbuds in, listening back to a recording on her MacBook, city windows behind her

The next time someone asked

Two weeks later it happened again. Different vendor, same kind of question. Finance wanted to know whether the delivery partner had agreed to absorb the fuel surcharge in November or only "look into it."

This time Priya opened Knowledge, chose All knowledge, and asked something close to the prompt in the meeting search guide: "What did the delivery partner say about the fuel surcharge for November across these meetings? List the original passages, session names and timestamps. Say if the recordings don't settle it."

The answer pointed to two sessions. In the first, the partner's account manager said they would "look into absorbing it." In the second, a week later, he said, "we'll cover it for November, December we'll talk."

She didn't forward the answer. She opened each citation, read the lines around it, and played the audio from the timestamp. The answer is only a pointer, and a transcript can get a number wrong or miss that someone said "maybe" quietly before the sentence. Here the second quote was clear, and it was the account manager speaking, not someone on her side.

Her reply to finance had the session name, the time in the call, and the exact sentence. It took six minutes.

What runs where

Priya's company asked, so she checked. Recording, transcription, and indexing and search in VoxStudio for Mac run on her Mac. AI answers, the live notes and the chat use the service she picks, VoxStudio Cloud or her own API provider, and that service gets the text it needs for the request. The knowledge base page spells out where those lines are. There's also a separate Meet Bot in the VoxStudio web app for calls she can't attend, but that one does join the call as a visible notetaker and keeps the recording in the cloud. For her vendor calls, she sticks to the Mac.

She still writes notes. They're just shorter now, and she no longer has to rely on them.

If your week is mostly calls and you've ever been asked "did we agree to that?", VoxStudio for Mac is free to try for 14 days, and after that you can keep using it on recordings up to 15 minutes long. It needs an Apple silicon Mac with macOS 15 or later. Record one call, then ask it one question you'd normally dig through your notes for.

Comments

Popular posts from this blog

570 visitors, 17 clicks, zero downloads: what a too-small OpenAI ad taught me about growing VoxStudio

Speaker Labels vs. Speaker Names: Getting "Who Said What" Right in Mac Transcripts

The quote her editor asked about at 9:40 p.m.