RIM to WM and back to RIM?
We have a small business (less than 10 employees), but have been using mobile technology since the CDPD days. We were VERY early adopters of RIM devices (857, 957) for two-way communications and access to other, non-wireless applications via special-purpose application gateways - mostly self-hosted.
I moved us off of RIM at the beginning of this year (to Motorola "Q" devices) primarily as part of a move from iDEN to PCS - and the fact that at that moment, RIM was somewhat behind the handset offerings of other vendors with the combination of features we wanted in an integrated phone/email/web/PIM device. Specifically, battery life was atrocious, lack of camera and multi-media were becoming a real issue, and the premium price for the devices was unjustified against the rest of the market.
As mentioned before, we self-host our own gateways, but are primarily a LINUX shop - so no MS Exchange or Exchange clones. That being said, one of the selling features of the Windows Mobile platform was the ability to easily integrate non-proprietary mail and web services - although in actual practice this has proven to be very Microsoft-limited. I have had to get Windows in dual-boot configuration throughout the company in order to support the WM5 platform (SynCE is just a bit too far behind to fully support the "Q", and Motorola does not allow access to updates on their web site from non-IE platforms. At least they now allow access from Vista - THAT was blocked when we first migrated to WM5! Bad Motorola - VERY BAD!!)
I am now considering a move to either the new RIM devices (the Curve) or possibly to a Linux-mobile platform from the WM devices. Yes, WM has proven to be THAT much of a disappointment: slow, unstable, requiring a great degree of user interaction with the platform to keep it operating. (BTW, this is NOT a Motorola issue: the same problems occur on ANY WM5 device we've tested. The "Q" is an excellent device on the phone side - except where a WM "feature" gets involved - then it's a dice roll as to whether the device is going to be there when you need it. 10 minutes and two reboots to dial 911 - real-life experience- is NOT acceptable performance.)
As far as service from carrier - Sprint has provided excellent support in all aspects for us, especially on the data side of the equation. EVDO works - period. Data rates are excellent - not DSL, mind you, but consistent 50-100KBpS even in rural markets - plenty of band width for the uses we have.
To summarize: if your business is built on the Windows mono-culture, you have a variety of choices for integration with your mobile communications, albeit with plenty of work to keep your in-house IT support busy. If you are outside of the Windows environment, you are faced with a much narrower choice of handset technology, although the pieces to support it (POP3 from the device, SSL tunnel, custom web-based apps and device-specific applications) are available. If you MUST use a WM device, thorough vetting by in-house IT is a *MUST*, and customized in-house developed training for using the device is a *NECESSITY*.
Oh, and get Opera on there ASAP. It is a FAR superior browser and web-enablement tool than IE on WM. Worth the cost from Opera, even in a large deployment.