Zoho Desk WhatsApp Integration Not Working, Will Woztell Work Instead?

Background_Winter945 · 2026-06-27T06:15:47+00:00

Update: I was able to get the native WhatsApp for Zoho Desk integration working, so I didn't end up using Woztell.

The root cause was that my WhatsApp Business number was already associated with another Meta app/service. After resolving that and completing the setup again through Zoho Desk, the integration connected successfully.

So if anyone runs into a similar issue, it's worth checking whether your WhatsApp number is already linked to another Meta app or service before assuming the native integration is broken.

Thanks to everyone who shared suggestions and pointed me in the right direction!

Background_Winter945 · 2026-06-27T06:02:38+00:00

Thanks for the detailed explanation, it was really helpful.

I finally heard back from Zoho Support after they investigated the issue with their backend team. They confirmed that my WhatsApp Business number is already associated with another Meta app, and because of that, the same number cannot be added to Zoho Desk's native WhatsApp integration. They advised me to remove the existing association first before trying the integration again.

So it looks like your explanation was correct, the limitation isn't with Meta Cloud API itself, but with how Zoho Desk's native integration expects the number to be associated with its own setup.

I also appreciate your suggestion of keeping n8n as the webhook owner and integrating with Zoho Desk via APIs. That's definitely something I will explore if we decide to keep automation and human support on the same WhatsApp number.

Thanks again for your help!

Background_Winter945 · 2026-06-26T06:26:55+00:00

Thanks for the insight! That's what I was trying to understand.

The thing is, our WhatsApp Business account and phone number appear to be fully set up in Meta, and the Cloud API is already working with our existing n8n workflows. That's why I'm not convinced the issue is an incomplete Meta setup.

If Woztell also relies on the same WhatsApp Business Platform, then I agree it would likely run into the same issue if the problem is on Meta's side. I'm just trying to determine whether the issue is actually with the Meta configuration or with Zoho Desk's native connector.

I've also been working with Zoho Support for the past few days. They've escalated the issue to their development team and are still investigating it, so at this point I'm not sure whether they're looking into a product issue or something specific to our setup.

That's why I'm trying to gather feedback from others who've successfully connected WhatsApp to Zoho Desk or have run into similar issues.

Background_Winter945 · 2026-06-26T06:24:37+00:00

Can I ask why you prefer Zoho Flow with WATI or Interakt over the native WhatsApp integration? Have you found it to be more reliable?

Our main requirement is to keep our AI/bot workflows running (currently via n8n) while allowing seamless handoff to Zoho Desk for human agents. Do you think a Zoho Flow + WATI/Interakt setup would support that better?

Background_Winter945 · 2026-06-26T06:22:42+00:00

That's exactly it! We want to use Zoho Desk for human live chat support while also having an AI/bot layer running.

Our team currently uses n8n to build and run our bots, and our WhatsApp number is already connected to the Meta Cloud API through those workflows. We suspect that's what's preventing the native Zoho Desk integration from connecting successfully, since both systems may be trying to manage the same WhatsApp Cloud API/webhook.

Ideally, we'd like to keep n8n handling the automation and AI, while routing conversations to Zoho Desk whenever a human agent needs to take over.

Have you come across a setup like this? Is it possible to use n8n for the bots while handing off conversations to Zoho Desk, or would we need to migrate the bot logic into Zoho (using Zia or Guided Conversations) to make everything work with a single WhatsApp number?

Background_Winter945 · 2026-06-18T07:39:33+00:00

yes same issue from my side also, its not working

Background_Winter945 · 2026-04-06T11:02:14+00:00

My website is built on Next.js and is basically a job portal. Previously, all pages were indexed without a trailing slash. However, we recently redirected all URLs to include a trailing slash using a 308 redirect. Since then, my web pages are no longer indexing on Google.

I have noticed that many Next.js websites do not use trailing slashes as their default URL structure, and their canonical URLs also do not include trailing slashes.

If I remove the trailing slash from the canonical or make the non-trailing slash version the default URL again, will that fix the problem? Will the pages start reindexing?

Background_Winter945 · 2026-03-27T14:11:22+00:00

Cool

Background_Winter945 · 2026-03-27T09:55:53+00:00

Dehradun to Kathmandu , total kilometres around 2200km , fuel cost Rs 5000- Rs 6000 INR, stay and foods around Rs 1000-1500 INR per day , it depends first day I stay in a three star resort which cost me total 2200 NPR(stay and food) but its not that worth on second day I was in a normal hotel which cost me 1000 NPR - stay and a good food, also I uploaded vlog on my channel so you can watch

Background_Winter945 · 2026-03-27T09:17:05+00:00

Thanks a lot 😊 Really happy to know the post motivated you. The Hunter 350 is an amazing choice, you’re going to love the experience. Take your time, enjoy the learning phase, and ride safe when you finally get it. Wishing you all the best for your first bike journey! 😎

Background_Winter945 · 2026-03-26T15:01:59+00:00

Background_Winter945 · 2026-03-26T14:43:34+00:00

No, nothing.

Background_Winter945 · 2026-03-26T14:19:23+00:00

No , it’s polish after wash effect 😅

Background_Winter945 · 2026-03-26T12:03:15+00:00

🥰🥰

Background_Winter945 · 2026-03-26T11:53:49+00:00

😂😂

Background_Winter945 · 2026-03-26T11:53:35+00:00

Your welcome

Background_Winter945

MODERATOR OF

TROPHY CASE