IoT for #AwesomeAdmins – Dreamforce ’16 Sneak Peek

Dreamforce is right around the corner and the HeyWire team is getting ready for another exciting and eventful conference! (Plus, who isn’t excited for U2?) Meanwhile, this year, I was lucky enough to get selected to speak during the Admin Track, which is definitely an honor since only 60 sessions were accepted out of the 867 submissions!!

My topic this year: IoT (Internet of Things) for Admins

It’s all about being connected.

IoT is all about being connected. Whether it’s you having a thermostat that allows you to control the temperature in your home while on the go, or a field service company tracking their commercial vehicles and drivers to send and receive notifications regarding appointment progress, mileage and delivery or service confirmation. At the end of the day, it’s all the same:  the impetus behind connecting these people, places and things is to provide manufactures, brands, customers – and everything in between – a better, more convenient way to get something done.

Well, the same is true for your Salesforce instance.

You can’t just purchase a Salesforce license and be up and running in a couple days; that just doesn’t happen and that’s not the way Salesforce is built. Think of Salesforce as the hub – or better, warehouse – for storing and distributing data. Getting that data into the system is the ongoing key business objective – to determine what that data is and where it is coming from, which is all dependent on that company’s needs.

Start where you want to end.

In the IoT space, companies are investing in connecting technology with products so that they can get something out of it – e.g. the connected thermostat so that consumers can easily, from anywhere, adjust the temperature of their home.  So, now think of your Salesforce instance: you likely purchased it because you are looking to get something out of it – e.g. more data, stronger reports, etc. Right?

Thus, in order to ensure you are getting the end result you’d like, data from outside must be entered into that system, i.e. inputs. An input is anything that is entered into Salesforce, and can be thought of as one of two types, a digital or analog input.

Digital input: This is an input that is essentially black or white. For example, when you turn a light on, it’s on; when you turn a light off, it’s off. There is no in-between with this input; it’s binary – which is also to say, digital. An example of this in Salesforce could be an account name that you report on each month. The company name for that account is either right or wrong, it will not change.

Analog input: An analog input, on the other hand, can be in the grey zone. Example, a light in the room is too bright, but you don’t want to turn it off, so you use the dimmer to take it down a few notches. An example of this in Salesforce may be a checkbox field.

End where you want to start.

Back to the thermostat example, you get home and the temperature is where you want it to be – awesome! But that wouldn’t have happened unless, on your way home, you input that temperature. That end result is the output.

In Salesforce, the reports (outputs in this case) you want to run are only as good as the data entered (the inputs). For example, if you are looking to get a very detailed lead report but forget to input the contacts name field into that report, chances are that your output – the report – won’t be what you were hoping for.

Let’s dig deeper. This is just a sneak peek of what you can expect from my session at DF16, taking place on Tuesday, October 4th from 5:00-6:00pm in 2007 Moscone West – I hope to see you there! Meanwhile, be sure to stop by HeyWire’s booth #2037 if you would like to chat with me more about connecting your Salesforce instance, specifically with HeyWire’s LiveText messaging channel!