Many routers out there have multi WAN capabilities. From boxed units such as Draytek, or Cisco (Linksys) small business series "RV" models.They all work "OK".
There are some specific brands that specialize in multi WAN routers, such as Peplink ..really products.
And many *nix distros do it, Untangle does it VERY well.
There are pros and cons to multi WAN'ing a network. Failover is one thing...really only makes sense when you use different ISPs. But with load balancing...some routers are just OK with it, and others do much better. Much of it has to do with having the smarts to keep sessions on one particular WAN interface/IP. This is especially true with httpS sessions. If you're in the middle of an httpS session, such as with your bank, and the router switches which WAN port/IP you appear to come from, your httpS session will break and you'll have to log in again. Envision that scenario with all sorts of internet activity and usage. Email clients. Browsers. Various online apps, cloud apps, etc.
Also, don't fall into the trap of thinking that pairing two 6 meg DSL connections results in a 12 meg connection if you do online speed tests. What you get is a network that can handle more internet traffic than a single DSL connection...almost 12 megs worth..but no single session will peak faster than a single WAN connection. (so any online speed test of a pair of balance 6 meg pipes will still only peak at 6 megs)
An equal part of troubleshooting this from a performance perspective, is having a router with a good amount of horsepower, and lots of RAM, that can handle many concurrent sessions. I bet much of your clients issue stems from a router that is not capable of that. You'd be AMAZED at how much better the performance is if you're running behind a very capable firewall such as Untangle...with proper bandwidth management. I have a large accounting office on a single 3 meg bonded T1 line. Untangles bandwidth management can prioritize important traffic, and deprioritize less important traffic.
I bet your clients issue is due to a firewall that cannot do those important things. It's probably overwhelmed with more sessions than its memory and state table can handle, and it doesn't do well at QoS.