FileLink is like another type of virtual CUBE — each one shows up with its own name, serial number etc in CUBE MC just like a physical CUBE device would.  It is managed in the same way, including linking folders to it, where you can use not-before/not-after dates on the various files.    You also then associate one or more email addresses to each FileLink serial, and specify what kind of format each should deliver (eg mp3, wav, ulaw etc).

What FileLink then does, is that it generates a mixed production automatically whenever the linked content changes (for example: new content added, not-before/not-after dates trigger, etc) according to the same “primary settings” as the physical device would use (fade time etc), and executing the full interleaving logic.   It then sends a branded email to the email addresses linked to that serial, to notify them of the new content.  It doesn’t include the mixed file directly on this email, but instead a button to a web page from where the customer can “download” the file.   When the customer “downloads” the file, this updates the manifest status indicator in MC (in the same way this works for physical devices).

If no one pulls the file, the manifest status remains “pending” and a follow-up notification is sent a few days later, and then a few days later again, on a specific cycle.