|
Notice: This page contains information for the legacy Phidget21 Library. Phidget21 is out of support. Bugfixes may be considered on a case by case basis. Phidget21 does not support VINT Phidgets, or new USB Phidgets released after 2020. We maintain a selection of legacy devices for sale that are supported in Phidget21. We recommend that new projects be developed against the Phidget22 Library.
|
|
button in the menu bar to go to the Phidget22 version of this page.
Contact Us: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Contact Us== | |||
Need technical support? We are here to help. | |||
Give us a call, or send us an email. | |||
If you're looking for a solution ''right now'', though, check out our documentation. See, we're lucky to be a small company. So, we're ''not'' saying read our documentation because we're trying to push you through some 'knowledge base' before even talking to you. | |||
Not at all. Quite the contrary. Instead, we want our documentation to be ''so good'' that when you have a burning question when you are coding away with empty coffee cups and the clock reading 1:00 am, you can find the answer right then and there, on our web site. | |||
We know you're the type of person who doesn't need to sit through basic website help, you want to know how to wire something, where the API is, how to limit ground loops, or how to build cool projects. So every week - yes, every single week - we sit down and discuss every technical support request that comes through. And we ask ourselves: how can we make our documentation better for our customers? | |||
Got an idea how? Let us know. | |||
{{SERVER}}/images/other/ContactUs.png | {{SERVER}}/images/other/ContactUs.png | ||
Revision as of 19:22, 27 June 2012
Contact Us
Need technical support? We are here to help.
Give us a call, or send us an email.
If you're looking for a solution right now, though, check out our documentation. See, we're lucky to be a small company. So, we're not saying read our documentation because we're trying to push you through some 'knowledge base' before even talking to you.
Not at all. Quite the contrary. Instead, we want our documentation to be so good that when you have a burning question when you are coding away with empty coffee cups and the clock reading 1:00 am, you can find the answer right then and there, on our web site.
We know you're the type of person who doesn't need to sit through basic website help, you want to know how to wire something, where the API is, how to limit ground loops, or how to build cool projects. So every week - yes, every single week - we sit down and discuss every technical support request that comes through. And we ask ourselves: how can we make our documentation better for our customers?
Got an idea how? Let us know.
