Social and custom messaging channels

What it does

The social channels bring Facebook Messenger, WhatsApp, LINE and Microsoft Teams conversations into the same routed inbox as chat and SMS. Where the platform your client uses isn't on the list, a custom messaging channel does the same job over the Azure Bot Service Direct Line connection.

Key facts

First-party social channels in Customer Service: Facebook, WhatsApp, LINE, Apple Messages for Business and Microsoft Teams. Apple Messages for Business is deprecated — do not design new work onto it.
All of them are asynchronous except Teams, which behaves synchronously. Asynchronous channels get auto-close after inactivity and representative affinity by default.
Facebook needs a Facebook Page with Messenger enabled and a Business-type app registered on the Meta developer site. You collect four values: App ID, App Secret, Page ID and Page Access Token.
Facebook's 24-hour messaging window applies. Outside it, a representative cannot respond unless the customer messages again or the Facebook message tag setting is enabled. Representatives can start conversations for up to seven days.
Facebook page access tokens expire, sometimes unpredictably, and Microsoft's guidance is to refresh them on a 60-day cycle. Plan for an owner and a calendar reminder, not a hope.
Required Meta permissions include pages_messaging to send messages and business_asset_user_profile_access to retrieve the customer's username. While the Meta app is in development mode only users with an app role can message it.
Custom messaging channels need an agent built on the Microsoft Bot Framework, registered with Azure Bot Service as a multitenant app. You supply the App ID and client secret, then paste the Dynamics messaging endpoint URL back into the Azure bot channel registration.
Telegram and Kik as prebuilt custom messaging channels were deprecated and removed on 8 October 2024. Telegram is now a build-it-yourself Direct Line job.
All social channels support custom automated messages, post-conversation surveys, configurable file attachments, context variables and smart assist agents, and they all sit on a Messaging workstream like chat does.
Non-Microsoft channels need a separate subscription with that provider, and specific Dynamics licensing applies to SMS, social, Teams and custom messaging on top of the base Customer Service licence.
Social and Direct Line traffic shares the same quota as the rest: 100 incoming conversations per minute, adjustable via support.

When to use / skip

WhatsApp is the one that matters commercially in the UK and Europe — it is where customers already are, and clients ask for it by name. Facebook Messenger is worth doing if the client already runs an active page with an inbox somebody is manually working; you are replacing a person alt-tabbing into Meta Business Suite, which is an easy business case. LINE is worth doing only for Japanese and Thai operations, where it is unavoidable.

Microsoft Teams as a channel is the quiet winner nobody asks for. It is the cleanest way to give an internal IT or HR service desk a front door in the tool their colleagues already have open, and it needs no third-party account at all.

Skip custom messaging channels unless the client genuinely has a proprietary app with an in-product chat. Building a Direct Line integration to reach a platform Microsoft doesn't support is real development work with ongoing maintenance, and clients consistently underestimate it. If the ask is "we want Instagram", the honest answer is that it is not a supported first-party channel and the workaround is a build.

Configuration decisions

Which platforms are actually in scope, and whether the client's marketing team already owns those accounts. They almost always do, and they will not hand over admin rights cheerfully.
Whether the Facebook message tag is enabled, and what your policy is for conversations that go quiet past 24 hours.
Who owns page access token rotation, and where that lives operationally after handover.
Whether attachments are enabled per channel, in which direction, and what happens to the files.
Auto-close window per asynchronous channel — social conversations left open indefinitely make supervisor dashboards useless.
For custom channels: who builds and hosts the bot, and who maintains it after go-live.

Gotchas

Ownership of the social accounts is a political problem, not a technical one. Marketing owns the Facebook page and the WhatsApp Business account; service wants the inbox. Sort this in discovery or it will stall the build.
Expiring Facebook tokens break the channel silently. Messages stop arriving and nothing in Dynamics tells you why. This is the most common social channel production incident.
The Meta app stays in development mode until you take it through review, and while it is there only app-role users can message it. Teams testing with their own accounts think it works, then it doesn't for real customers.
The 24-hour window catches people out. A representative composes a thoughtful reply the next morning and it simply will not send.
Data leaving the tenant to Meta or the channel provider is a data protection conversation. Microsoft's position is that monitoring, recording and consent notices are the customer's responsibility. Get the client's DPO involved early.
Apple Messages for Business is deprecated and Telegram and Kik are already gone. Check the current channel list before you promise anything from a slide deck.

Consultant notes

Get the client's social account admin in the room during the configuration session. Doing it asynchronously over email takes three weeks; doing it live takes forty minutes.
Demo Teams as a channel to any client with an internal service desk. It costs nothing extra to show and it frequently opens a second phase of work.
Set up token expiry monitoring before handover and name the person responsible in the runbook. "Someone will notice" is not a plan.
Be straight about custom channels. Quote them as a development workstream with a support cost, not as a configuration checkbox.
Where a client wants a channel that only Contact Center covers in depth, say so and move on rather than trying to bend a custom channel into the gap.

Worth another look each release wave — the supported social channel list changes more often than anything else in this area.