Eleven meetings a day, each one drafted afterwards from the meeting record, its participants and the space where the conversation carried on. Decisions and owners named, thin records flagged as thin.
In a Webex-heavy organisation the calendar is the job. Eleven meetings, two of which mattered, and the actions from those two live in one person’s notebook. Writing a decent follow-up takes fifteen minutes, and there was another meeting.
A companion reads meetings, recordings, spaces and people, and drafts what should have gone out afterwards. It does eleven of them while you are in the twelfth.
01
What does a companion do after a meeting?
Assembles the follow-up from what exists: the meeting record, its participants, whether a recording was produced, and the space where the conversation continued. Out of that comes a note naming decisions and owners.
Where the record is too thin to say anything, it says so and points at the recording instead of pretending to know what was said.
02
Are the spaces worth reading?
Often more than the meetings.
A space attached to a project holds the real status: what slipped, what nobody wanted to say on the call, which file is the current one. A companion reads the messages and memberships and returns decisions with links.
It also finds the spaces that have gone quiet, which is a good signal about which projects have stopped.
03
Tidying up recordings and dormant spaces
Recording storage, dormant spaces, external participants who still have access to something, and the meetings that recur weekly with three attendees out of twelve. A companion reads the lists and reports specifics; every deletion or removal is confirmed individually.
Licensing, device management, calling setup, security policy and compliance retention are Control Hub’s domain.
The available Webex actions follow the vendor’s public API, so check that the object you care about is exposed before you plan a routine around it. That holds for every tier-two connection and it is cheap to verify.
It drafts them from the meeting record, the participants and the space where the conversation continued, and says when the record is too thin to summarise. It works from records rather than audio.
Yes. Connect the account and a companion reads meetings, recordings, spaces and people, and drafts what should have gone out afterwards. The Webex public API defines the actions available.
Yes, with decisions, owners and message links. A companion also flags the spaces that have gone quiet, which is a decent proxy for projects that have stalled.
It lists them with dates, sizes and owners. Deleting or removing access is confirmed individually, since both are irreversible and affect other people.
For assembling the follow-up from meeting records, spaces and the systems where the work lives, an agentic browser does the whole pass in one go. Download Strawberry and try one week of meetings.
Webex Strawberry