मुफ्त लाइब्रेरी
21 विफल भुगतान वसूली के हर चरण को कवर करने वाले कॉपी-पेस्ट टेम्पलेट: ईमेल, SMS, WhatsApp। परीक्षित सब्जेक्ट, रीट्राय टाइमिंग, और डिक्लाइन-कोड-विशिष्ट प्रकार। कोई साइनअप नहीं, कोई गेट नहीं।
प्राथमिक डनिंग चैनल। अनुक्रम के हर चरण में उपयोग करें।
गैर-ईमेल पाठकों तक पहुंचने के लिए दिन 3+ पर मल्टी-चैनल पुश। TCPA-अनुपालन।
जहां अपनाव अधिक है (LATAM, EU, भारत, SEA) सबसे मजबूत चैनल।
भुगतान विफलता होने से पहले भेजा जाता है, ताकि स्रोत पर चर्न को रोका जा सके।
Sent 30 days before a card on file expires, based on the expiration date you already have stored. Goal: fix the card BEFORE the payment fails, preventing dunning entirely. This is the single most effective pre-dunning move.
Sent 30 days before an annual subscription auto-renews. Goal: transparently remind the customer, offer an upgrade/downgrade path, reduce chargeback risk. Required by law in several US states (e.g., California) and in the EU.
तत्काल पहला संपर्क, आमतौर पर पहली विफल चार्ज के मिनटों के भीतर।
The first email sent immediately after a payment fails, before any retry. Goal: catch the 40-60% of failures that resolve with a simple nudge, before the customer feels embarrassed or annoyed.
Sent when a subscription payment fails specifically because the card on file expired. This is the easiest dunning recovery - not a money problem, just an admin task. Goal: treat it like routine maintenance, not an emergency.
Sent when a payment fails with insufficient_funds. Customers in this bucket are often experiencing cash flow issues and aggressive emails here cause churn and support tickets. Goal: keep them as a customer long-term even if this payment cycle needs flexibility.
Sent when the bank flagged the transaction (do_not_honor, generic_decline, call_issuer). The card is valid; the bank blocked this specific charge. Goal: explain this is a routine bank fraud flag (not a card problem) and give two clear paths to fix it.
Sent when the bank requires 3D Secure / Strong Customer Authentication (SCA) before approving the charge. Almost always an EU or UK customer. Goal: explain this is standard, normalize the verification step, link to the 3DS challenge.
जब प्रारंभिक हेड्स-अप ने भुगतान पुनर्प्राप्त नहीं किया तो फॉलो-अप।
Sent on day 3 after the friendly heads-up did not recover the payment. The customer has ignored the first email. Goal: be direct without being aggressive, and preempt silent churn.
An SMS version of the day 3-5 dunning email, used as a multi-channel push alongside email. Goal: reach customers who are not reading email. SMS has 45-50% open rates compared to 20-30% for email.
WhatsApp message sent on day 3-5 for customers with a WhatsApp-linked phone number. Goal: use the highest-open-rate channel available (90%+ in most markets) for maximum reach.
मध्य-अनुक्रम अनुस्मारक जो नुकसान को ठोस बनाता है।
Sent on day 7 after two prior emails did not work. The customer has ignored both. This email is not about payment mechanics anymore - it is about what they are about to lose. Goal: make the loss concrete and offer a clean exit if they want out.
Last-chance SMS sent at day 7 or day 14, paired with the final email. Goal: catch customers who are not reading email before the account suspends.
अंतिम सूचना, साफ बंद, और विन-बैक हुक।
Sent on day 14 after all retries and prior emails have failed. The grace period is over. Goal: close cleanly, preserve goodwill, and leave the door open for reactivation. A well-done final notice is often the best win-back hook you have.
Sent as the final payment escalation for B2B SaaS customers (larger accounts, AP departments, purchase orders). Goal: formalize the escalation without damaging the relationship, and give the AP team everything they need to pay.
Final WhatsApp message sent at day 14 alongside the final email. Goal: reach the last bucket of non-responders with the channel they are most likely to read.
सफल रिकवरी के बाद भेजा जाता है ताकि लूप बंद हो और विश्वास फिर से बने।
Sent immediately after a retry succeeds following a dunning sequence. Goal: close the loop, reassure the customer, and turn a near-churn moment into a positive touch. Skipping this email is a common mistake.
Sent immediately after a customer successfully updates their card. Goal: confirm the update, reassure that billing will resume normally, and close the dunning loop cleanly.
कैंसिलेशन के 30-90 दिन बाद चर्न ग्राहकों को फिर से जोड़ें।
Sent 30-60 days after a subscription was cancelled due to failed payments. The customer has had time to decide whether they want to come back. Goal: re-engage with a specific reason (new feature, usage-relevant improvement) and remove friction to reactivate.
Sent immediately after a churned customer reactivates their subscription. Goal: confirm the reactivation, restore trust, and set up a proactive check-in so they do not churn again.
जब ग्राहक रद्द करने पर क्लिक करता है तो नरम विकल्प (विराम, डाउनग्रेड, छूट) देने के लिए भेजा जाता है।
मुफ्त ट्रायल को चुपचाप समाप्त होने से पहले भुगतान में बदलें।
ऊपर दिए गए टेम्पलेट एक मानक 14-दिन वसूली अनुक्रम पर मैप होते हैं। यह कैडेंस, के आधार पर निर्धारित रीट्राय के साथ संयुक्त Stripe डिक्लाइन कोड, आमतौर पर 60-80% विफल भुगतानों को वसूलता है:
| दिन | कार्रवाई | लक्ष्य |
|---|---|---|
| D0 | रीट्राई + ईमेल #1 (मित्रवत हेड्स-अप) | 60% पकड़ें जिनके पास अस्थायी डिक्लाइन था |
| D2 | रीट्राई (मौन) | अधिकांश वेतन आने के बाद प्रयास |
| D3 | ईमेल #2 (सीधा अनुरोध) + SMS | गैर-ईमेल पाठकों तक पहुंचें |
| D5 | रीट्राई + WhatsApp पुश | 90%+ ओपन रेट चैनल |
| D7 | ईमेल #3 (मूल्य अनुस्मारक) | याद दिलाएं वे क्या खोएंगे |
| D10 | रीट्राई (अंतिम स्वचालित) | अंतिम-मौका रिकवरी पकड़ें |
| D14 | ईमेल #4 (अंतिम सूचना) + WhatsApp | साफ बंद, विन-बैक हुक |
कॉपी-पेस्ट का काम छोड़ें
5 मिनट में Stripe कनेक्ट करें। Rebounce विफलताओं का पता लगाता है, डिक्लाइन कोड के अनुसार वर्गीकृत करता है, और सही समय पर ईमेल, SMS, और WhatsApp में सही टेम्पलेट चलाता है। वसूली पर ऑटो-कैंसिल। $3.50/माह से।