We’ve been busy! Here’s a snapshot of some of the new features we’ve recently added to the Calenzen platform.
BlueJeans meetings with a participant passcode are now detected and properly incorporated into tokenization.
We look for URLs with the passcode embedded and extract out the meeting ID and the passcode:
https://bluejeans.com/1234567890/1234 → meeting ID is 1234567890 and passcode is 1234
These are tokenized to the following in processed meetings:
A single account can not support multiple paying users. With this change you can buy Calenzen for the entire team for all of 2020.
Our fallback tokenizer detects non-vendor specific conferences using our Generic processing engine.
This started out as a rather naive implementation that looks for text resembling a phone number along with additional number groupings that following on the same line.
With our latest update this has been improved to scan for bridge numbers followed by meeting IDs across multiple lines.
At present we detect the following scenarios:
Capture meeting IDs containing multiple numbers if found after a valid US phone number.
888-555-1212 [any text] 12345678
Fold subsequent lines that begin with leading spaces and scan for meeting IDs therein.
888-555-1212 [leading spaces] [any text] 12345678
Capture meeting IDs from subsequent lines if they include keywords like “pin” or “ID”.
888-555-1212 [any text] (pin or id keywords) 12345678