IB Customer Service is Poor

Quote from stockgirl:

IB you need to get it together, I've sent in tickets that never get answered and if they do sometimes it's weeks later. Today, your export utility for Monthly Statements DOES NOT export in EXCEL format or anything else besides HTML - Try selecting a different format and all you get HTML - So I call your customer service and let them know - they say there gone for the day, call back later, SAY What! I'm not your freaking IT department - How ABOUT YOU get up off your a$$ and YOU NOTIFY your own damn IT department! I DON"T WORK FOR YOU!!! YOU WORK FOR ME!!!

What a loser you are. Business is a two way operation. They are not slaves to you. They provide a low cost operation that does work almost all the time vert very very well in my experience. You pay them for that. They are not going to fix your crap out of hours.
 
Quote from nonam:

True story.
Question to IB."Can I buy pk stocks in my margin account?"
IB reply."Contact our trade desk for help selling your pk stocks".

High quality services indeed. LOL.
 
Quote from IBj:

It would be great if we could leave the name calling and other irrelevent posts in the playground sandbox.

I assume the thread started for a real reason. I am interested in the problem posed by the thread subject and not by who has the most 'colorful' vocabulary. IB contribution is intended to inform and learn from our clients and other intelligent commentators. Why would anyone want to be in the middle of a name calling exercise which helps nobody and, aside from some mild amusement factor, serves no purpose.
Fine, but I find it interesting, insulting, and telling that an IB employee would quote me instead of quoting the colorful, compulsive, and obscene kiwi_trader, the one who started all of this distraction in the first place. Better still, why did you feel the need to quote anyone at all. I think what you just did was unprofessional.
 
Suggestion: don't send email. Aside from the fact that it is being desupported in a few weeks, it is the lowest priority for us. Use the web ticket system. I hear some complaints in this thread about these 'disappearing'. Look on the 'Inactive' tab. Try logging in to acct mgmt again. If there really is a problem, PM me because so far we have never seen a case of true disappearance. BTW, the web ticket system is the only system we are investing effort in.

I'm afraid you are not correct.
Like other IB reps, you may simply not realise how exactly the ticket system works.

The ticket system would be great if the policy is to keep our tickets at least for a while (like at least a month), or the ticket sytem is simply not credible.

Recently I have written suggestions/bugs/problems each by each. Suddenly one of the tickets disappeared on one day. That's the ominous sign. After that day, my tickets kept disappearing one after one until only one is left.

Originally I supposed it must be a bug. Someone promised to look into the issue. However it turned out to be another guy who got the responses.

Here's the official reply from mattm:
============================================
Inactive tickets are not visible for an unlimited period of time. The more tickets that are submitted for an account, the less history is visible.

Per previous requests to condense questions / requests regarding similar issues to a single ticket please close this ticket.

There are currently a number of open inquiries for this and the other account. We would greatly appreciate your condensing these inquiries to as few tickets as possible. Submitting multiple tickets regarding similar issues requires that multiple reps are investigating multiple different inquiries all related to the same trader.

The web ticket system is provided as a service to our customers. Should this service be abused or should the number of submitted tickets cause inefficiencies in the customer support group, these tickets may be forcefully closed without allowing the ability to re-open them.

We appreciate your understanding and cooperation with this issue.

Please do not reply to this.
Please confirm close this ticket.
============================================

That's the only ticket left.

This suggests IB reps will forcefully close your tickets at their discretion and without any prior notice or warning. After closing they will simly delete them out of the system, so you have no chance to re-open or read them back.

I don't think it is commonly knwon among IB reps. Otherwise the first guy who take in charge of my inquiry would know the answer.

This may justify why cscott and a few posters regard the ticket system as inefficient or "doesn't work". At least IB staff cannot arbitrarily delete all correspondences in your mailbox.

Here's the summary about the ticket system:
(1) If I observe/find quite a few bugs in TWS (eg: booktrader, charttrader), but the bugs are not related to each other, should I submit all bugs as one big ticket? I'm afraid the answer is yes. Personally I don't think it is going to be communication-efficient. It is hard to follow when someone submitting over several ten bugs in one ticket , isn't it? It is going to be more than twenty pages (I file a detailed bug report. That's why it has such a length) and a lot of attachments (images, documents etc.) No one is going to read such a lengthy bug report.
(2) How long will an inactive ticket be kept? It seems to be less than a few days in my experience. Don't you think it is too short? It doesn't give you enough time to review the closed ticket
(3) not to say most tickets, if not closed by you, will be deleted straight away, without being placed in the inactive ticket panel at all. Thus you should backup your inquiries or tickets before IB deleted yours.
(4) If I submit bugs and suggestions which are not to IB liking or IB couldn't answer, IB may simply delete them without prior notice. They will not explain why. That's my experience: I got a few tickets which have been assigned to several reps. The tickets are deleted after a week or so without hearing any reply (The only type of reply is "we have read your ticket. A response will be made shortly").
(5) As far as I know, it appears if you have more than 9 open tickets, you will be regarded as abusing the ticket system. Odd enough, instead of reducing the no. of tickets to 9, IB would take further actions to kill all your open tickets. Why? I don't get it.

Sorry to say, but I do feel the rules and procedures of the ticket system is a bit unreasonable. On one hand, IB promotes the use of ticket system. On the other hand, all these rules make the ticket system less efficient and less credible way to communicate with IB reps.
 
I will insert comments in blue
Quote from DirectTrader:

I'm afraid you are not correct. Like other IB reps, you may simply not realise how exactly the ticket system works.
'Like other reps' does not apply here, sorry. I designed the entire Customer Service technology package. I know exactly how it works.

The ticket system would be great if the policy is to keep our tickets at least for a while (like at least a month), or the ticket sytem is simply not credible.
Tickets remain accessible to the ticket system for 30 days at least

Recently I have written suggestions/bugs/problems each by each. Suddenly one of the tickets disappeared on one day. That's the ominous sign. After that day, my tickets kept disappearing one after one until only one is left.
If the tickets exceeded the 30 day limit, that might explain it. Or perhaps the tickets were closed and moved over to the 'Inactive' tab. More on closure below.

Originally I supposed it must be a bug. Someone promised to look into the issue. However it turned out to be another guy who got the responses.
don't understand. What do you mean 'someone else got the responses'.

Here's the official reply from mattm:
============================================

============================================

That's the only ticket left.

This suggests IB reps will forcefully close your tickets at their discretion and without any prior notice or warning. After closing they will simly delete them out of the system, so you have no chance to re-open or read them back.
Initially, the design relied on clients closing tickets when they were satisfied. It turns out that people weren't closing tickets and this was creating a clutter of theoretically open issues on the internal interfaces. The clutter in turn made it hard to identiofy new issues.

So we instituted a cleanup of old items and closed them ourselves. In the meantime, we added a dual closure algorithm which allows us to keep our side clean but leaves cotrol with the client. It works as follows.
if CSR thinks the issue/question has been answered/resolved, he/she is permitted to close it. This does not set a true closed state (CLS), but rather a Pending Closed state (visible to the client as PCLS). Pending closed tickets drop from the active view of the CSR.
However, on the client side, the following happens: if the ticket is replied or added to by the client, it is automatically re-opened and becomes again visible in the 'In Progress' view internally. If the ticket is ignored or otherwise not touched by the client for 7 days, IB presumes the client is satisfied and a program will automatically run and set the full closure state.


Closed tickets can be reopened for up to 7 days. We don't allow indefinite re-opening because clients were re-using an existing ticket to ask an unrelated question, which prevents us from routing tickets to the right team. For example, clients would ask a trade desk question and then later ask a funding question. These service teams are fully disjoint but the recycling of the old ticket made it hard to route the funding question properly.

One of the biggest hurdles we have had in developing this system is anticipating clients use (or misuse). Deisgn elements that I, as architect, presumed would be the best for the workflow, prove problematic when people do things like reuse old tickets for new questions. I dont know why they do; I wouldn't were I a user; but it is this way and I don't think retraining clients is productive or realistic.


I don't think it is commonly knwon among IB reps. Otherwise the first guy who take in charge of my inquiry would know the answer.
The ticket system was designed to allow the CSRs to concentrate on the question, not on the technology of the delivery method. I am sure most CSRs don't know the inner workings. Just like most people don't know how an automobile transmission works. As long as it IS working, nobody cares how.

This may justify why cscott and a few posters regard the ticket system as inefficient or "doesn't work". At least IB staff cannot arbitrarily delete all correspondences in your mailbox.

Here's the summary about the ticket system:
(1) If I observe/find quite a few bugs in TWS (eg: booktrader, charttrader), but the bugs are not related to each other, should I submit all bugs as one big ticket? I'm afraid the answer is yes. Personally I don't think it is going to be communication-efficient. It is hard to follow when someone submitting over several ten bugs in one ticket , isn't it? It is going to be more than twenty pages (I file a detailed bug report. That's why it has such a length) and a lot of attachments (images, documents etc.) No one is going to read such a lengthy bug report.
(2) How long will an inactive ticket be kept? It seems to be less than a few days in my experience. Don't you think it is too short? It doesn't give you enough time to review the closed ticket
30 days, minimum. We are working on a facility to access older tickets. The issue is resources. Why transmit 12 months of tickets for 100'000 clients when few people care about more than the last few weeks.
(3) not to say most tickets, if not closed by you, will be deleted straight away, without being placed in the inactive ticket panel at all. Thus you should backup your inquiries or tickets before IB deleted yours.please email me via E-T if you see this happening. This is not the design and if it is happening, it is a bug which we wil fix
(4) If I submit bugs and suggestions which are not to IB liking or IB couldn't answer, IB may simply delete them without prior notice. They will not explain why. That's my experience: I got a few tickets which have been assigned to several reps. The tickets are deleted after a week or so without hearing any reply (The only type of reply is "we have read your ticket. A response will be made shortly").
If the inquiry was related to a problem you actually experienced that needed correcting, then please give me an example by E-T email. We can only fix a problem if we can find a specific case to test.

Bug reports get entered into a defect tracking systm which feeds into the development department. As bug fixes, and suggestions, can be 1 hour to forever, there really isnt a response method. We fix bugs depending on thier priority but there isn't really a great way to inform clients about when that happens.

Please enter suggestions into our new features voting system. That is the best way to get your ideas to the programming queue.

(5) As far as I know, it appears if you have more than 9 open tickets, you will be regarded as abusing the ticket system. Odd enough, instead of reducing the no. of tickets to 9, IB would take further actions to kill all your open tickets. Why? I don't get it.There is no "MaxTicket algorithm". That incorrect assumption is leading to false conclusions I think.

Sorry to say, but I do feel the rules and procedures of the ticket system is a bit unreasonable. On one hand, IB promotes the use of ticket system. On the other hand, all these rules make the ticket system less efficient and less credible way to communicate with IB reps.
Last comment:
Much has changed in the Web ticket interface over the last 2-3 months. If you have not used it recently, your experiences and opinions may be outdated. As with every aspect of IB's business model, we release systems, constantly work on them and improve them, and we listen to constuctive commentary. That is as true with service technology as with the brokerage system technology.
IBJ
 
Quote from cscott:

Fine, but I find it interesting, insulting, and telling that an IB employee would quote me instead of quoting the colorful, compulsive, and obscene kiwi_trader, the one who started all of this distraction in the first place. Better still, why did you feel the need to quote anyone at all. I think what you just did was unprofessional.

Might have something to do with the level of constructive criticism and contribution Kiwi has offered versus...

OR it could have been a random event.

Anyway, we're all guilty. It's not as if anyone looked at IBJ's post with you quoted in it and said, "Schwooo! Glad I'm not that guy." I read it an said, "yep. True. Guilty as charged. But at least I know IBJ was mildly entertained by some of it."

:)
 
IBj,

Sometimes a CS rep mishandles an issue, and refuses to allow it to be escalated to higher authority. Sometimes problems just don't get addressed through the system. Sometimes the trouble ticket system itself seems to malfunction. These situations require some sort of backup communications channel outside of the trouble ticket system. You have posted that in such situations, people can send private messages to you via EliteTrader.

Have you considered that people might not be willing or able to communicate through such a channel? Many IB customers don't read ET or have an ET membership, so that they won't have any way to proceed or to communicate in such situations, and will instead come up flat against a brick wall, without even knowing that the ET option exists. Others may have access to ET, but not want to use it for account management purposes, because of concerns over privacy and security. Did you know that ET moderators have unlimited and unrestricted access to read all private messages sent over ET? I'm not faulting ET, and I think that your participation in the public ET forums is a wonderful thing that should definitely continue, but I think that ET's private message system should not be used in order to address issues with individual customer accounts.

I think that you need to give further thought to what happens when the trouble ticket system fails, due to machine problems or to human error, and then some sort of backup system is needed. EliteTrader PM is not, in my view, an adequate backup system.
 
It would be great if you could place your reply outside the quote next time. It is because the system will cut off the whole quoted messages when I press the "quote" button to reply your message. Thank you!

Here's my reply.

Quote from IBj:
---------------------------------------------------------------------------------------------------------
'Like other reps' does not apply here, sorry. I designed the entire Customer Service technology package. I know exactly how it works.
---------------------------------------------------------------------------------------------------------
Sorry, I don't realize that.

Quote from IBj:
---------------------------------------------------------------------------------------------------------
Tickets remain accessible to the ticket system for 30 days at least
---------------------------------------------------------------------------------------------------------
Does it apply to all types of tickets?

It is okay to keep inactive/closed tickets for 30 days at least.

However it is not alright for open tickets. Sometimes open tickets are not answered for more than 30 days. The open ticket should only be closed after it is resolved. It is silly to delete it simply because the time is up.

If your IB rep thinks the user may have abandoned the ticket, they should issue a PCLS first (in lieu of deleting the ticket instantly). If the user doesn't respond without 7 days, the ticket will be closed and placed in the "inactive" tab first (but not trashing it instantly), or the "re-open" option is rather pointless.

But it shouldn't apply when there is no meaningful response. Responses like "we will get back to you soon" are not really answers and shouldn't be closed even if I do not reply. What do you expect me to reply for these kinds of responses?


Quote from IBj:
---------------------------------------------------------------------------------------------------------
If the tickets exceeded the 30 day limit, that might explain it. Or perhaps the tickets were closed and moved over to the 'Inactive' tab. More on closure below.
---------------------------------------------------------------------------------------------------------
No. They are simply deleted.
I couldn't see them even in the "inactive" tab, no matter how many times I login. I have tried in different computers. I have cleared cookies and temporary Internet files. This should prove the case.

If memory serves, the open tickets are just between 1 to 2 week old.



Quote from IBj:
---------------------------------------------------------------------------------------------------------
don't understand. What do you mean 'someone else got the responses'.
---------------------------------------------------------------------------------------------------------
Sorry for the confusion.

Let's say the ticket was assigned to def. He promised to look into the issue. However it turned out to be IBj who answered my inquiry.

Do you get it now?
 
Quote from IBj:
---------------------------------------------------------------------------------------------------------
Initially, the design relied on clients closing tickets when they were satisfied. It turns out that people weren't closing tickets and this was creating a clutter of theoretically open issues on the internal interfaces. The clutter in turn made it hard to identiofy new issues.

So we instituted a cleanup of old items and closed them ourselves. In the meantime, we added a dual closure algorithm which allows us to keep our side clean but leaves cotrol with the client. It works as follows.
if CSR thinks the issue/question has been answered/resolved, he/she is permitted to close it. This does not set a true closed state (CLS), but rather a Pending Closed state (visible to the client as PCLS). Pending closed tickets drop from the active view of the CSR.
However, on the client side, the following happens: if the ticket is replied or added to by the client, it is automatically re-opened and becomes again visible in the 'In Progress' view internally. If the ticket is ignored or otherwise not touched by the client for 7 days, IB presumes the client is satisfied and a program will automatically run and set the full closure state.
---------------------------------------------------------------------------------------------------------
No, it is incorrect.
As said by mattm, they may forcefully close clients' tickets at their discretion without allowing the ability to re-open them. When it is deleted, it is not viewable in the "inactive" tab. The tickets are simply gone.

Please re-read the following official reply from mattm:
---------------------------------------------------------------------------------------------------------
The web ticket system is provided as a service to our customers. Should this service be abused or should the number of submitted tickets cause inefficiencies in the customer support group, these tickets may be forcefully closed without allowing the ability to re-open them.
---------------------------------------------------------------------------------------------------------



Quote from IBj:
---------------------------------------------------------------------------------------------------------
Closed tickets can be reopened for up to 7 days. We don't allow indefinite re-opening because clients were re-using an existing ticket to ask an unrelated question, which prevents us from routing tickets to the right team. For example, clients would ask a trade desk question and then later ask a funding question. These service teams are fully disjoint but the recycling of the old ticket made it hard to route the funding question properly.
---------------------------------------------------------------------------------------------------------
Yes, this is reasonable. However it would not be the case when IB forcefully deletes the ticket.


Quote from IBj:
---------------------------------------------------------------------------------------------------------
One of the biggest hurdles we have had in developing this system is anticipating clients use (or misuse). Deisgn elements that I, as architect, presumed would be the best for the workflow, prove problematic when people do things like reuse old tickets for new questions. I dont know why they do; I wouldn't were I a user; but it is this way and I don't think retraining clients is productive or realistic.
---------------------------------------------------------------------------------------------------------
It is because your staff still promotes such kind of workflow.

Let's talk about my case. When I deal with bug tracking and reporting system, it is normal to contain one bug per issue. I do so by sending one bug per ticket. Also when I have questions, say, there are 3 questions. The first one is about hotkeys. The second one is particularly for booktrader. The third one is sending and modifying orders. Instead of lumping all questions together as a ticket, I send each question per ticket.

Nevertheless I am accused of abusing the ticket system and ask me to lump the questions and bugs together as one ticket. I do so by closing other tickets and re-send them by replying them in the first ticket.



Quote from IBj:
---------------------------------------------------------------------------------------------------------
If the inquiry was related to a problem you actually experienced that needed correcting, then please give me an example by E-T email. We can only fix a problem if we can find a specific case to test.

Bug reports get entered into a defect tracking system which feeds into the development department. As bug fixes, and suggestions, can be 1 hour to forever, there really isnt a response method. We fix bugs depending on their priority but there isn't really a great way to inform clients about when that happens.

Please enter suggestions into our new features voting system. That is the best way to get your ideas to the programming queue.
---------------------------------------------------------------------------------------------------------
What's the best way to report possible bugs?
Should I send via poll system or ticket system?

I ask this question because your staff, mattm, seems to suggest me to file bug report in poll system.
I have filed a bug report. Then mattm replied me as follows:
---------------------------------------------------------------------------------------------------------
This setting cannot currently be adjusted in the TWS.

One of the advantages of being an IB customer is that we listen to our professional customers as we continue our never ending quest to lead the industry with the most advanced trading technology. In order to systematize your requests we are adding a new permanent feature poll that allows you to suggest new TWS enhancements and to have other customers vote on the enhancements. We will do our best to prioritize those requests with the most number of votes. To nominate requests and to vote, visit our new TWS Voters Poll page, to learn how to sign up for a Voter ID and password in order to add your voice to our programming queue.

www.interactivebrokers.com/en/general/poll/poll.php?ib_entity=llc
---------------------------------------------------------------------------------------------------------
I don't understand why he calls it "setting", but he copied this reply for a bug report. What does it imply? Should a bug go to the poll system? I'm confused.

After all, I would suggest a bug tracking and reporting system like https://bugzilla.mozilla.org/ (the software is called bugzilla http://www.bugzilla.org/ ).

Reasons:
- I found many bugs in TWS. It would be crazy to lump all bugs together as one ticket.
- other people can view the bugs
- Reduce bug duplication: when people see the bug, they would not sending the same bug over and over again
- search the bugs
- easy to keep track on the bugs



Quote from IBj:
---------------------------------------------------------------------------------------------------------
There is no "MaxTicket algorithm". That incorrect assumption is leading to false conclusions I think.
---------------------------------------------------------------------------------------------------------
Only 9(?) tickets can be displayed. You can issue more tickets, but the older ticket will be pumped out of the system. What's more, I am accused of abusing the ticket system because I sent too many tickets (as I have about 9 tickets opened at one time).

Please see the following official reply from mattm:
---------------------------------------------------------------------------------------------------------
Should this service be abused or should the number of submitted tickets cause inefficiencies in the customer support group, these tickets may be forcefully closed without allowing the ability to re-open them.
---------------------------------------------------------------------------------------------------------


Quote from IBj:
---------------------------------------------------------------------------------------------------------
Last comment:
Much has changed in the Web ticket interface over the last 2-3 months. If you have not used it recently, your experiences and opinions may be outdated. As with every aspect of IB's business model, we release systems, constantly work on them and improve them, and we listen to constructive commentary. That is as true with service technology as with the brokerage system technology.
---------------------------------------------------------------------------------------------------------
This incident happened in less than a month.
I have PM you, so you can follow up the issue.
Thanks for your help in advance.
 
Back
Top