docs: add FAQ for updating WhatsApp business profile info #655
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| <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 | ||
|
|
||
| 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). | ||
|
Contributor
There was a problem hiding this comment.
Suggesting to remove this - as now it is confusing because there are many terms outside of glific. |
||
|
|
||
| ## What you can update | ||
|
|
||
| - Profile photo | ||
| - Business description (the short summary shown at the top of the profile) | ||
| - Website URLs (your primary website, plus any additional ones) | ||
| - Business email address | ||
| - Business address | ||
| - Business category | ||
| - Contact details (phone number) | ||
|
Contributor
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 |
||
|
|
||
| ## Steps to update your business profile | ||
|
|
||
| 1. Go to [WhatsApp Manager](https://business.facebook.com/latest/whatsapp_manager/phone_numbers/) in Meta Business Manager, and log in with the Meta Business Account linked to your chatbot's WhatsApp number. | ||
| 2. Under `Phone numbers`, select your chatbot's WhatsApp number, then open its `Profile`. | ||
| 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. | ||
|
Contributor
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 |
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 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
📝 Committable suggestion
🧰 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
Source: Linters/SAST tools