Anthropic adds five beta features to the Claude Suite

By Priya Raman

Anthropic has introduced five Claude Suite features in beta: meetings, whiteboards, sheets, Claude data and interactive connectors. All five require a paid plan, and some remain restricted to enterprise users, so availability already depends on an organization’s contract as much as on the product’s capabilities.

What changes inside a Google Meet call?

Meetings gives Claude a role during a virtual call: users can assign it drafting a plan, mapping a timeline or retrieving data. When the call ends, Claude saves the action items for follow-up. The stated goal is to shift the focus of meetings from discussion to execution. The launch names Google Meet as its starting point.

The catch is access. The feature reportedly will not join calls with external guests unless an administrator explicitly permits it, and meetings is limited to teams and enterprise plans. Tool Finder, which describes the rollout, says its account draws on a few external sources and shares limited detail about the integration.

That leaves operational questions open: how an admin grants access, what a guest sees, and how Claude handles a request that the meeting participant did not authorize. The account supplies no answers, performance measures or comparison with another meeting assistant.

What do whiteboards and sheets add?

Whiteboards converts documents or ideas into visual elements when a user mentions Claude in chat. The rollout describes the output as “neat and linear,” which specifies an arrangement but not whether people can edit, annotate or reuse what Claude produces. Anthropic makes the feature available on web, desktop and mobile; it remains in beta for paid users.

Sheets brings collaborative spreadsheets to Claude. It supports tabs, formulas, formatting and drop-down menus, and lets people edit cells together in real time. Teams can use it to build a campaign tracker or hiring budget, an experience the source compares with Excel. Sheets is also beta and available only to paid users.

What can Claude data connect to?

Claude data, previously called dashboards, connects to company systems or CRMs to produce dashboards and written data stories. Anthropic positions it for larger, fast-moving teams that want pitch decks or quicker analysis, with flexibility in how results appear. It does not claim to replace other applications.

The source names no particular CRM, permission model, refresh interval or example output. That makes “written data stories” a description of a format, not a demonstrated result: no reporting-time, accuracy or user-study figures appear in the rollout.

Do embedded apps really reduce context switching?

Interactive connectors embed what the source calls “full versions” of Adobe, Atlassian and HubSpot inside Claude, so a user can work with an application without moving to another platform. The stated benefit is less context switching and a more unified workspace. Tool Finder compares the approach with a similar offering from PandaDoc, a parallel rather than proof of superior productivity.

None of the three named apps comes with a task list of supported actions, and the account does not say whether permissions or embedded behavior match the standalone product. No time-saved or completion-rate measurement backs the claim.

What should enterprise teams test?

Taken together, the features deepen Claude’s enterprise offering and may reduce handoffs between meetings, spreadsheets, company data and business applications. Tool Finder reads that direction as a likely effort to increase Claude’s public offering value; the company has not stated that strategy as a formal target.

Teams already using Claude have a practical way to test the promise: whether a meeting assignment produces a usable action item, whether co-edited cells stay consistent, and whether an embedded app keeps the data and permissions it needs. Those checks measure work completed, not features shipped.

During beta, the missing measures remain missing. If Anthropic documents access rules, supported systems and actual gains, the package could mature into a more coherent enterprise workspace. Until then, teams should treat the promised efficiency as unproven.