Proactive Chat Triggers Playbook
Trigger rules that start helpful conversations at the right moment. Use the variants as they are, fill in the placeholders, or download the editable Word file.
1. Pricing page trigger
When to useUse this when the customer situation is pricing page trigger and the reply needs to be specific, calm, and useful.
Rule
When the situation is pricing page trigger, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
2. Checkout hesitation trigger
When to useUse this when the customer situation is checkout hesitation trigger and the reply needs to be specific, calm, and useful.
Rule
When the situation is checkout hesitation trigger, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
3. Docs confusion trigger
When to useUse this when the customer situation is docs confusion trigger and the reply needs to be specific, calm, and useful.
Rule
When the situation is docs confusion trigger, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
4. High-intent return visitor
When to useUse this when the customer situation is high-intent return visitor and the reply needs to be specific, calm, and useful.
Rule
When the situation is high-intent return visitor, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
5. Long session rescue
When to useUse this when the customer situation is long session rescue and the reply needs to be specific, calm, and useful.
Rule
When the situation is long session rescue, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
6. Exit-intent save
When to useUse this when the customer situation is exit-intent save and the reply needs to be specific, calm, and useful.
Rule
When the situation is exit-intent save, the system should respond with one clear next step instead of a generic greeting or a dead-end form.
Customer-facing message
Hi customer name, I can help with that. Based on specific detail, the best next step is next step. I am routing this to owner with the context included so you do not have to repeat yourself.
Internal handling
- Capture the customer's exact wording, especially numbers, dates, product names, and screenshots.
- Add the reason or tag: CRM field.
- Include what has already been tried.
- Set the next owner and deadline.
- Tell the customer what will happen and when.
- If no owner is available, send the fallback message and set deadline clearly.
Quality bar
The customer should understand who owns the issue, what happens next, and when they will hear back.
For small sales and support teams
Capture every lead and follow up on time.
The CRMsoftware.pro AI agent qualifies website visitors 24/7 and sends each inquiry to your leads inbox. Turn a lead into a deal in one click and track every follow-up as a task.
- Leads inbox and 1 pipeline on the free plan
- Tasks with an assignee and a deadline for each follow-up
- WhatsApp, Telegram and human handover from Launch, $19 a month billed yearly
Free plan: 3 users, no credit card.
How to use
How to use this template
- 1
Pick the closest variant. Choose by the situation, not only by the channel.
- 2
Replace every placeholder in brackets. If you cannot fill one, ask the customer one short question first.
- 3
Save the final wording where your team works: your CRM, your help desk, or saved replies and the knowledge base in CRMsoftware.pro.
- 4
Review the results every week. Drop the variants that confuse people and improve the ones that work.
FAQ
Frequently asked questions
Can I use these templates commercially?
Yes. Copy, edit, and use them in your business, client work, CRM, help desk, or CRMsoftware.pro workspace.
Why are there six variants?
One generic template rarely fits every situation. Six variants give your team practical choices without a messy library.
Should I paste these into CRMsoftware.pro?
Yes. Save the best variants as canned replies, knowledge base entries, routing rules, or CRM notes so your AI agent and team stay consistent.
Put this template to work in CRMsoftware.pro
Start free with 3 users and an AI agent that answers on your website 24/7. Paid plans start at $19 a month, billed yearly.