Welcome access here Audience Global Support and ODDU L2 Ticket Portal
Atria Support & Unified Ticketing System
Dear All, in our continuous effort to improve we are moving towards a Unified Ticketing System.
- For Atria Support to raise a request tickets please use Service Desk.
- All request for changes are still managed through Service Now Change Management module.
If you have any questions or issues related to Atria Support please refer to Jan Fric, Atria Support Manager.
| 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) | To ensure the team can support you faster and efficiently a Good Description for a ticket request must contain: 1) Title, what is the request for, with concise subject and the correct category (e.g., weighting not running, rerun failure, etc.); 2) the Description, what you want L2 support team to do, it must describe comprehensively the problem/request including, what you (L1) have done to resolve (this is essential) with the analysis, investigation, relevant logs, errors, reports, data files, tests, panel homes/individuals, application/s and version/s. Where possible should always provide evidence like pics/audio; 3) Please ensure all other mandatory fields are completed. An incomplete / not acceptable description could lead to delay or, return to “waiting for customer” state. |
| 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 |