Hi there Christin Joseph
Thanks for using QandA platform
when you send a message with channelData, Direct Line will forward it to the bot, but when the bot (or the connector) echoes the message back, it rebuilds the activity and doesn’t retain the original custom payload. This is why you’re seeing empty objects in channeltype, customercontext, and conversationcontext.
To work around this:
You can manually include the required channelData in the bot’s reply activity (before calling turnContext.sendActivity() or equivalent).
Alternatively, store the context data in conversation state or user state so your bot can rehydrate and pass it along when needed.
For Omnichannel integration, make sure your adapter (or middleware) explicitly transfers channelData fields to Dynamics instead of relying on the echo activity.
So yes — this is expected behavior from Direct Line, not an error on your side, but it does mean you’ll need to explicitly preserve and resend the channelData from within the bot logic.
If this helps kindly accept the answer thanks much.