Industry Insights
New Research: Utility Customers Wanting More Communication, Smarter Thermostats
July 31, 2015
This blog was originally posted on Comverge.com. Itron acquired Comverge on June 1, 2017, and all future demand response blogs will be posted here.
Earlier this month, J.D. Power released its 2015 Electric Utility Residential Customer Satisfaction Study-the 17th annual edition. This year's report includes great news for utilities, and not just for our client Southern Maryland Electric Cooperative, which ranked highest among eastern midsize utilities in customer satisfaction for the eighth year in a row. Overall customer satisfaction with residential electric utility companies has improved for the third consecutive year of the study, even as the average monthly bill remains unchanged. Satisfaction currently averages 668 out of 1,000 on J.D. Power's scale, up 21 points from 2014.
Utilities have a lot to be proud of. Still, there are clear areas for improvement-for instance, communication and engagement. Says Andrew Heath, Senior Director of Energy at J.D. Power, "We have preference questions we ask: 'How frequently would you like to hear from your utility?' Even the best performers in terms of communication volume, those best performers are still well short of what customers want." In fact, customers want as much as twice the amount of communication they're currently getting.
Just because customers don't feel communicated with doesn't mean utilities aren't trying. Proactive communications from a utility, such as phone calls, emails, and text messages, are only reaching 7.3% of customers, according to the report. A number this low suggests a disconnect, potentially in the channels that utilities are using. User-friendly mobile applications that are linked to a customer's smart thermostat allow for remote temperature adjustments, and offer personalized, actionable, and relevant energy savings tips and push notifications that can help keep customers continually engaged and more easily reachable by their utility. These features also pave the way for successful integrated demand response and energy efficiency programs that have been proven to deliver impressive cost-effectiveness results for the utilities that implement them.
Using smart thermostats as the touchpoint to connect with customers and make their energy interactions more meaningful can have a lot of upside for utilities today. By the end of this year, nearly half of all thermostats sold will be connected two-way smart thermostats, according to new research from Parks Associates, and the way in which customers are obtaining them is evolving. Increasingly, customers are turning to retail stores and the HVAC channel, showing proactive interest in adding smart thermostats to their homes. To maintain their role as a trusted energy advisor to their customers, utilities can leverage these third-party smart thermostats for bring your own device (BYOD) demand response programs, which provide value-added services to these customers but do involve new complexities.
By taking steps forward, such as integrated demand response/energy efficiency programs, smart thermostat offerings, or even BYOD programs, utilities can help ensure that 2016 is another year of improvement for customer satisfaction.
Earlier this month, J.D. Power released its 2015 Electric Utility Residential Customer Satisfaction Study-the 17th annual edition. This year's report includes great news for utilities, and not just for our client Southern Maryland Electric Cooperative, which ranked highest among eastern midsize utilities in customer satisfaction for the eighth year in a row. Overall customer satisfaction with residential electric utility companies has improved for the third consecutive year of the study, even as the average monthly bill remains unchanged. Satisfaction currently averages 668 out of 1,000 on J.D. Power's scale, up 21 points from 2014.
Utilities have a lot to be proud of. Still, there are clear areas for improvement-for instance, communication and engagement. Says Andrew Heath, Senior Director of Energy at J.D. Power, "We have preference questions we ask: 'How frequently would you like to hear from your utility?' Even the best performers in terms of communication volume, those best performers are still well short of what customers want." In fact, customers want as much as twice the amount of communication they're currently getting.
Just because customers don't feel communicated with doesn't mean utilities aren't trying. Proactive communications from a utility, such as phone calls, emails, and text messages, are only reaching 7.3% of customers, according to the report. A number this low suggests a disconnect, potentially in the channels that utilities are using. User-friendly mobile applications that are linked to a customer's smart thermostat allow for remote temperature adjustments, and offer personalized, actionable, and relevant energy savings tips and push notifications that can help keep customers continually engaged and more easily reachable by their utility. These features also pave the way for successful integrated demand response and energy efficiency programs that have been proven to deliver impressive cost-effectiveness results for the utilities that implement them.
Using smart thermostats as the touchpoint to connect with customers and make their energy interactions more meaningful can have a lot of upside for utilities today. By the end of this year, nearly half of all thermostats sold will be connected two-way smart thermostats, according to new research from Parks Associates, and the way in which customers are obtaining them is evolving. Increasingly, customers are turning to retail stores and the HVAC channel, showing proactive interest in adding smart thermostats to their homes. To maintain their role as a trusted energy advisor to their customers, utilities can leverage these third-party smart thermostats for bring your own device (BYOD) demand response programs, which provide value-added services to these customers but do involve new complexities.
By taking steps forward, such as integrated demand response/energy efficiency programs, smart thermostat offerings, or even BYOD programs, utilities can help ensure that 2016 is another year of improvement for customer satisfaction.
Wystąpił błąd podczas przetwarzania szablonu.
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>