Reports Archiver

overview the report archiver facilitates the storage, and distribution of historical reports it migrates data from the active ameyo database to a report database, and finally to a third party ftp server report management template management users (administrators) can create custom report templates for frequently used queries templates can be edited, deleted, or run on demand via the template list output formats reports can be generated in csv, xls, pdf, and html queue management the queue tab provides a history of all report requests, showing status (success/fail), request time, and download links for generated files for more information on contact center reporting, please check out this link docid\ nwourz6fw0anjdss6hvkn automated scheduler the scheduler allows for the automatic generation and delivery of reports based on a set frequency (hourly, daily, weekly, monthly, yearly) step 1 create delivery profiles before scheduling a report, delivery destinations must be configured email profile smtp configuration set up the sender email, password, and server details delivery mode choose to send reports as attachments or embed them in the email body recipients define to, cc, and bcc addresses ftp profile connection configure host ip, port (default 21), username, and password destination specify the folder path on the remote server where reports will be saved step 2 configure schedule select report choose from the list of available ameyo reports (e g , agent productivity, specific campaign reports) set frequency define how often the report runs (e g , "every monday at 9 00 am") data window specify the time range for the data (e g , "last week" or "current month") advanced filters ftp configuration link an ftp profile for automatic file storage optional fields select specific metrics to include, such as max hold time or process name charts option to include visual graphs like abandoned call analysis or queue wait time analysis operational guidelines prerequisites licensing separate licenses are required for report archiver infrastructure dedicated archiver server (windows/linux) network storage (nas/san) accessible via ftp/mapped drive ameyo call manager (for vla) and ameyo database access sizing considerations proper sizing is essential for performance factors influencing server requirements include total agents and calls per day average call duration retention period (e g , 1 year vs 5 years) retention & cleanup data lifecycle data is retained based on the configured policy (e g , 3 years) auto cleanup the system can be configured to automatically purge data older than the retention period to free up storage, though archival to external media is recommended before purging privileges privilege key description default roles contactcenter\ dacx cc admin reports archiver\ invoke access open report archiver and manage templates / schedulers administrator contactcenter\ dacx cc admin reports archiver delivery profile\ invoke access create / edit email (smtp) and ftp delivery profiles administrator contactcenter\ dacx cc admin reports archiver template\ invoke access create / edit / delete report templates administrator contactcenter\ dacx cc admin reports archiver retention\ invoke access configure retention and auto cleanup administrator configuration parameters key / parameter description how to configure constraints sample output format file format for generated reports template editor csv / xls / pdf / html xls schedule frequency how often the scheduler runs scheduler form hourly / daily / weekly / monthly / yearly every monday 09 00 data window range of data the report covers scheduler form last hour / last day / last week / current month / custom last week email delivery profile smtp profile used for email delivery delivery profiles > email profile valid smtp host + credentials smtp example com 587 ftp delivery profile ftp destination for the generated file delivery profiles > ftp profile host / port / user / path ftp\ //files example com/reports/ retention policy days / months the archive is kept retention 1–n years 3 years auto cleanup whether older data is purged automatically retention > auto cleanup on/off on infrastructure dedicated archiver server + nas/san + ftp deployment time; sized by agent / call volume / retention requires licensed archiver server 1 archiver vm, 2 tb nas limitations licensed module — confirm with the exotel account team before enabling retention is enforced by auto cleanup ; external backup to tape / object storage is recommended before purge smtp delivery obeys the mailbox's own size limit (most providers reject attachments > 25 mb); use ftp for large reports related pages archiving solution — umbrella doc report scheduling & exporting — the console side scheduler voice logger and archival (vla) / interaction archiver — sibling archivers high availability & disaster recovery / understanding business continuity plan (bcp)