[GOWS] WhatsApp Business: profile/name succeeds but old name still appears via wa.me

Describe the issue

This concerns accounts using the WhatsApp Business app, linked to WAHA.

Changing the profile name through WAHA returns {"success":true}. Subsequent WAHA reads show the new name, but the old name is still seen when opening the account through its wa.me link.

All names below are fictional examples: OLD EXAMPLE STORE → NEW EXAMPLE STORE. Real business names, phone numbers, session identifiers, and infrastructure details are omitted.

Version

The running instance returned the following from GET /api/version during the follow-up investigation:

{
  "version": "2026.8.1",
  "engine": "GOWS",
  "tier": "CORE"
}

Steps to reproduce / observed workflow

1. Use an existing, working session linked to a WhatsApp Business account whose displayed name is OLD EXAMPLE STORE.

2. Send PUT /api/{session}/profile/name with:

   json复制

   { "name": "NEW EXAMPLE STORE" }

3. WAHA returns:

   json复制

   { "success": true }

4. Read GET /api/{session}/profile: its name is NEW EXAMPLE STORE. Also read GET /api/sessions/{session}: me.pushName is NEW EXAMPLE STORE. These are the relevant fields only; personal data is omitted.

5. Open the account through its wa.me link. The reported visible name is still OLD EXAMPLE STORE.

Expected behavior / clarification requested

We want to change the name customers see for this WhatsApp Business account. If PUT /profile/name supports that field, the customer-visible name should eventually reflect the change.

If this endpoint changes only pushName and cannot change the WhatsApp Business name, please clarify that limitation and the supported way to update the business name.

Verification and limitations

• The successful name update and subsequent WAHA readback were verified across multiple working sessions.
• Profile picture updates succeeded separately, and downloading the refreshed picture confirmed the new image. The remaining issue is the name.
• The old name via wa.me was reported by the operator. We have not isolated whether the exact displayed field is a business name, a saved-contact label, or cached data, nor measured a propagation delay. We are not claiming a confirmed root cause or that every account's public name was checked.
• Reading the WAHA profile controller shows that GET /profile uses me.pushName for its name field, so this readback alone does not independently verify the customer-visible business name.

Questions

1. For WhatsApp Business accounts, which name does PUT /profile/name change: push name, business profile name, or both?
2. Is there another supported endpoint or engine capability for changing the business name displayed when someone opens a wa.me link?
3. If this requires the WhatsApp Business mobile app, or has known propagation/cache behavior, could the Profile API documentation describe it and how to verify the result?

References

• Profile API documentation: https://waha.devlike.pro/docs/how-to/profile/
• Earlier Profile API feature requests: #529 and #453
• Profile controller: https://github.com/devlikeapro/waha/blob/core/src/api/profile.controller.ts

No production logs or identifying screenshots are attached for privacy.