Common Mistakes
The patterns that quietly cost you time, money, and accuracy.
Treating Amua like just a chat app#
Amua isn't just another Telegram client. All your chats still work the same, but Amua’s power comes from the layer on top of them. If your setup still looks like plain Telegram (a flat list of chats held together with pins and folders), you aren’t getting much out of Amua yet.
Using the workspace as your main chat feed#
The workspace tabs are meant for organizing your chats, not actually messaging at scale. You'll have a better experience using the chat section with filters where you can interact with more chats faster and with more detail.
Not utilizing subgroups#
Subgroups are how you organize your workspace. They link the right people to the right chats so you can manage things in bulk instead of one person or chat at a time.
If you're adding people to multiple chats by hand, or your workspace has no structure below the top level, you should be using subgroups.
Splitting one business across multiple workspaces#
Use one workspace per business entity. Splitting one company into two workspaces creates two different sources of truth, and you can't act across both at once.
To separate departments, teams, or clients within one business, use subgroups.
Onboarding, offboarding, and permissioning mistakes#
Don't add new hires one chat at a time. Add them to the right subgroups and they'll get added to the right chats at once.
Forgetting the one-week audit. New hires sometimes end up in the wrong chats or missing from chats they should be in. Audit on day 7.
Don't delay offboarding. The window between someone leaving and being removed from company chats can be very sensitive. To remove an ex-employee from the workspace and all associated company chats, navigate to their card on the Team tab, click the overflow menu, and select "Remove from workspace and all chats."
Assuming removal was complete. "Remove from workspace and all chats" only reaches every chat that you have administrative control over. If you weren't an owner or admin in a chat, they may still be in it. Verify in the activity hub as well as the operation report.
Be mindful with roles. Adding someone as a Member when they should be an Admin means coming back later. Set the role during onboarding.
Treating Admin as a default role. Admin is for trusted operators who you've trusted to delegate managerial capabilities across your company. This might be other C-level executives or certain department heads, like Head of HR. Otherwise, most people should be Members.
Assuming an Amua role grants a Telegram role. It doesn't. You can be a workspace Admin and still have no administrative control in a given Telegram chat, which means no ability to remove someone (like an ex-employee) from it. Check the Overview tab to see where you actually hold Telegram chat admin rights.