fix(automation): drop BSP wording in QR-trigger explainer#43
Merged
Conversation
ForgeChat is not a WhatsApp BSP; we are a Meta Business Partner. The QR-code trigger description in the automation builder said "the BSP attributes it via the pre-filled text", which is both incorrect about our partner status and confusing to users. Reword to "ForgeChat attributes it via the pre-filled text" so the explainer correctly names the actor doing the attribution. Signed-off-by: KingArthur000 <sathyaprakashelango@gmail.com>
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
1 participant
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.
Why
The QR-code trigger explainer in AutomationBuilderView.jsx:1904 said:
Forgemind is a Meta Business Partner, not a WhatsApp BSP. "BSP" is the WhatsApp Business Solution Provider tier — a different program with different obligations. Naming us a BSP in user-facing copy both overstates our relationship with Meta and is confusing for self-hosters.
What changed
AutomationBuilderView.jsx:1904 — "the BSP attributes it" → "ForgeChat attributes it". The new wording is also clearer about what is doing the attribution.
The internal
source: "bsp"enum values at lines 1920/1926/1932 are untouched — they're not user-facing (only thesourceLabelstrings are) and renaming the enum risks breaking unknown call sites. Brand compliance doesn't require it.Test plan