Configure the service-menu introduction
Edit the introduction and optionally use {{contact_name}}. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
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 you’ll accomplish
Edit the introduction and optionally use {{contact_name}}. 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 configure the service-menu introduction.
- 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 to review
Master automated-response switchMaster automated-response switch
Service-menu and branch togglesService-menu and branch toggles
Ticket department and priorityTicket department and priority
Automation ownerAutomation owner
Administrator recipientsmaximum 20
All configurable messagesmaximum 4,000 characters
Rules the system enforces
- The workflow runs only after a conversation is verified and only in one-to-one chats.
- The master switch disables prompts, menus, automated CRM records and confirmations but leaves the live Inbox and manual actions available.
- A processing-state claim prevents simultaneous duplicate handling.
- Edit the introduction and optionally use {{contact_name}}.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.