PU Prime Customer Service: What to Record While It Happens (Canada)
Parts of a support case exist only while they are on your screen — the exact time, the wording of a message, the state of the screen around it. Which of them to record on the spot, and which your account history keeps for you.
Open PU Prime Account →Record four things while the event is still on your screen: the exact time as the platform showed it, the wording of the message as it was written, the order or transaction number, and a picture of the screen. The number and the amounts are kept in your account history anyway. The time you read, the exact wording and the state of the screen are kept by nobody but you.
What perishes on the screen, and what is kept for you anyway
| What it is | How long you can still take it | What is left if you did not |
|---|---|---|
| The exact time, read off the clock you were watching | Only while the screen is still in front of you | An hour, roughly — which lines up with nothing |
| The wording of a message, word for word | Until the panel refreshes or you click away | A paraphrase: close in meaning, useless for matching |
| The state of the screen around it | Until the next redraw | Memory keeps the feeling of it, not the layout |
| The order or transaction number | Kept in the account history and can be pulled up later | Recoverable — you just spend the first reply looking for it |
| Balance and equity as they stood | Kept in the history as of that moment | Recoverable from your own statements |
| What you had clicked immediately before | Only in your head, and it fades within the hour | The one detail nobody can reconstruct for you |
One habit keeps the rest usable: write the time down as the platform showed it, and note that it came from the platform clock. Two clocks turn one event into two.
A record and a retelling are different documents
Every support case is eventually read as a document. If you wrote things down while they were happening, that document can be laid alongside the account history and the two either agree or they do not. If you did not, the document is a retelling: a summary written afterwards, from memory, by someone who was surprised at the time.
A retelling can only be checked against itself. That is its whole weakness. Nobody has to doubt a word of it for it to be useless — there is simply nothing on the other side to line it up with, so the conversation turns into clarifying questions about details that were on your screen an hour ago and are not anywhere now.
The fix is small and has to happen early. Thirty seconds of recording at the moment removes an entire round of correspondence later, and it removes it from the beginning of the case rather than the end.
Which clock the time came from
A time on its own is half a fact. The same event carries one time on the platform, another on your phone and possibly a third in your own note, and none of them is wrong — they are just different clocks. Written down without saying which clock it came from, a precise time becomes a precise guess.
So record the reading and its source together, in the same line. It costs three extra words and it is the difference between a timestamp that can be matched and one that has to be argued about.
The screenshot is the cheapest of the four
A picture of the screen carries the wording, the reading on the clock and the state of everything around it in one action, before you have decided which of those will turn out to matter. That last part is the real value: at the moment something goes wrong you do not yet know what the important detail is going to be.
It also survives you being wrong. People misremember which button they pressed and which number they read far more often than they expect, and a picture taken before the re-reading is the only version of events that was not edited by hindsight.
Take it first, before you re-read, before you retry, before you close the window. Everything else on this page can be reconstructed from a good screenshot; nothing on it can be reconstructed from a closed one.
What your history keeps without any help from you
Executed operations leave their own trail: numbers, amounts and the times they were recorded stay in the account history and can be pulled up long afterwards. That is exactly why they are not the ones to spend attention on in the moment.
Spend it on the perishable half instead. Whatever way you reach support, the parts of your message that cannot be rebuilt later are the parts worth writing down first.
The half minute after something goes wrong
- Take the picture first — before you re-read it, before you click anything, before you switch windows.
- Write the time as it stands on the platform clock, and write that it is the platform clock.
- Copy the message as text if the text can be selected; a picture plus the exact words beats either one alone.
- Note the order or transaction number if one is on the screen in front of you.
- Add one line about what you had just done. The click before the message is the part nobody else can reconstruct.
- Only then re-read, retry, or close the window.
In that order the whole thing takes less time than composing the first sentence of the message you were about to send.