Here are some tips on what to do if you couldn't find an answer to your question in the Knowledge Base.
Nobody is perfect - that's why it can unfortunately sometimes happen that something doesn't quite work as it should. But don't worry, we're here to help fix it!
Basically, a distinction must be made between 3 categories:
1. Errors in the functionality of the app
e.g. login does not work
2. Feature not available
e.g. I would like to see more info here
3. Error in the configuration
e.g. table 2 is located somewhere else than shown in the plan
Depending on which of the above 3 categories it is, the further procedure differs. In general, however, the following applies:
If you can't find an answer here in the Knowledge Base, your first point of contact is always the person responsible for Seatti in your company.
If you don't know who this is, you will most likely find this info in one of the following places:
- Service Desk / Ticket Portal, where there is a category related to applications or Seatti directly, if applicable, and you can create a ticket with your question.
- Sharepoint article about Seatti
- Teams channel about Seatti
- Email announcing (the launch of or updates to) Seatti.
Namely, the onsite contact can assess whether it is a configuration change or a technical issue on the Seatti side.
Changes to the configuration can be easily done by your admin.
Whether a table is right or wrong is as difficult for Seatti, who don't know your office personally, to judge as other location- or person-related requests, such as permissions and group memberships, which can only be changed internally by IT anyway.
Technical issues can be submitted by your admin via a ticket to Seatti and will then receive appropriate status updates for troubleshooting.
To make it easier for your admin and Seatti to help you, you can check the following in advance and send it as a screenshot if necessary:
- test if the behavior is the same everywhere
- Seatti within MS Teams
- Seatti in the browser (my.seatti.co)
- Seatti in MS Teams in the browser (teams.microsoft.com)
(this will help you to determine if the problem is with Teams or with Seatti)
- screenshot of the problem (preferably of the whole window, so that other parameters (such as filters, timings, etc.) can be checked directly to narrow down the source of the problem)
- A description of
- what did you actually expect?
- and what happened instead?
- check the network tab in the developer tools
(a bit more technical and described here in more detail)