...
| Note | ||
|---|---|---|
| ||
Dear All, in our continuous effort to improve we are moving towards a Unified Ticketing System.
If you have any questions or issues related to Atria Support please refer to Jan Fric, Atria Support Manager. |
AGS Global Support Training & Documentation
| TICKETING | TECHNOLOGY COMPONENTS | |
|---|---|---|
Atria Support Global > All Markets | Atria Cloud, Atria NG/NGI, Atria Online (FMDP, VMRG), Atria QC framework, Aten, Portal, AtriaPro, Atria Portable, Transmission Logs. | |
Atria Support Service Now > Kantar Markets (see note above) | ||
| Watermarking Documentation | ||
| TV Meters Documentation | ||
| /wiki/spaces/EVME/overview | ||
| ODDU Documentation | ||
 | Good Ticket Description (L1) | An acceptable description to raise To ensure the team can support you faster and efficiently a Good Description for a ticket request must state whatcontain: 1) Title, what is the request for using, with concise subject and the correct category (e.g., weighting not running, rerun failure, etc.) . Must explain; 2) the Description, what you likewant L2 support team to do with a full description of, it must describe comprehensively the problem/request including :, what you (L1) have done to resolve, anyall relevant logs, errors, reports, data files, tests, panel homes/individuals, application/s and version/s. Where possible also add pics/audio; 3) Please ensure all other mandatory fields are completed. An incomplete / not acceptable description could lead to delay or return back to customer. |
| Service Desk | User Guide. |
| Service Now | User Guide should be accessed through main service now portal. |
| Confluence access | If you need access to Confluence please review requirements here |
| AGS Know-How - sharepoint | AGS Global Support Training & Documentation |
...