Configure the duplicate-ticket response | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/whatsapp-web-messaging-verified-customer-automation-configure-the-duplicate-ticket-response Publisher: Pixie Technologies LLC Verified-customer service menu, tickets, callbacks and team hand-off Configure the duplicate-ticket response Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use {reference} to identify the existing open ticket in the customer message. Audience: Administrators, service managers and verified customer contacts; Permission: Administrator to configure; automatic system workflow for verified conversations; Module v1.0.0 · 2026.07.30-r20.5; 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 Use {reference} to identify the existing open ticket in the customer message. 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 duplicate-ticket response. - 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 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 and limits - 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. - Use {reference} to identify the existing open ticket in the customer message. 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 Understand duplicate open-ticket protection (https://pixiecrm.com/help-centre/whatsapp-web-messaging-verified-customer-automation-understand-duplicate-open-ticket-protection)Understand when a new ticket is allowed again (https://pixiecrm.com/help-centre/whatsapp-web-messaging-verified-customer-automation-understand-when-a-new-ticket-is-allowed-again)Verified-customer service menu, tickets, callbacks and team hand-off (https://pixiecrm.com/help-centre/topic/whatsapp-web-messaging-verified-customer-automation)WhatsApp Web Messaging (https://pixiecrm.com/help-centre/category/whatsapp-web-messaging)Create a task (https://pixiecrm.com/help-centre/create-a-task)Create a support ticket (https://pixiecrm.com/help-centre/create-a-support-ticket)