Sagetap Integration
Sagetap, where buyers hold evaluation sessions with vendors, sent a second stream of prospect calls, but as rough transcripts with no names, dates or company.
Sagetap calls now go through the same recorder as every other call, and the dashboard tags each call with its source. One call ran end to end; a second waits.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Sagetap recordings are uploaded to the same recorder as other calls, so the pipeline reads them the same way.
One path for every call · came from Mark Parson
- The call list and each call page show a small source tag, Avoma or Sagetap. In words
- A script uploads a Sagetap video and fills in its details from the file name. In words
- One Sagetap call ran end to end; the second and some small fixes were left for later. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
market-analyst-c6-D1 Upload Sagetap videos to Avoma and let it transcribe and assign speakers, instead of preprocessing Sagetap's CSV transcripts. — Mark Parson
Sagetap recordings are uploaded to the same recorder as other calls, so the pipeline reads them the same way.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Routed Sagetap calls through the recorder Qpoint already had
Git authorship: the record names nobody; the Sagetap commits (2026-03-17, 2026-03-23) are his.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 1 decisions · 9 key-change entries · 1,283 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c6 →