Plan requirement
| Subscription | Any plan |
| Access | Admin |
Installing, configuring and removing. The scope setting is the one people leave at its default.
Install one
- Open the apps in Admin Center.
- Find the app and install it.
- Configure its settings.
- Restrict it to the groups or roles that need it.
- Tell those agents it is there and what it does.
Restrict the scope
By default an app is available to everybody. An app relevant to one team adds a panel to every agent's screen, and interface clutter is a real cost.
Restricting it is one setting and it is worth doing every time.
Tell people it exists
An app nobody knows about is an app nobody uses. Two sentences at a team meeting is the difference between a purchase and a tool.
Test it on a real ticket
Not on a test one. Apps behave differently with real data, real attachments and real customers, and the difference usually shows up in the first hour of real use.
Removing one
Uninstall it, and separately cancel any subscription with the developer. Those are two actions, and missing the second leaves a charge for an app nobody has.
Check what depends on it
Fields, tags or triggers the app created will still be referenced after it is gone. Look before uninstalling rather than debugging afterwards.
Review the list annually
Every app is a third party with access to your tickets. Removing what nobody uses is a security improvement as much as a tidy-up.
Comments
0 comments
Article is closed for comments.