Meetbot review: checking what the bot heard before it reaches Bigin
Example data for theStacc's sales team on Tue 27 Oct 2026: three calls, one clean, one with no clear deal, one the bot missed. 12 screens; 12 are tagged Needs backend work. Click a screen to open it; each page has Prev and Next for its journey and a link back here. Nothing here is connected to a real account.
What this shows
- The call note is written straight away, so a call is never lost. Anything that changes the deal (tasks, amount, closing date, stage) waits for a tap.
- Confidence only decides what is ticked by default. Stage is never ticked by default, and nothing is written without the rep.
- Every change shows the current Bigin value, the proposed value and the exact caption line it came from, so a mis-heard number is easy to spot and correct.
- Telegram handles the common case in one tap; the web page handles corrections, picking a deal, recovering a missed call, undo and retry.
- When the bot is not let in or captures almost nothing, the rep is told during the call and can rebuild the call from the recording and their own notes.
1After a normal call
The rep checks six proposed changes, corrects a mis-heard amount and writes them. The call note is already in Bigin.
TG01Telegram: review card after the callNeeds backend workOne message per call listing every pending change; a batch callback that writes the ticked set once
RV02Call review: Kestrel SolarNeeds backend workReview page served by meetbot; reads pending changes from SQLite under the same lease as the Telegram buttons
RV03Correct a mis-heard amountNeeds backend workStore corrected value, reason and who corrected it; serve a short recording clip by caption time
RV04Confirm the writeNeeds backend workBatch write with a per-record result; one-time lease so a Telegram tap cannot write the same set twice
RV07Activity: what was written, undo and retryNeeds backend workExpose the writes table; undo restores the old value only if Bigin still holds the value Meetbot wrote; retry only failed records
RV08Write rulesNeeds backend workMove the write policy from code constants into stored settings; reminder and expiry jobs2When the bot is not sure which deal
The invite matches a contact with two open deals, so the rep picks one before anything is drafted.
RV01Review queueNeeds backend workQueue query over processed calls and pending changes, per rep
TG02Telegram: no deal matchedNeeds backend workExisting unmatched prompt, plus a link to the web picker and one-time buttons shared with it
RV05Pick the deal for an unmatched callNeeds backend workDeal search across Bigin; candidate list kept from the matcher; extraction runs after the link (exists today)3When the bot misses the meeting
The prospect hosts the call, the bot waits in the lobby, and the rep recovers the call from the recording and their own notes.
TG03Telegram: Notetaker waiting to be let inNeeds backend workHandle Attendee's waiting-room state; alert after 2 minutes in the lobby; skip removes the bot
TG04Telegram: almost nothing capturedNeeds backend workWhisper re-transcription job from the Attendee mp3; no-show marker; buttons for each recovery path
RV06Recover a missed callNeeds backend workWhisper transcription of the Attendee mp3; merge rep notes with the recording transcript before extraction; mark note-based values