Disable registered-mobile recognition
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Force unknown/new one-to-one conversations through the exact registered-email workflow when verification remains enabled.
Where to goAdmin Area → WhatsApp → Settings
Before you start
- Verify the module is active and select the intended WhatsApp account before changing any operational record.
- Use an account with the stated native CRM capability and per-account access.
- Test with controlled customer/contact data before relying on live verification, email or CRM automation.
What this guide helps you do
Force unknown/new one-to-one conversations through the exact registered-email workflow when verification remains enabled. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Follow these steps
- Go to Admin Area → WhatsApp → Settings.
- Find the control used to disable registered-mobile recognition.
- Select or enter only the supported value described below.
- Select the page’s Save, Save settings, Save access control or Save controls action.
- Reload or open the affected Inbox/account and verify the new behaviour.
Fields and options
Customer verification toggleCustomer verification toggle
Registered-mobile recognition toggleRegistered-mobile recognition toggle
Maximum attempts1–10
Configurable verification and welcome messagesConfigurable verification and welcome messages
Conversation verification status and linked contact/customerConversation verification status and linked contact/customer
Rules and limits
- Verification runs only for one-to-one conversations, not groups or broadcast/status content.
- A registered-mobile match must resolve to exactly one active contact; ambiguous or unknown numbers fall back to exact registered email.
- Raw submitted email is not copied into audit context; a one-way hash is recorded.
- Force unknown/new one-to-one conversations through the exact registered-email workflow when verification remains enabled.
Check it worked
- The requested action completes without a permission, validation, connector or native CRM error.
- The selected account or conversation shows the expected state without changing another account’s data.
- Where the action creates evidence, confirm the message, native record, verification event, portal history or audit entry is present.
Security, privacy and troubleshooting checks
- Never expose connector tokens, loopback ports, authentication directories or raw customer verification replies.
- Use the supported Connections, Access Control, Settings and Audit Trail pages rather than editing runtime or database records directly.
- If the expected control is missing, verify both native capability and per-account permission before treating it as an installation fault.
Related guides
Was this guide useful?Your response is stored only in this browser.