These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- CRM + E-commerce for D2C
- Features
- Retention follow-ups
Retention follow-ups
Schedule customer outreach and carry each submitted follow-up through review.
OverviewMy follow-ups×
CRM + E-commerce for D2C · Retention follow-ups
New
My follow-ups
Retention follow ups
| Parent opportunity | Account | Subscriber | Follow up at | Purpose | Status | |
|---|---|---|---|---|---|---|
| OPP-19734 | ACC-120 | SBS-695 | 05 Oct | PRP-126 | Draft | |
| OPP-22511 | ACC-110 | SBS-720 | 10 Oct | PRP-796 | Submitted | |
| OPP-55081 | ACC-130 | SBS-694 | 25 Oct | PRP-197 | Approved | |
| OPP-88656 | ACC-150 | SBS-225 | 08 Oct | PRP-891 | Completed | |
| OPP-91106 | ACC-110 | SBS-311 | 16 Oct | PRP-432 | Draft |
6 of 6 records
SBS-695Retention follow ups · RFU-17778
DraftParent opportunityOPP-19734
AccountACC-120
Follow up at05 Oct
PurposePRP-126
What you can do
The work in this module
A retention follow-up is anchored to an opportunity and organization, with an owner responsible for the next contact. It can also name the account, subscriber, purpose, follow-up date, quantity and an external order reference. Status moves through Draft, Submitted, Approved, Rejected and Completed. This lets the team separate a planned touchpoint from a reviewed one and a finished one.
A follow-up keeps a planned contact date, purpose, owner and parent opportunity. Its account, subscriber, quantity and external order reference add context when the team has it. Draft, Submitted, Approved, Rejected and Completed distinguish preparation, review and completed outreach without turning a product-interest line into an order.
How the work is organized
- Ownership. The named owner keeps the next action current and is responsible for resolving stale work.
- Context. Related records keep the customer, opportunity and organization together so the team can inspect the case before acting.
- Evidence. A date, outcome, decision or receipt helps a colleague understand what actually happened.
What to agree during setup
Agree what requires a reviewer decision, how long a submitted item may wait and who handles a rejected follow-up. Decide how an external order reference is captured if a connected order system supplies one. Use quantity as context for the follow-up and keep the related reference with the case.
Pilot a dated check-in with a Retention Owner and a different Retention Reviewer. They should agree what context the reviewer needs from the linked opportunity, how to handle a revised purpose and who records the decision. Check that the owner can see the status and act on an approved item.
Check the handoff on an actual case
After an opportunity closes, the Retention Owner schedules a check-in about the product discussed. The owner records the purpose and contact date, then marks the follow-up Submitted for review. The Retention Reviewer examines the account and opportunity context, records a decision against the submitted revision and gives a reason when returning or rejecting it. After approved outreach, the owner marks the follow-up Completed.
Before handoff, compare the follow-up revision with the source revision on its review decision. The next Retention Owner should see the contact date, purpose and decision without relying on a verbal explanation. An external order reference may help identify a separate order, but it does not represent an order managed here.
What your team sees
- My follow-ups — See owned follow-ups with contact date, purpose and status.
- Follow-up review inbox — Find Submitted follow-ups with the owner and revision for a decision.
Follow the work through
See opportunity progress, customer follow-up and the data model for the linked records.
What it keeps track of
Data model- Retention follow ups
- Scheduled retention follow-up records: owner, contact date, quantity, reference number and review lifecycle.
- Opportunities
- A potential sale being pursued, used to track its progress, value, and likelihood of closing.
- Accounts
- A customer or business the team sells to, used to track their details, potential, and standing.
- Team members
- A person who works at the organization; the team uses it to know who owns accounts, deals, and tasks.
- Review decisions
- A recorded approval or rejection on a deal, used to track who signed off and why.
Who uses it
Permissions- Retention Owner
- And Retention Reviewer use this module to prepare, decide and check the next handoff.
- Admin
- Maintains access and organization settings.
Set up CRM + E-commerce for D2C your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.