Meeting platforms currently supported by Room Calendar parsing

VCA Room Calendar can currently recognize join links from multiple mainstream meeting platforms.
For some platforms, VCA can also extract meetingId and meetingPassword from the URL itself or from structured invitation content.

This article explains:

• which meeting platforms are currently supported
• which fields VCA can usually extract
• when parsing may still be limited

How parsing works

VCA does not rely on a single language template.

The parser uses this priority order:

1. Provider-specific URL structure
2. Explicit invitation fields such as Meeting ID, Passcode, 会议号, or 会议密码
3. Provider-specific structured fallback rules

This makes parsing more stable across Chinese, English, and other localized invitation templates.

Currently supported platforms

Important limitations

Join link support is more reliable than passcode support

For most platforms, VCA can recognize the join link more reliably than the passcode.

This is because:

• many providers encode the join URL in a stable official format
• some providers do not include the passcode in the URL
• some invitations omit the passcode entirely

If the invitation does not contain a stable passcode field, VCA will return meetingPassword = null instead of guessing.

Personal room links do not always expose a meeting ID

Some platforms use personal-room or vanity links.
In those cases, the join URL may still be recognized correctly, but a separate numeric meetingId may not exist in the source invitation.

Calendar systems may remove useful body content

If your calendar provider or room mailbox strips the invitation body, some third-party platforms may lose their structured meeting fields even though the event itself is still visible.

If you are using Microsoft 365 room resource mailboxes, see:

• Microsoft 365 room mailboxes show organizer names or fail to parse third-party meetings

Platforms not currently included

The following kinds of meeting links are not yet treated as first-class providers:

• fixed-room browser platforms such as Whereby
• custom enterprise portals that wrap the real meeting URL
• webinar or livestream links that do not expose a stable meeting structure

These links may still appear in event bodies, but VCA does not currently guarantee provider-aware parsing for them.

If you want us to support another platform

The fastest way to add a new provider is to share a real invitation sample.

Please include:

• the full invitation body
• the join URL
• the meeting ID line, if present
• the passcode or password line, if present
• at least one sample in the language your users actually receive

The more complete the sample is, the more likely we can add a stable parser instead of a fragile keyword-based workaround.