Plum's session history shows the first call going out at 4:39 PM EDT, which looks right, but the second block of those calls (21:19-21:34) going out two hours later, from 6:23PM EDT until 6:39PM. I have a screenshot of the logs, though it doesn't appear I can attach it here. The customer complained that they didn't get the calls until after they were home for the evening.

Has Plum recently had some queueing / delay issues? Is there any SLA about call delay?

Incidentally, either the timezones used or the system clocks in Plum are often somewhat off, leading us to feel somewhat uncertain about trusting them and making it hard for us to track down specific calls. Here's an example from the first few lines of a recent call log. In this example, the second timestamp was correct:

Regarding your first question, there was an issue on 8/11 for which you should have received a notification directly from Plum Support with all of the details you are looking for. If you did not receive this email or are looking for further details about your particular issue please email us at support@plumgroup.com with your customer number in the subject line.

Regarding your second question, we have filed a bug with our development team who will look into this issue further. The timestamp within the call logs is the correct value, the timestamp at the top of the page appears to be specific to your timezone (albeit with the incorrect timezone listed). We will let you know when a patch has been deployed for this issue.