![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 85%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGW%3C/text%3E%3C/svg%3E)
The agent is generating responses in Copilot Studio, but they aren’t being delivered back to WhatsApp. This points to an issue in the channel/transport path between Copilot Studio and WhatsApp rather than in the agent logic itself.
From the available information, the following areas are relevant:
- WhatsApp channel behavior and setup
- Copilot Studio uses Azure Communication Services (ACS) to connect the agent to the WhatsApp endpoint (the chat where users interact with the agent).
- After publishing, the agent must be explicitly connected to a specific ACS resource and WhatsApp phone number from the Channels → WhatsApp configuration in Copilot Studio, and the QR code must be used to start chatting from the WhatsApp device.
- If the ACS resource or phone number selected in Copilot Studio doesn’t match the one actually used in WhatsApp, messages can appear in ACS metrics and Copilot Studio analytics but not show up in the WhatsApp client.
- In Copilot Studio, open Channels → WhatsApp for the agent and verify:
- The correct Azure subscription and ACS resource are selected.
- The correct phone number is selected.
- If needed, Disconnect the agent from the current number and Deploy again to the correct number, then scan the new QR code from the WhatsApp device.
- User authentication configuration for WhatsApp
- For WhatsApp, the agent’s authentication must be set to No authentication or Authenticate manually before enabling the channel.
- If authentication is misconfigured, the agent can process messages (and show transcripts/credits) but still not send visible replies to users.
- In Copilot Studio, confirm the agent is configured with either No authentication or Authenticate manually as required for WhatsApp.
- If using phone-number–based checks for WhatsApp, verify that the phone numbers used for testing are in the allowed list; otherwise, the agent can reject users and show only the configured “unregistered” behavior.
- WhatsApp channel limitations and behavior
- The WhatsApp channel has specific behavior differences from synchronous channels (like web or Teams), including how conversations start and how greetings/first messages are handled.
- If the conversation start configuration or greeting logic is misaligned, the agent can appear to respond in analytics but not send messages back to WhatsApp.
- Transport path and policy issues (general pattern)
- In other Copilot Studio channels, unresponsive behavior with valid transcripts is often caused by network or policy blocks on the real-time messaging path (for example,
/subscribeconnections or Conditional Access policies). While the provided documentation describes this for the Test panel and Teams, a similar pattern can apply to WhatsApp if any network device or policy interferes with ACS or Copilot Studio endpoints.
- Ensure that required Copilot Studio and ACS domains are not blocked by corporate firewalls or proxies.
- If Conditional Access policies are in place for the tenant, verify they are not blocking token acquisition for the Copilot Studio agent on the WhatsApp channel.
- In other Copilot Studio channels, unresponsive behavior with valid transcripts is often caused by network or policy blocks on the real-time messaging path (for example,
- When local checks don’t resolve the issue
- Because analytics show valid sessions, credits, and transcripts, and ACS shows delivered events with zero errors, this is likely a platform-level or configuration edge case.
- In such cases, the recommended next step is to open a support ticket with Microsoft Support, providing:
- Environment ID
- Agent ID
- ACS resource and phone number
- Sample timestamps and conversation IDs from the Analytics export where messages are visible in the transcript but not in WhatsApp.
This combination of checks (WhatsApp channel binding, authentication mode, allowed phone numbers, and network/policy validation) plus escalation to Microsoft Support if needed is the supported path to resolve a situation where Copilot Studio shows successful conversations but WhatsApp clients don’t display the replies.
References: