Feature Request: Separate Contact Appearance for WhatsApp
Current Behavior
When using WhatsApp with OpenClaw in selfChatMode, the assistant appears as the user talking to themselves rather than as a distinct contact. This makes it less clear that you're interacting with an AI assistant.
Desired Behavior
The assistant (e.g., "Jeeves") should appear as a separate, named contact in WhatsApp conversations, making it clear you're chatting with an AI assistant.
Current Workaround
According to the assistant's response, the current workaround requires:
- Secondary phone number: Obtain a number that can receive SMS verification (old SIM, cheap eSIM like GiffGaff/Lyca, or virtual number service)
- Link new number to OpenClaw: Generate QR code and use "Link a Device" in WhatsApp with the secondary number
- Update configuration: Modify
openclaw.json to:
- Disable
selfChatMode
- Add primary number to authorized users for the new "assistant" account
Proposed Improvement
Simplify this process or provide better documentation/tooling for:
- Setting up WhatsApp with a distinct assistant identity
- Managing secondary number requirements
- Configuring the assistant as a separate contact without manual JSON editing
Configuration Context
{
"channels": {
"whatsapp": {
"selfChatMode": true,
"dmPolicy": "allowlist",
"allowFrom": ["+447767278403"]
}
}
}
Use Case
Users who want their AI assistant to have a distinct identity in messaging apps, making it clearer when they're interacting with AI vs. themselves.
Environment
- OpenClaw version: 2026.2.6-3
- Platform: macOS (Darwin 25.2.0)
- Channel: WhatsApp (native plugin)
Feature Request: Separate Contact Appearance for WhatsApp
Current Behavior
When using WhatsApp with OpenClaw in
selfChatMode, the assistant appears as the user talking to themselves rather than as a distinct contact. This makes it less clear that you're interacting with an AI assistant.Desired Behavior
The assistant (e.g., "Jeeves") should appear as a separate, named contact in WhatsApp conversations, making it clear you're chatting with an AI assistant.
Current Workaround
According to the assistant's response, the current workaround requires:
openclaw.jsonto:selfChatModeProposed Improvement
Simplify this process or provide better documentation/tooling for:
Configuration Context
{ "channels": { "whatsapp": { "selfChatMode": true, "dmPolicy": "allowlist", "allowFrom": ["+447767278403"] } } }Use Case
Users who want their AI assistant to have a distinct identity in messaging apps, making it clearer when they're interacting with AI vs. themselves.
Environment