If you sell to both businesses and consumers, or if you're moving from one market to the other, your dunning sequence probably needs more than one version.
B2B and B2C customers fail payments for different reasons, respond to different messaging, operate on different timelines, and require different escalation paths. A dunning sequence that recovers 65% of B2C payments might recover only 35% of B2B payments, and vice versa. The mechanics of payment failure are the same. Everything else is different.
Here's where the two models diverge and how to adjust your approach for each.
The Core Differences
Who receives the email matters
B2C: The person whose card failed is the person who uses the product and the person who decides whether to update. It's one human making one decision. Your dunning email lands in their personal inbox, and they either act or they don't.
B2B: The person whose card failed might be a finance manager, an office admin, or a founder who set up billing six months ago. The person who uses the product might be an entirely different team. And the person who can authorize a card update might be someone else entirely.
This stakeholder fragmentation is the #1 reason B2B dunning underperforms when you copy a B2C sequence. Your email might reach the billing contact who hasn't logged into your product in months, while the team of 15 people who use it daily has no idea there's a payment issue.
The payment method tells a different story
B2C: Credit cards, mostly. Sometimes debit cards or PayPal. The customer owns the card and can update it immediately. The most common failure reasons are expired cards (they have a replacement in their wallet) and insufficient funds (temporary).
B2B: Corporate credit cards, virtual cards, purchasing cards, and increasingly, invoicing and ACH. Corporate cards have their own set of complications:
- They expire on company schedules, not personal ones
- They may have spending limits that your charge exceeds
- The cardholder might have left the company
- Finance may have switched card providers without updating vendors
- Some companies require PO numbers or approval workflows before any payment can be processed
A B2C customer can update their card in 30 seconds. A B2B customer might need to file an internal request, get it approved by procurement, and wait for a new virtual card number to be issued. That process takes days, not minutes.
The urgency equation is inverted
B2C: High emotional urgency, low financial stakes. A $15/month streaming subscription or a $49/month productivity app. The customer cares about access (they want to watch their show, use their tool), but the dollar amount isn't keeping anyone up at night. Recovery depends on making the update fast and easy.
B2B: Low emotional urgency, high financial stakes. A $500/month team license or a $2,000/month enterprise plan. The financial impact is significant, but the person handling billing may not feel personal urgency about it. It's a task on a list, not a problem keeping them from their evening plans.
This inversion means:
- B2C dunning should focus on speed and ease of action
- B2B dunning should focus on persistence and reaching the right person
B2C Dunning: Speed and Simplicity
For B2C customers, the optimal dunning sequence is fast, friendly, and frictionless. You're dealing with one person who can resolve the issue in under a minute. Your job is to make them aware of the problem, make the fix effortless, and do it quickly before they forget or move on.
The B2C sequence
Day 0: Immediate notification
Subject: Your $29 [Product] payment didn't go through
Hi [Name],
We tried to charge your card for [Product] but it didn't
go through. Quick fix:
[Update Card - 30 seconds, no login needed]
Your account is safe. Once updated, we'll retry automatically.
[Product] Team
Short. Direct. Pre-authenticated link. Under 50 words.
Day 1: SMS
Hi [Name], your $29 [Product] payment didn't go through.
Update your card here: [link]
B2C customers respond well to SMS. The immediacy and intimacy of a text message drives faster action than a second email would.
Day 4: Value reminder
Subject: [Name], don't lose your [specific feature/data]
Hi [Name],
Just a reminder about your [Product] payment. You've
[specific usage: "created 47 designs" / "tracked 12
workouts" / "saved 89 bookmarks"] and we'd hate for you
to lose access.
Update your card and pick up right where you left off:
[Update Card]
[Product] Team
Tap into loss aversion. Reference their specific usage to make the potential loss tangible.
Day 7: Final warning
Subject: Your [Product] account will be paused Friday
Hi [Name],
Your payment is still pending. On [date], your account
will be paused and you'll lose access to [specific thing].
Your data stays safe for 30 days. You can reactivate
anytime by updating your card.
Last chance: [Update Card]
[Product] Team
Clear deadline. Specific consequence. Reassurance about data.
Day 14: Win-back (post-cancellation)
Subject: We saved your [Product] account
Hi [Name],
Your [Product] account was paused due to a payment issue.
Everything is still here: [specific data/usage stats].
Come back anytime: [Reactivate]
[Product] Team
B2C timing: Compressed
Total sequence length: 7 days active dunning + 7-day win-back. B2C customers who are going to act will act within the first week. Extended sequences have diminishing returns.
B2C channels: Email + SMS
SMS is highly effective for B2C. Text messages are personal, immediate, and have 95%+ open rates. Use SMS for the initial follow-up and the final warning, with email carrying the longer messages.
B2B Dunning: Patience and Escalation
B2B dunning requires a fundamentally different approach. You're working within organizational processes, dealing with multiple stakeholders, and often waiting for decisions that involve more than one person.
The B2B sequence
Day 0: Notification to billing contact
Subject: [Company] payment for [Product] didn't process
Hi [Name],
The payment of $499 for [Company]'s [Product] subscription
didn't go through.
This usually happens with expired corporate cards or
spending limit flags. You can update the payment method
here: [Update Payment]
Your team's access to [Product] is unaffected while we
sort this out.
If you're not the right person to handle billing, could
you forward this to whoever manages [Company]'s
subscriptions? That would help us get this resolved.
[Your name]
[Product] Team
Key B2B elements: mention the company name (not just the individual), reference the team's access, and explicitly ask for routing if this person isn't the right contact. That last bit is critical. In B2B, your billing email often reaches someone who can't personally resolve it.
Day 3: Follow-up with CC suggestion
Subject: Re: [Company] payment for [Product]
Hi [Name],
Following up on [Company]'s [Product] payment. The invoice
of $499 is still outstanding.
If the payment process on your end requires any additional
information from us (PO number, updated invoice, W-9, etc.),
just let me know. Happy to provide whatever's needed.
Update payment method: [Update Payment]
Download invoice: [Invoice Link]
[Your name]
This email acknowledges the reality of B2B procurement. Sometimes the holdup isn't a card issue at all. It's a missing PO number, a paperwork requirement, or an approval workflow. Proactively offering supporting documents removes friction.
Day 7: Escalation
Subject: Action needed: [Company]'s [Product] subscription
Hi [Name],
I wanted to let you know that [Company]'s $499 monthly
payment for [Product] has been outstanding for 7 days.
Your team currently has [X active users / specific usage
data]. To avoid any disruption to their workflow, we'll
need updated payment information by [date].
If there's a better way to handle billing (invoicing,
ACH transfer, different contact), I'm happy to set that
up. Just reply and we can work it out.
Update payment: [Update Payment]
[Your name]
At day 7, introduce a specific deadline and mention the team that relies on the product. This creates internal pressure. If the billing contact hasn't acted, knowing that their team's tool is at risk may prompt escalation within their own organization.
Day 10: Direct outreach to user/admin (if possible)
If you have contact information for the primary user or admin (separate from the billing contact), a short email to them can unblock the situation:
Subject: Heads up about your [Product] account
Hi [Admin Name],
I wanted to flag that [Company]'s payment for [Product]
hasn't processed. This is usually a billing issue that
[Billing Contact Name] can resolve, but I wanted to make
sure your team is aware.
If you can nudge your billing/finance team, that would
help us avoid any interruption to your account.
Thanks,
[Your name]
This is a careful escalation. You're not going over anyone's head. You're making sure the people who rely on the product know there's a risk.
Day 14: Final notice
Subject: [Company] [Product] account: final notice
Hi [Name],
[Company]'s payment for [Product] has been outstanding for
14 days. We've extended the grace period, but we'll need to
restrict access on [date] if we don't receive payment.
Your team has [specific access/data details]. All data will
be preserved during any restriction period.
Options to resolve:
1. Update card: [Update Payment]
2. Pay by invoice: [Request Invoice]
3. Pay by ACH/bank transfer: [Setup ACH]
4. Discuss other arrangements: Reply to this email
[Your name]
Multiple payment options are a B2B necessity. Some companies can't put a $499/month charge on a credit card. Offering invoicing or ACH removes a real structural barrier.
B2B timing: Extended
Total sequence length: 14-21 days active dunning. B2B processes are slower. Giving up after 7 days means giving up before many companies have completed their internal approval cycles.
B2B channels: Email primary, phone for high-value
SMS is less effective in B2B. The billing contact's phone number might not even be in your system, and a text message about a business subscription feels intrusive. Email is your primary channel.
For high-value accounts ($500+/month), a phone call at day 7-10 is appropriate and effective. "Hi, this is [Name] from [Product]. I'm calling about a billing issue on your account. Just want to make sure your team doesn't lose access." Phone calls convert at 2-3x the rate of email for B2B.
Side-by-Side Comparison
| Dimension | B2C | B2B |
|---|---|---|
| Decision maker | Individual | Multiple stakeholders |
| Average ACV | $15-100/mo | $100-5,000+/mo |
| Common failure reason | Expired personal card | Corporate card limits, employee turnover |
| Primary channel | Email + SMS | Email + phone |
| Sequence length | 7 days | 14-21 days |
| Tone | Casual, friendly | Professional, helpful |
| Key motivator | Loss of personal access | Team disruption risk |
| Escalation path | Urgency in emails | Contact additional stakeholders |
| Payment alternatives | Card only | Card, invoice, ACH, wire |
| Win-back timing | 7-14 days post-cancel | 14-30 days post-cancel |
| Recovery rate benchmark | 55-65% | 45-60% |
Hybrid Approach for Prosumer Products
Some products straddle B2B and B2C. A design tool used by freelancers and agencies. A project management app used by individuals and teams. In these cases, you need to segment.
Signal-based routing:
- Personal email domain (@gmail, @yahoo) = B2C sequence
- Business email domain (@company.com) = B2B sequence
- Solo plan = B2C sequence
- Team plan = B2B sequence
- Under $50/month = B2C sequence
- Over $200/month = B2B sequence
You don't need perfect segmentation. Even a rough split based on email domain or plan type will significantly outperform a one-size-fits-all sequence.
Key Takeaways
- One sequence doesn't fit both. B2B and B2C customers fail for different reasons and recover through different processes.
- B2C is about speed and simplicity. Get the email there fast, make the fix easy, and use SMS to catch what email misses.
- B2B is about persistence and routing. The billing contact might not be the decision maker. Ask for routing. Offer multiple payment methods. Be patient with organizational processes.
- B2B grace periods should be longer. 14-21 days accounts for procurement cycles. 7 days doesn't.
- Phone calls work for high-value B2B. A 5-minute call recovers more than 5 follow-up emails for accounts over $500/month.
- Segment by signals. Email domain, plan type, and price point are reliable proxies for B2B vs. B2C when you can't tag explicitly.
Rekko lets you build multiple dunning sequences and assign them based on customer attributes. Create a fast, SMS-heavy B2C sequence and a patient, multi-stakeholder B2B sequence, then route customers automatically based on their plan or account type.
Start your free trial and stop sending the same recovery email to a freelancer and an enterprise finance team.