https://discord.gg/botpress logo
Powered by
conversationStarted trigger
# 🤝help
b
im using conversationStarted trigger at the root of my workflow. earlier it triggered the welcome message when the user clicked on the chatbot icon on my website now the trigger just fires already on page reload, so user lands on webpage and they are immediately getting message from the bot not only that but when the user keeps my website tab in the background even then the bot would randomly give notifs, which is super annoying, cuz the user doesnt even want to interact with the bot, and the bot would still spam them with notif sounds and messages this wasnt the behavior earlier i believe? i didnt change anything https://cdn.discordapp.com/attachments/1459415820315656266/1459415820487626802/image.png?ex=697b9626&is=697a44a6&hm=7ae1876d606a54a7ee27ff30c5486ecd3a4136cbf90d87297131fa9f99694d01& https://cdn.discordapp.com/attachments/1459415820315656266/1459415821410631711/image.png?ex=697b9626&is=697a44a6&hm=7b0b5be5cf71732e259f54971d7a3a1f49d7418a93b93d8681bf5c0d4c917d4f&
anyone?
w
whats the version of your webchat?
b
3.5
it should be sent only on chat window open right
im a paying customer pls help me its urgent, ive had to disable the bot on the website cuz users were reporting bot as annoying behavior
w
have you tried to delete this trigger, deploy , add a new trigger then redeploy ?
or quick fixes like this
also can you show the logs
b
yeah
messeges immediately popup on webpage load, its also using up my available msg quota
w
and do you have any other trigger in your page ?
that's weird
b
yes 2 more custom triggers
well 1 is disabled, so only 1 other custom trigger
deleted both the others, same issue
@wooden-beard-40210 pls help man
l
When the Webchat widget loads, it automatically creates a conversation so the trigger fires immediately on page load. @better-refrigerator-38990
whats your workspace ID
If you are part of the plus plan you have access to direct customer support who can reply on short notice 🙂 messaging on a Sunday evening and not getting an immediate reply is normal!
As a quick workaround until things get fixed disable the start conversation trigger and include a welcome message after the user messages the bot.
b
yeah my bad man forgot it was sunday
wkspace_01KBPB9WS4ZDS7GXDSSTDCXHWA
did this, but is there no way to initiate convo when user clicks the icon, i swear it was like this uptil a few days ago
l
You can try creating a custom trigger instead I see you had one created
b
yeah but i had to target the chatbot element using direct DOM manipulation which broke my react app rules
so i removed that
l
Copy code
window.botpress.on('webchat:opened', () => { 
  // Manually start the conversation or send a welcome 
  window.botpress.sendEvent({ type: 'custom', name: 'startWelcome' }) 
})
for example
b
oh webchat.opened doesnt even get fired, that was the first thing i had tried
l
however the start conversation should only trigger when the webchat is selected, will do some testing on my side and get back
b
pls thank you ross
l
for fun @better-refrigerator-38990
and see if still does it ?
(change the 3.5 to 3.4 in the embed)
can you set webchat to 3.4
b
ok lemme see
original working was on webchat.ready im sending payload and storing in user.email then user would click on chatbot icon and flow would start but ever since the flow has started triggering on webpage load it is clashing with the payload saving thingy
now payload arrives when its expecting a user input and mistakes the payload for user input, i think
l
oh my goodness
b
ik this is annoying im sorry man, im handling this alone and my proj manager would kill me if this is not fixed asap im down to help however needed
l
can you send the link to your web too
@better-refrigerator-38990
the conversation start trigger worked as intended on my end
I didnt recieve a notification in the thumbnail only when clicking it opened
b
@loud-crowd-60573
it even becomes 4 on another refresh
l
dm me the log in again
that way you wont leave it here
b
found anything? @loud-crowd-60573
l
Will drop insight when I can! Hopefully by today it will be all resolved
Found a work around @better-refrigerator-38990
What you can is remove the start conversation trigger and turn this on instead: In the webchat configuration space. This shows a message, but it's just a style (meaning it won't count as a message). If they're interested, they'll send a message.
However this seems to be a bug @better-refrigerator-38990 and it will be reported for fixing!
b
okay then ill disable the trigger for now and tell my team its a bug on botpress end when its fixed you let me know? ill enable it again in my workflow how much time do u reckon it will take to fix this?
l
I cannot give a precise ETA @better-refrigerator-38990
b
ok ive told my team whenever this is fixed ill re-enable the trigger when its fixed pls let me know, thanks ross
2 Views
PreviousNext
Powered by