Unable to send WhatsApp messages to a client – “Something went wrong, please try again later” | Community
Skip to main content
Answered

Unable to send WhatsApp messages to a client – “Something went wrong, please try again later”

  • May 10, 2026
  • 1 reply
  • 92 views

Hi everyone,

I’m unable to send any WhatsApp message to one specific client. No matter what I try to send, I get the error: “Something went wrong, please try again later.”

The client has been waiting for a reply since yesterday, and they also just sent another message a few minutes ago, which I still cannot respond to.

I also tried starting a completely new conversation and sending an already approved template, but the same issue still happens.

Has anyone experienced this or knows how to fix it urgently?

Best answer by Sean Meade Forum Support Lead

Hi folks, Seán here from the Fin technical support team 👋

Just for anyone else that came across this, after reviewing logs, we could see that Intercom successfully handed messages off from our side. The “Something went wrong” error occurred after that point, when delivery was not completed by WhatsApp/Meta for those specific messages.

This issue is resolved now but please reach out directly with the support team if anyone is seeing this kind of behaviour, thanks!

1 reply

Karla T
Intercom Team
Forum|alt.badge.img+1
  • Intercom Team
  • May 17, 2026

Hi ​@Sapir Holtsman 👋  Karla here from the community team here! I’m going to create a conversation with our support team so they can take a closer look and investigate further with you. They’ll be able to dig into your setup and provide more targeted guidance. Keep an eye out for a follow-up from the team shortly.


Forum|alt.badge.img+6

Hi folks, Seán here from the Fin technical support team 👋

Just for anyone else that came across this, after reviewing logs, we could see that Intercom successfully handed messages off from our side. The “Something went wrong” error occurred after that point, when delivery was not completed by WhatsApp/Meta for those specific messages.

This issue is resolved now but please reach out directly with the support team if anyone is seeing this kind of behaviour, thanks!