docs: add FAQ for updating WhatsApp business profile info - #655
docs: add FAQ for updating WhatsApp business profile info#655SangeetaMishr wants to merge 4 commits into
Conversation
Explains that address/email/website/description shown on a contact's WhatsApp business profile view is managed via Gupshup, not Glific, and gives the steps to update it there. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
🚀 Deployed on https://deploy-preview-655--glific-docs.netlify.app |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded a FAQ page explaining editable WhatsApp Business Profile fields, how to update them in Meta WhatsApp Manager, and that no additional Glific configuration is required. The page also includes read-time, level, and last-updated metadata. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@tanuprasad530 - Can you please review it by tomorrow ? |
| - Website URLs (your primary website, plus any additional ones) | ||
| - Business email address | ||
| - Physical business address | ||
| - About text (shown when a contact taps the info icon at the top of the chat) |
There was a problem hiding this comment.
About text & social media handles are not mentioned as specific fields. Just checked from a screenshot for one of consulting orgs, when we reached out to gupshup for this.
Pls remove this.
There was a problem hiding this comment.
As per that screenshot I can see a another field names Category.
Please feel free to add that.
Forwarded the email (with the screenshot) for reference.
There was a problem hiding this comment.
Removed "About text" and "social media handles" from the list, and added "Business category" per the screenshot you forwarded.
|
|
||
| # Updating Your WhatsApp Business Profile Info | ||
|
|
||
| When a contact taps on your chatbot's name in WhatsApp, they see a business profile - your description, address, email, and website links. This information isn't managed in Glific. It's part of your WhatsApp Business Profile, which you manage through Gupshup (the WhatsApp Business API provider Glific uses to send and receive messages). |
There was a problem hiding this comment.
Isn't this through Meta Manager Page and not Gupshup? The details to be updated below are accessible through this link: https://business.facebook.com/latest/whatsapp_manager/phone_numbers/ and this is not via gupshup.
There was a problem hiding this comment.
In either case - it would be worth mentioning somewhere that these updated don't require verification by Meta, unlike the display name change.
There was a problem hiding this comment.
Switched the whole flow over to Meta's WhatsApp Manager (business.facebook.com/latest/whatsapp_manager/phone_numbers/) instead of Gupshup, and folded the Gupshup account reference into the intro/step 1 instead of a separate footer section.
There was a problem hiding this comment.
Added a note that these profile updates don't require Meta verification, unlike a display name change.
|
|
||
| ## Steps to update your business profile | ||
|
|
||
| 1. Log in to your Gupshup account - the same account used when you [set up Gupshup](https://glific.github.io/docs/docs/Pre%20Onboarding/Gupshup%20Setup/) for your chatbot. |
There was a problem hiding this comment.
Same as my previous comment - this is through Meta Manager page & Gupshup.
Kindly check and make the necessary changes.
There was a problem hiding this comment.
Updated the steps to go through Meta's WhatsApp Manager (Phone numbers > Profile) instead of the Gupshup dashboard.
|
|
||
| --- | ||
|
|
||
| You can read more about related setup here: |
There was a problem hiding this comment.
If it is indeed through Meta Manager - we can remove this section about "read more"
There was a problem hiding this comment.
Removed the separate "read more" footer section - the Gupshup Setup link is now referenced inline in the intro paragraph instead.
Switches the primary path from Gupshup to Meta's WhatsApp Manager, drops unconfirmed fields (about text, social handles), adds the business category field, and notes these updates skip Meta verification unlike a display name change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/8`. FAQ/Updating Your WhatsApp Business Profile Info.md:
- Line 32: Update the propagation note in “Updating Your WhatsApp Business
Profile Info” to remove the claim that profile updates take effect immediately;
state instead that Meta verification is not required, while acknowledging that
changes may still take time to appear consistently across WhatsApp clients.
- Line 23: Update the FAQ’s profile update instructions to distinguish the
chatbot phone number used to select the business profile from the editable
contact details field; remove or reword “Contact details (phone number)” so it
does not imply the chatbot number can be changed.
- Around line 1-11: Move the “Updating Your WhatsApp Business Profile Info” H1
heading before the metadata <h3> table so it is the document’s first content.
Preserve the existing metadata block and its contents after the heading.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 761586bd-f83a-466b-adef-853ece8b9cdf
📒 Files selected for processing (1)
docs/8. FAQ/Updating Your WhatsApp Business Profile Info.md
| <h3> | ||
| <table> | ||
| <tr> | ||
| <td><b>3 minutes read</b></td> | ||
| <td style={{ paddingLeft: '40px' }}><b>Level: Beginner </b></td> | ||
| <td style={{ paddingLeft: '40px' }}><b>Last Updated: July 2026</b></td> | ||
| </tr> | ||
| </table> | ||
| </h3> | ||
|
|
||
| # Updating Your WhatsApp Business Profile Info |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Place the H1 before the metadata block.
The file currently starts with an <h3> metadata block, triggering markdownlint MD041 and potentially weakening document structure.
Proposed fix
+ # Updating Your WhatsApp Business Profile Info
+
<h3>
...
</h3>
-
- # Updating Your WhatsApp Business Profile Info📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <h3> | |
| <table> | |
| <tr> | |
| <td><b>3 minutes read</b></td> | |
| <td style={{ paddingLeft: '40px' }}><b>Level: Beginner </b></td> | |
| <td style={{ paddingLeft: '40px' }}><b>Last Updated: July 2026</b></td> | |
| </tr> | |
| </table> | |
| </h3> | |
| # Updating Your WhatsApp Business Profile Info | |
| # Updating Your WhatsApp Business Profile Info | |
| <h3> | |
| <table> | |
| <tr> | |
| <td><b>3 minutes read</b></td> | |
| <td style={{ paddingLeft: '40px' }}><b>Level: Beginner </b></td> | |
| <td style={{ paddingLeft: '40px' }}><b>Last Updated: July 2026</b></td> | |
| </tr> | |
| </table> | |
| </h3> |
🧰 Tools
🪛 markdownlint-cli2 (0.23.1)
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/8`. FAQ/Updating Your WhatsApp Business Profile Info.md around lines 1 -
11, Move the “Updating Your WhatsApp Business Profile Info” H1 heading before
the metadata <h3> table so it is the document’s first content. Preserve the
existing metadata block and its contents after the heading.
Source: Linters/SAST tools
| - Business email address | ||
| - Physical business address | ||
| - Business category | ||
| - Contact details (phone number) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== candidate file context =="
cat -n "docs/8. FAQ/Updating Your WhatsApp Business Profile Info.md" | sed -n '1,80p'
echo "== related search for WhatsApp profile / phone number setup docs =="
rg -n "Contact details|phone number|chatbot|organization|Gupshup|Updating Your WhatsApp Business Profile" docs -S || true
echo "== repository files with FAQ path =="
git ls-files | rg "docs/8\. FAQ/Updating Your WhatsApp Business Profile Info.md|docs.*Gupshup|docs.*Pre Onboarding|FAQ|Phone"Repository: glific/docs
Length of output: 50367
Distinguish between selecting and changing the chatbot number.
In the profile update flow, the chatbot phone number is used to select the profile; contacting details for that business profile are the editable field. Clarify this or otherwise avoid presenting the chatbot number as an item to edit.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/8`. FAQ/Updating Your WhatsApp Business Profile Info.md at line 23,
Update the FAQ’s profile update instructions to distinguish the chatbot phone
number used to select the business profile from the editable contact details
field; remove or reword “Contact details (phone number)” so it does not imply
the chatbot number can be changed.
| 3. Update whichever fields you need - photo, description, website, email, address, category, or contact details. | ||
| 4. Save your changes. | ||
|
|
||
| Note: These updates go to WhatsApp directly, not through Glific, so there's nothing further to configure in Glific for this to take effect. It can take a little time for the changes to show up consistently across Android, iOS, Web, and Desktop WhatsApp for your contacts. Unlike changing your WhatsApp Business display name, these profile updates don't need Meta's verification, so they take effect as soon as you save. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Resolve the contradictory propagation wording.
“Take effect as soon as you save” conflicts with the preceding statement that updates may take time to appear consistently. Say that no separate verification is required, but propagation can still take time.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/8`. FAQ/Updating Your WhatsApp Business Profile Info.md at line 32,
Update the propagation note in “Updating Your WhatsApp Business Profile Info” to
remove the claim that profile updates take effect immediately; state instead
that Meta verification is not required, while acknowledging that changes may
still take time to appear consistently across WhatsApp clients.
|
|
||
| # Updating Your WhatsApp Business Profile Info | ||
|
|
||
| When a contact taps on your chatbot's name in WhatsApp, they see a business profile - your description, address, email, and website links. This information isn't managed in Glific. It's part of your WhatsApp Business Profile, which you manage through Meta's [WhatsApp Manager](https://business.facebook.com/latest/whatsapp_manager/phone_numbers/) - using the same Meta Business Account connected to your chatbot's WhatsApp number when you [set up Gupshup](https://glific.github.io/docs/docs/Pre%20Onboarding/Gupshup%20Setup/) (the WhatsApp Business API provider Glific uses to send and receive messages). |
There was a problem hiding this comment.
when you [set up Gupshup](https://glific.github.io/docs/docs/Pre%20Onboarding/Gupshup%20Setup/) (the WhatsApp Business API provider Glific uses to send and receive messages). this is irrelevant na?
Suggesting to remove this - as now it is confusing because there are many terms outside of glific.
Summary
Fixes #538
Adds a new FAQ page, "Updating Your WhatsApp Business Profile Info," answering how to update the address, email, description, and website links shown when a contact taps your chatbot's name in WhatsApp (matching the screenshot in the issue).
This info isn't managed in Glific - it's the WhatsApp Business Profile, managed through Gupshup. The page explains:
ProfiletabCross-links to the existing "Gupshup Setup" doc (same account these steps use) rather than duplicating the account setup instructions.
Verification
Confirmed the exact navigation path and editable fields against Gupshup's own documentation (
docs.gupshup.io/docs/profileanddocs.gupshup.io/docs/manage-business-profile), since Glific doesn't control this profile info itself.Test plan
Summary by CodeRabbit