Ok, so here’s my interpretation…
Client A 192.168.1.1 -> WAN1 184.108.40.206 -> Internet -> FusionHub 220.127.116.11 -> Client B 18.104.22.168
Client A 192.168.1.1 -> WAN2 22.214.171.124 -> Internet -> FusionHub 126.96.36.199 -> Client B 188.8.131.52
Ok so if you don’t bond these, but rather place them in priority WAN1 then WAN2… Not bonded, just failover… The beauty here is that Client B thinks he is talking to 184.108.40.206, so when the IP changes from 220.127.116.11 to 18.104.22.168 upon failover, the client doesn’t know the IP changed, FusionHub handles that. This is what they are calling Hot Failover. If you were talking to client B from 22.214.171.124 instead of 126.96.36.199 and then changed to 188.8.131.52 the client would not be happy and would take probably close to a minute to re-connect and your customers would definitely notice.
Now add bonding on top of what I just said instead of straight failover and I think that explains it. The tech they are branding here is that IP changes are hidden from Client B due to FusionHub 184.108.40.206.