Delete a standard reply
Confirm deletion; the reply and its selected-staff mappings are removed permanently. 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 → Standard Replies
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
Confirm deletion; the reply and its selected-staff mappings are removed permanently. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Follow these steps
- Go to Admin Area → WhatsApp → Standard Replies.
- Select the correct account, conversation, customer, staff member or session before you delete a standard reply.
- Complete the visible fields and confirmation prompts exactly as described below.
- Select the available action once and wait for its success or validation response.
- Check the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.
Fields and options to review
WhatsApp accountone account or All accounts for administrators
Titlerequired, maximum 191 characters
Shortcutmaximum 80 characters
Categorydefaults to General, maximum 100 characters
Reply textrequired, maximum 10,000 characters
Sort order0–10,000, default 100
VisibilityAll authorised staff or Selected staff only
Activeon or off
Rules the system enforces
- Only administrators can create global All accounts replies.
- A non-administrator must have the native Manage standard replies capability and Manage access to the applicable account.
- The Inbox shows active global and selected-account replies that the current staff member is allowed to see.
- Verify deletion; the reply and its selected-staff mappings are removed permanently.
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.