Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Wesley Bowles
Beigetreten 03. Okt. 2022
·
Letzte Aktivität 18. Juli 2023
Folge ich
0
Follower
0
Gesamtaktivitäten
14
Stimmen
3
Abonnements
7
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Wesley Bowles
Wesley Bowles hat einen Post erstellt
So we're having an issue where it seems one or two keywords are too heavily weighted in our Messaging bot article recommendations.
In our company's case, the word "Design" is used quite frequently for a variety of intents throughout our help centre articles.
The problem we're having is the article recommendations are almost always never what the customer is looking for because the main keyword the messaging bot seems to pick up on is "Design" rather than everything else in the customers question.
For example, we have a large section of our help center devoted to accessibility and how users can make their designs accessible. If a user asks the question "How do I make my design accessible" No accessibility related articles. Instead numerous completely unrelated articles are provided simply because the word "Design" is included in them.
I guess what this boils down to is there doesn't seem to be a way for me to tell the messaging bot specifically to ignore common words, in our case, the word "design".
And yes I realize the best option here is to craft an answer for the bot if I know I want to target the accessible intent. The problem surfaces for lesser known intents we don't have crafted answers for yet and the negative user experience customers receive when chatting with the bot.
I'll also highlight that this is NOT the case for email article recommendations. The email auto reply suggestions actually handle this MUCH better and customers get the articles that make sense.
I hope that makes sense? TLDR, we have a broadly used keyword that seems to be too heavily weighted causing completely inaccurate recommendations within messaging.
Gepostet 12. Juli 2023 · Wesley Bowles
2
Follower
1
Stimme
0
Kommentare
Wesley Bowles hat einen Kommentar hinterlassen
Hey Jakub Konik , following up again. Are there any updates on the road map for Sell trigger conditions?
Kommentar anzeigen · Gepostet 19. Juni 2023 · Wesley Bowles
0
Follower
3
Stimmen
0
Kommentare
Wesley Bowles hat einen Kommentar hinterlassen
I appreciate the updated deal triggers however we're still extremely limited in what we need.
We need to automate the movement of deals through deal stages based on time. For example, we handle renewal flows in Sell and based on how close we are to the customer's renewal date, the stage of that deal should change to reflect where the deal is in it's lifecycle.
In hubspot i could handle this with a standard workflow: If date in {{date field}} is less than 90 days from now, move deal to new stage.
I can't achieve this right now because the triggers are only based on if a deal is updated. Not all of our deals get updated daily or even weekly but automated actions still need to occur.
Kommentar anzeigen · Gepostet 21. Feb. 2023 · Wesley Bowles
0
Follower
0
Stimmen
0
Kommentare
Wesley Bowles hat einen Kommentar hinterlassen
Are there plans to include subscription properties in triggers/automatons?
For example:
-ability to automate tasks based on upcoming subscription renewals
-trigger subscription creation based on deal closure (or end subscription based on deal lost)
-Trigger email sequences to fire based on the amount of elapsed time from when the subscription has started?
etc.
Kommentar anzeigen · Gepostet 03. Okt. 2022 · Wesley Bowles
0
Follower
2
Stimmen
0
Kommentare