It seems to make a little more sense reindented:

O{ bTyp | S{WCS-STD} bUsr | S{Paul R Dunaway} bUid | S{1350} sCmd | S{} sId | A{} sNme | S{} sUrl | S{} sLbl | S{} sCok | S{} mMsg | S{All Other Software} fAct | S{} fTyp | S{} fKey | S{} fVal | S{} bUserType | S{CUST} transType | S{} mTsp | S{2012-01-26 15:03:04} } | O{ bTyp | S{WCS-STD} bUsr | S{system} bUid | I{-1} sCmd | S{} sId | A{} sNme | S{} sUrl | S{} sLbl | S{} sCok | S{} mMsg | S{[An agent will be with you shortly.]} fAct | S{} fTyp | S{} fKey | S{} fVal | S{} bUserType | S{SYSTEM} transType | S{} mTsp | S{2012-01-26 15:03:04} }

(Please excuse me if I'm just restating the obvious.) This doesn't look like any form of serialization I've seen before; I don't think it's outside the realm of possibility to think it's proprietary. Values, contained within braces, can be of one of four data types, indicated by the character immediately preceding the opening brace: S for string, I for integer, O for object (a collection of values as named properties), or A , presumably for array. Object properties are named based on the string preceding the value and separated from it with a pipe character.

Some questions still remain: