Update Help Center revenue potential wording - #66
Merged
Conversation
✅ Deploy Preview for legendary-lollipop-e2d131 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pelcasandra
marked this pull request as ready for review
August 10, 2026 16:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
CLM-013 was updated on August 10, 2026 to confirm that Hellotext prioritizes among active, eligible commercial missions according to their probability of generating revenue. The previous “compatible action” wording understated this confirmed product behavior.
The new copy keeps the required eligibility scope visible and does not extend revenue-potential prioritization to reactive conversation routing.
Impact
Copy-only changes across four bilingual Help Center files. No product behavior or Claim Registry data is changed.
Validation
git diff --checkyarn build(production Jekyll build for both languages and security-header verification)