Skip to main content

Multi-Channel Customer Support


Customer service automation is evolving rapidly, and I experienced this myself this week.  Here is an example of excellent use of multi-channel customer service from SiriusXM Satellite radio.  The entire transaction went smoothly even though it switched between four channels.

Channel 1: Mail

I received a letter telling me that my SiriusXM Satellite Radio subscription was up for renewal, and my credit card would be charged for another year.  I no longer owned the car associated with the subscription and had forgotten to cancel it.  

I called the phone number on the letter.  My phone number was associated with the account and used to look up my account information.  I was told that to avoid a wait for a customer service rep I could switch to text message (SMS) support.  SiriusXM sent a text to my phone number.

Channel 2: SMS Text Message

The text message told me it was from SiriusXM and asked me to confirm my account number and vehicle information.  I was cautioned not to enter this in the text chat, but directed to a web page with a link.

Channel 3: Web

The link took me to a page on which I entered my account information.  After I submitted the form I was notified that the lookup was successful and directed back to the text message chat.

Back to Channel 2

I received a text confirming the account lookup.  Two questions later, my cancellation was complete and I received a final confirmation message and invitation to complete a satisfaction survey.

My company InfoStrat helps customers implement CRM and customer service, so it was interesting for me to experience automation as the end user, especially when the result was a smooth transaction that likely was faster and more painless than I would have experienced just using a phone call or the website as a single channel.  Having options to choose and switch channels is another way to empower customers and raise customer satisfaction. 


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan