WhatsApp Observations/Teething Problems

Status
Not open for further replies.

jonfry

SOHO User
Joined
Jan 18, 2021
Messages
14
Reaction score
4
Hi all,

(I know it's still only an alpha build. I'm testing it internally only at this stage. These are my observations).

I have two numbers routed into the business via 3CX. One is a local landline number for voice calls only and the other is for SMS and calls. Customers may have one or both numbers stored in their contact list. Traditionally some customers text work through, some call and some do both so it makes sense to have both numbers associated with WhatsApp too.

Earlier in the week I registered and set up the first number between WA and 3CX. Initially I could only receive WA messages but replies I sent were not received by the sending account. This sorted itself out overnight and I now have two way messaging on that account. Last night I decided to register and set up the second number between WA and 3CX, creating a new app at dev.facebook and a new trunk in 3CX. This morning I have only one way messaging on that trunk so will see whether it sorts itself out overnight.

The WA routing doesn't seem to be working for me. I set up the routing so WA messages arrive at the reception desk in the same way as I have FB and SMS routed. Outside of normal office hours (reception phone goes to DND following global office hours) the WA messages are not delivered to the extension and the sender receives a reply stating 'There are no agents available at the moment'. FB and SMS are still delivered to this extension when the business is closed and can be dealt with the following day but the WA messages are not and there's no indication a message has been received so no way to know a customer has made contact when we are closed.

I changed the destination for calls outside office hours on this WA trunk to an extension not set as DND and excluded from the office hours setting but messages are not being received at that extension. It doesn't seem to be obeying the destination for calls outside office hours setting. When I manually change the reception extension to available messages are once again received.

In the future are we going to be able to initiate WA messages to customers? It would be nice to be able to send customers a 'free' WA message rather than a charged SMS message.

Other than that, the concept of having as many of the customer contact methods (calls, FB, SMS, WA and voicemail) routed into a single system is brilliant. We now only have one place to go to respond to these messages; a massive time saver.
 
Hi,

Same here. I have added two apps to meta.

First app works fine with 3CX, messages work both ways.

Second app only receives messages but doesn’t send messages back to the customer.
 
  • Like
Reactions: jonfry
You can not use the same number as is being used in other routes. So you must dedicate a Whatsapp number to whatsapp only.

In regards to sending out messages, this will probably not be possible or only using pre set templates and with many limitations. Otherwise Whatsapp will be used to send out spams and this is what Meta of course does not want.

So whatsapp is very much a platform to process incoming customer messages, not to send out regular messages to customers or even initiate conversations.
 
Last edited:
Hi Nick,

We are using two different numbers for each App for WhatsApp.

We have been using WhatsApp with Twilio integrations for more than a year now, we do understand how it works.

When we say that messages are not sent, it’s on customer initiated conversations. When the customer initiates the conversation and we reply the messages won’t go out on the second app. On the first app it does works fine.

Upon reading on 3CX forums it looks like several people have the same or similar issue. We are trying to report and help identify if there is a bug or issue so it can be fixed. This feature for 3CX+WhatsApp is a killer feature that will bring tons of new sales and we want to be sure it works perfectly.

Thanks
 
OK make sure the number you are using is not being used by Twilio also.
And in this alpha, the number can not be used anywhere else in 3CX although this will change in alpha 2 which we will release today.
 
  • Like
Reactions: jonfry
Hi,

I can confirm that after update alpha 2, now it works perfectly.

Thanks
 
  • Like
Reactions: N_G and Mazzoni
Hi @ngx , Could you tell me how the process of releasing a number that was already being used as WABA in twilio should be done? Is it necessary to delete the app? Should this be done directly by support?
 
Status
Not open for further replies.