ChatGPT Prompts for Microsoft Teams (Chat, Channels, Meetings)

Design Teams channel structure for [team / org]. Output: which channels exist (rule of thumb: ≤10 channels per team), naming convention, public vs private rules, channel description templates, when to spin up new channel vs use existing. Prevent channel sprawl.

Help me decide: chat (DM/group chat) vs channel post for this content. Channel = topic-based, persistent, broadly relevant. Chat = ad-hoc, ephemeral, narrow audience. Misuse blurs purpose. Default to channel for work-relevant content.

Standardize channel descriptions across [team]. Output: template (purpose, when to post here vs not, who owns, tags used), example for each channel type. Description = first impression for new members; default Teams description is empty.

When private channels appropriate. Examples: [describe]. Decision framework: confidential discussions only (HR, legal, deal-sensitive), not for "we don't want them seeing." Private channels can't convert back; choose carefully.

Setup Teams meeting for [purpose]. Options to set: lobby controls (external attendees wait), recording (notify + ask), captions, breakout rooms if needed, attendee notification, polls. Default settings often wrong; intentional setup matters.

Workflow for Teams meeting recording + transcript. Output: when to record (yes by default, ask consent), transcript review, distribution to absent attendees, retention policy, search later. Recording without workflow = forgotten asset.

Hybrid Teams meeting etiquette (some in-room, some remote). Output: in-room rules (single mic, one speaker at a time, camera on for in-room), remote-first practice (all on individual cameras even if in-room), facilitator role. Hybrid is hard; rules help.

Use Teams polls in [meeting type]. When to poll (decision points, opinion gathering, knowledge check), how to design poll question (clear, single-answer typically), follow-up on results. Engagement tactic underused.

Set up file collaboration in Teams channel. Where files live (channel Files tab → SharePoint), naming convention, version control, who can edit, archive cadence. Files in chat → lost. Files in channel → findable.

Co-author docs in Teams (Word/Excel/PPT). Etiquette: announce when editing major sections, comment vs edit decision, version conflict resolution, when to lock for owner editing. Co-authoring without etiquette = edits clobbered.

New team member onboarding to Teams. Output: tour of relevant channels, expected etiquette, where files live, recurring meetings calendar, who-to-DM-for-what, first-week checklist. Most onboarding skips Teams basics.

External guests (clients/contractors) in Teams. Setup: which channels they access, file permissions, watermarking sensitive docs, removal cadence after engagement, security review. External access = risk + need.

Reply in channel thread vs DM the sender. Decision rule: relevant to channel = thread reply; only relevant to sender = DM. Thread for visibility; DM for narrow. Most reply-alls should be threads.

@mention etiquette. @person = expect their attention. @channel = expect EVERYONE's attention. @team = whole team. Calibrate: @person sparingly, @channel rare, @team almost never. Over-mention = ignored.

Set up Teams status + working hours. Why: protect focus time, signal availability. Output: status meanings (available, busy, do-not-disturb, focus), working hours configured, automatic away, after-hours norms. Discipline = reclaimed time.