Communication & Workplace Apps

Meta’s messaging app; the account is the phone number, which is why it works for contacting people who never installed anything “for work”. End-to-end encryption covers one-to-one chats, group chats, calls and status by default. The trade-offs that matter at work: it has no true desktop client independent of the phone, message history lives on the device, and there is no meaningful admin control on the free tier.Also covered here: WhatsApp Business, a separate listing with a catalogue, quick replies and label-based inbox — that is the one small sellers actually run, not the personal app.

Chat tied to a Facebook account rather than a phone number, which is the whole story: convenient if your customers already reach you through a Facebook page, awkward if you would rather not have workplace conversations sitting inside a social profile. Note: this listing and Messenger describe the same service; we keep one page as the reference and treat the other as a duplicate variant.

Cloud-first messenger: history syncs across devices by default, groups are very large, and channels plus bots make it useful as a broadcast tool rather than only a chat app. The caveat people repeat incorrectly — ordinary chats are cloud chats with server-side encryption, not end-to-end. End-to-end applies to Secret Chats, which are device-bound and do not sync. If a workflow depends on “Telegram is encrypted”, check which chat type it means.

The reference case for default end-to-end encryption with minimal metadata, run by a non-profit, open source, and free of advertising and cloud backup history by design. Consequences worth knowing: losing the device without a backed passphrase loses messages, and the small feature surface is deliberate rather than a shortfall.

Long-established alternative with strong adoption in parts of Europe and Southeast Asia; supports end-to-end encrypted one-to-one and group chats and public accounts. Practical value is mostly regional: it is the messenger the other person already has.

A number and messaging service rather than a chat-only app: it provisions a phone number for calling and SMS over data, which is why people use it as a second line. Because the model is advertising- or plan-supported, read the current terms before relying on it as a permanent work number — a number you cannot keep is worse than no number.

Servers, channels, roles and always-available voice — a community layer rather than a one-to-one messenger. It works well when the audience wants to gather, and badly when a company uses it as an unofficial support channel with no archive, no SLA and no way to reach a specific person who has gone quiet.

Username-based, historically popular because no phone number is required. Worth stating plainly: weak moderation and abuse history are the reason most organisations block it, and “anonymous” cuts both ways in a business context.

An AI assistant surface rather than a people-messenger; it appears in this hub because stores and users file it under chat. Different category in practice — the useful comparison is against other assistants, not against Signal or WhatsApp. Listed here for completeness with that caveat.

Chat inside a Google workspace: direct messages plus spaces, with files landing in Drive and history retained against the organisation’s policy rather than the handset. If email is your system of record and Drive is your filing cabinet, this is the version of chat that does not create a second unmanaged store of facts. Note that Google has moved the classic Hangouts chat service to Chat; if you are still on a Hangouts link, that is a migration question, not a preference.

Android’s default SMS/RCS client, and the reason the other apps on this list are not quite comparable: it carries the ordinary phone number, including two-factor codes. RCS gives read receipts, typing indicators and better media between carriers that support it, with end-to-end encryption for one-to-one RCS chats between two compatible clients — not for SMS fallback, and not for group chats at first. Verify on the current listing, because this has been rolling out in pieces.

A separate listing whose title overlaps with the above; in practice this is the same service family, and the naming collision is exactly the kind of thing our “is this the product I meant” criterion exists for. Confirm the developer and package name before installing anything chosen by search result alone.

The main client: meetings, team chat, phone and whiteboard under one login. Both listings in this group point at it; we are consolidating them to a single reference page so the choice stops being arbitrary.Two pages, one product — a duplicate we keep because you asked us not to delete either; we will differentiate or mark one noindex rather than let readers guess.

A build aimed at ChromeOS devices, where the ordinary Android package is not the recommended path. This one exists for a reason; it is not a duplicate.

Wrappers for organisations managing devices through Microsoft Intune / mobile device management, so the app can be policy-managed, protected and remotely wiped like the rest of the fleet. If nobody in your organisation administers devices, you do not need these and should install the plain client.

The panel that lives on a tablet mounted to a conference-room table — join, share, end. It is a room fixture, not a personal meeting app, and the two things are frequently confused.

Chat, channels, files and meetings under one Microsoft identity, which is also its main weakness as a standalone choice: the value is high if the organisation already lives in Microsoft 365 and mediocre if it does not, because you inherit a licence dependency for the collaboration half.

Meeting client for Google workspaces, with recording and moderation controls tied to the workspace tier rather than to the app. Bundled with Chat and Calendar above; treat them as one decision rather than three.

Historic listing. Google consolidated its consumer video calling into Meet; a Duo listing you find today is usually a legacy artefact rather than a product to adopt. We keep the page because it explains what happened to the thing people still search for — which we would rather do than delete and leave a dead end.

Legacy. Microsoft retired the Skype for Business Online service in favour of Teams, so a new deployment should be planned on Teams; if you are still seeing this app in an estate, that is a migration item to close, not a preference to defend.

Work-management and spreadsheet-style project tracking — not a meeting tool. It appears in this section only because our classifier grouped the name; it belongs under collaboration below, and this note is the honest interim state.

Real-time co-editing with server-side version history, which is the feature people underestimate until they need it: the audit trail is the organisation’s, not the individual’s. Offline editing on mobile is a separate app behaviour worth testing before you rely on it on a flight.

Pages, wikis and databases that shade into light project management; strong for a team that wants one place to write things down and link them, weaker as a substitute for a real spreadsheet or a document with proper tracked changes. The cost of leaving — export size and fidelity — is the question to ask before adopting it.

Channel-based conversation with integrations and workflow automation, and an archive depth that is a licensing decision rather than a technical one. Its practical failure mode is not noise but silence: a decision made in a private channel that never reaches the document everyone else is reading.

Sync and shared links with reliable cross-platform behaviour and a long history as the default for sending a large file as a link rather than an attachment. Note that link expiry and password protection are plan-dependent, so “we sent it securely” needs checking against the actual plan.

A mobile office suite for opening and editing Office-format documents on a handset or tablet. The realistic role is viewing and light edits: formatting fidelity on complex documents is where third-party suites diverge from the originals, so do not judge it on a document that matters until you have round-tripped one.

Professional network with a job board attached; the durable value is the network and the referral path, which is also why recruiters search it. Two listings, one service family.

An aggregator with the widest raw volume, and the corresponding noise problem: ease of applying floods employers with low-intent applications. Good for breadth and salary benchmarks, poor as a filter for senior or specialist roles.

Aggregator plus employer-side distribution, marketed on matching. Same caveat as above in reverse: matching quality is invisible to the candidate, so treat alerts as a convenience, not a filter.

Where the useful content is not listings but employer-reported salaries and reviews. Read reviews as directional and adversarially selected — the distribution is bimodal — and take the salary data far more seriously than the prose.

One of the older boards, now largely a distribution and resume-hosting layer. Fine as an additional surface; not a reason to skip the two above.

Productised freelance marketplace: you buy a defined deliverable rather than hiring hours. Work quality is a function of how precisely the buyer specifies it, and the platform fee sits on both sides — put that in the quote before you accept.

The client people confuse with the protocol. What matters on a work account is what the organisation can retain and what the client lets you control: delegated access, confidential-mode expiry, and whether third-party add-ons can read the thread.

A device-bundled client that will happily read Exchange and IMAP accounts. Convenient; the trade-off is that account settings, notification behaviour and any corporate policy applied through device management sit with the handset rather than with a managed mail app.

Where “who can see my availability, and can they see the title of the appointment” is configured — a privacy setting most people never look for because they are looking for a diary. Shared calendars and appointment scheduling links are the reason it becomes infrastructure rather than an app.

Deliberately small: subtasks, due dates, and a place to park commitments. It stays in this hub because its integration is the point — a list that appears beside the mail and calendar you already look at beats a better list nobody opens.