Rewrite the app catalog copy for the people who read it

Featurekamo-shared-library
Shipped
15 Agosti 2026, 03:53 UTC
Author
Kamo
Commit
14f0b4c

The display name and description on ServiceType are the only description of an app most people ever see: an org admin on Settings -> Apps & Features, a parent-org admin deciding what its child orgs may use on the branch-types screen, and now whoever is creating an organization in the network wizard -- someone who has typically never used the platform before. Two things were wrong with that copy, and both cost customers. It described the implementation. "AI-powered assistant with chat, RAG integration", "Voice Over IP PBX Phone System", "Self-hosted video conferencing", "Personal document storage with Docs editing", "Falls back to parent organization SMTP when disabled" -- accurate to an engineer, and no help at all to a business owner deciding whether they want the thing. Worse, it presented Kamo's own implementation as the whole app. E-Mail, Phone and Meetings are each a provider abstraction -- EmailProviderType, VoipProviderType and MeetingProviderType each ship a Kamo provider alongside Google Workspace / Microsoft 365 / Zoho / Exchange / IMAP, RingCentral and Teams Phone, Zoom and Teams. "E-Mail - E-Mail Hosting" reads as "tick this if you want Kamo to host your mail", so every org already on Workspace or 365 had a reason to decoder an app built for exactly them. Also fills two genuine gaps the copy never mentioned: HR owns the legal and disclosure documents staff have to read and sign, and Marketing sends bulk and drip email campaigns. ServiceTypeCustomerCopyTest pins both mistakes so they cannot come back. Constant names are untouched -- **************** persists the name as a string, so a rename would silently reassign every security model's grants.

All changes

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei