Omni-Revenue Framework
Tenet 4 — Omni-Service
v1.0
Tenet 4 of 5 · Omni-Revenue Framework
Omni-Service
Revenue doesn't end at the sale. The best clients come from the ones you already have.
Section 01
Overview
Omni-Service is the retention and expansion engine of the Omni-Revenue Framework. Omni-Insight, Omni-Presence, and Omni-Narrative built the pipeline and filled it. Omni-Service is what keeps clients, turns them into advocates, and generates referral revenue that costs a fraction of new customer acquisition.
Most businesses treat service and support as a cost center — something to minimize. Omni-Service flips this: it treats every post-sale touchpoint as a revenue opportunity. A well-served client leaves a 5-star review, refers two friends, and buys again. A poorly served client churns, warns others, and erases the revenue you fought to acquire.
Tenet Goal
By the end of Omni-Service, the client has a structured onboarding process for new customers, an active support system inside WundertreOS (Buffollow), a loyalty program that rewards repeat business, and a referral system that generates new pipeline without ad spend.
Omni-Service builds systems that the client's team will operate day-to-day. WundertreX builds the infrastructure and trains the team — then hands off the keys. The client must own their service culture.
| WundertreX Owns | Client Owns |
|---|---|
| Buffollow support system configuration | Daily management of support tickets |
| Customer onboarding workflow build | Responding to escalated tickets within SLA |
| Loyalty program design and setup | Providing content for KB articles (FAQs, how-tos) |
| Referral program design and setup | Operating the loyalty and referral programs |
| Knowledge Base (KB) article writing and structure | Responding to CSAT surveys and following up on low scores |
| AI Agent configuration and training | Sharing referral program with existing customers |
| CSAT survey setup and trigger automation | Maintaining service quality standards |
| Support escalation workflow | |
| Monthly CSAT and retention reporting |
Section 02
Delivery Timeline
Omni-Service has a 2-to-3-week configuration sprint for infrastructure build, then immediate operational handoff. The faster the client's team is working inside Buffollow, the more effective this tenet becomes.
| Week | Activity | Owner | Deliverable |
|---|---|---|---|
| Wk 1 | Onboarding workflow mapped — define the post-sale experience step by step from closed-won to fully onboarded customer. | Both | Onboarding Process Map (doc) |
| Wk 1 | Buffollow configured — support pipeline, ticket categories, priority levels, and team assignments set up. | WundertreX | Live Buffollow Support System |
| Wk 1 | Core Workflow built — Closed Won deal in LeadSprout triggers onboarding sequence in Buffollow automatically. | WundertreX | Onboarding Automation Active |
| Wk 2 | Knowledge Base built — minimum 10 articles covering FAQs, product/service how-tos, and common troubleshooting. | WundertreX | KB Live with 10+ Articles |
| Wk 2 | AI Agent configured — trained on KB content to handle first-line support questions without human intervention. | WundertreX | AI Agent Live + Tested |
| Wk 2 | CSAT survey setup — post-resolution survey triggered automatically. 1–5 star rating + open comment field. | WundertreX | CSAT Survey Active |
| Wk 3 | Loyalty program designed and configured — points structure, redemption tiers, and enrollment triggers defined. | Both | Loyalty Program Live |
| Wk 3 | Referral program designed and configured — referral link, reward structure, and confirmation workflows built. | Both | Referral Program Live |
| Wk 3 | Support team training — ticket management, escalation process, KB usage, and CSAT response protocol. | WundertreX | Training Complete + Recorded |
| Wk 3 | Reputation workflow activated — CSAT 4–5 star triggers review request (Google, Yelp). 1–2 star triggers internal escalation. | WundertreX | Review Request Workflow Active |
| Ongoing | Monthly CSAT report and churn analysis shared with client. | WundertreX | Monthly Retention Report |
| Ongoing | KB articles reviewed quarterly and updated for accuracy. | Both | KB Update Log |
| Ongoing | Referral leaderboard shared with client team monthly — celebrate top referrers. | WundertreX | Referral Report |
Section 03
WundertreOS Walkthrough
Omni-Service lives inside Buffollow and Core Workflows. The goal is to get the client's support team off email threads and into a structured, trackable, AI-assisted service system within the first week.
1
Buffollow · Tickets
Build a structured support pipeline
Navigate to Buffollow → Tickets. Configure the support pipeline: Open → In Progress → Pending Client → Resolved. Create ticket categories that match the client's service model (e.g., Billing, Technical, Delivery, General). Set priority levels (Urgent, High, Normal, Low) and team assignment rules. Train the support team: every customer issue is a ticket — nothing lives in email.
2
Buffollow · Knowledge Base
Build a self-serve support resource
Go to Buffollow → Knowledge Base. Organize articles into categories (Getting Started, FAQs, Billing, Troubleshooting). Write the first 10 articles — these should be answers to the questions the support team gets most often. Each article should include a title, clear answer, and any relevant steps or screenshots. The KB feeds the AI Agent directly: more articles = a smarter AI Agent.
3
Buffollow · AI Agent
Deploy first-line automated support
Navigate to Buffollow → AI Agent. Configure the agent name, welcome message, and escalation prompt ('Would you like me to connect you with our team?'). Train it on the KB articles. Set escalation rules: if the AI Agent cannot resolve the issue in 2 exchanges, it automatically creates a ticket and notifies the assigned support team member. Test every scenario before going live.
4
Buffollow · CSAT
Collect satisfaction data at every touchpoint
Go to Buffollow → CSAT. Configure a post-resolution survey to fire automatically when a ticket is moved to Resolved. Use a 1–5 star rating plus a single open-field comment. Review the CSAT dashboard weekly. Any score of 3 or below should trigger an internal alert and a personal follow-up from a team manager — within 24 hours, not a week later.
5
Buffollow · Loyalty
Build a program that rewards repeat business
Navigate to Buffollow → Loyalty. Define the points structure (e.g., 1 point per $1 spent, bonus points for referrals and reviews). Set redemption tiers and rewards (discount, free service, priority support). Configure enrollment: new customers are auto-enrolled when onboarded via the Closed Won workflow. Show the client how to view the leaderboard and communicate program value to their customer base.
6
Buffollow · Referrals
Build a referral engine that generates pipeline
Go to Buffollow → Referrals. Configure the referral program: unique referral link per customer, reward for the referrer (points, credit, or cash), and a reward or discount for the referred new customer. Set up the confirmation workflow — when a referred prospect converts to a customer, the referral reward is triggered automatically. Show the client where to find the referral link to share with their best customers.
7
Buffollow · Service Voice Agent
Deploy an AI phone agent for customer service calls
Navigate to Buffollow → Service Voice Agent. Configure the AI phone agent that handles inbound customer service calls — name it, set its persona, and define its core purpose: de-escalating frustrated callers and making every customer feel valued before a human is ever involved. Set the escalation threshold (e.g., after 2 failed resolution attempts, transfer to live support). Configure guardrails — the agent should never make promises about refunds or compensation; it should always escalate those. Test with sample scenarios covering common complaints before going live. This agent runs 24/7 and ensures no service call goes unanswered.
8
Buffollow · Scheduled Services
Configure recurring service scheduling for repeat customers
Go to Buffollow → Scheduled Services. Set up recurring service schedules for clients on maintenance plans or subscription-based service agreements. Define the service frequency (weekly, monthly, quarterly), assign the service type, and configure automated reminder notifications to both the customer and the field team before each scheduled visit. This is particularly powerful for home services businesses — lawn care, HVAC maintenance, pest control — where recurring appointments are the core revenue model. Automating this removes the manual scheduling burden and ensures no recurring customer falls off the calendar.
9
Buffollow · Survival Guides
Build post-service content that retains and re-engages customers
Navigate to Buffollow → Survival Guides. Create structured post-service content packages — educational guides, care instructions, warranty information, and follow-up tips — that are automatically delivered to customers after their service is completed. These are not generic newsletters: they are service-specific guides tailored to what was just done. A roofing client gets a roof maintenance guide. An HVAC client gets a seasonal maintenance checklist. A carpet cleaning client gets a care and stain prevention guide. Survival Guides reinforce the value of the service, position the business as an expert, and naturally lead into re-booking prompts. Build one guide per service category the client offers.
10
Core · Workflows
Automate the post-sale service journey
Navigate to Core → Workflows. Build the key Omni-Service automations: (1) Closed Won → trigger customer onboarding sequence (welcome email, onboarding checklist, first check-in call). (2) CSAT score 4–5 → send Google review request 24 hours later. (3) CSAT score 1–2 → create escalation ticket and notify manager immediately. (4) 90 days post-close → send loyalty program re-engagement email. These automations run without manual intervention.
Section 04
Client Progress Milestones
Omni-Service milestones track infrastructure adoption and early retention signals. The goal is to have service systems fully operational within 21 days so no new customer slips through the cracks.
| Checkpoint | Client Should Have... | X Team Should Have... |
|---|---|---|
| Day 14 | Support team trained and working tickets inside Buffollow. No support requests being handled over personal email. | Buffollow live with full configuration. KB published with 10+ articles. AI Agent trained and live. CSAT automation active. |
| Day 30 | First CSAT scores received and reviewed. Responding to sub-4 CSAT scores within 24 hours. Loyalty program communicated to existing customer base. | First CSAT report delivered. Onboarding workflow tested with at least one real new customer. Referral program configured and live. |
| Day 60 | Referral program actively promoted to top customers. CSAT average of 4.0+ achieved. First referral-sourced lead documented. | CSAT trend data reported. KB updated based on most common ticket categories. Review request workflow producing new Google/Yelp reviews. |
| Day 90 | Service operating entirely inside WundertreOS. CSAT data being used to identify service improvement opportunities. Referral program generating at least 2 new leads per month. | Full retention report delivered — churn rate, CSAT average, referral-sourced revenue, review count growth. Client approved to activate Omni-Tracking. |
Section 05
KPIs & Success Metrics
Omni-Service KPIs measure customer satisfaction, retention, and the referral engine's early performance. These metrics directly reflect the health of the client's revenue base.
| Metric | Minimum Bar | Target | How to Measure |
|---|---|---|---|
| CSAT Score (avg. survey rating) | 3.8 / 5 | 4.5 / 5+ | Buffollow → CSAT Dashboard |
| First Response Time (support tickets) | Under 4 hours | Under 1 hour | Buffollow → Tickets → Avg. Response |
| Ticket Resolution Time (avg.) | Under 3 days | Under 24 hours | Buffollow → Tickets → Avg. Resolution |
| AI Agent Deflection Rate | 30% of tickets | 60%+ of tickets | Buffollow → AI Agent → Deflection Rate |
| Customer Churn Rate (monthly) | Under 8% | Under 3% | LeadSprout → Closed Lost (churn tag) |
| Review Count Growth (monthly, all platforms) | +3 reviews/month | +8 reviews/month | MarketBOOST → Reputation |
| Average Review Rating | 4.2 stars | 4.7+ stars | MarketBOOST → Reputation |
| Referral-Sourced Leads (monthly) | 2 leads/month | 6+ leads/month | Buffollow → Referrals → Leads Generated |
| Loyalty Program Enrollment Rate | 40% of new customers | 80%+ of new customers | Buffollow → Loyalty → Enrollment |
| NPS (Net Promoter Score) | 25 | 50+ | Quarterly NPS survey via WundertreOS |
Section 06
Common Mistakes & How to Avoid Them
Mistake 01
Setting up loyalty and referral programs after you have customers
Most clients want to wait until they have 'enough' customers to justify building a loyalty or referral program. But the best time to enroll someone is the moment they become a customer — when their excitement and satisfaction is highest. Late enrollment means you missed the window.
How to Avoid It
Build the loyalty and referral programs during the Omni-Service configuration sprint, before any new customers close in Omni-Narrative. Configure the Closed Won workflow to enroll the customer automatically. Their first post-purchase experience should include an introduction to the loyalty program — not an afterthought six months later.
Mistake 02
Ignoring CSAT data
CSAT surveys go out, scores come back — and nobody looks at them. They sit in a dashboard unloved while service quality quietly deteriorates. The client discovers they have a problem when they start losing customers, not when they can still fix it.
How to Avoid It
Build a weekly CSAT review into the client's rhythm — 10 minutes every Monday morning. Any score under 4 gets a personal follow-up from a team lead that same week. CSAT data should drive KB article creation: if the same complaint appears twice, there should be a KB article and an AI Agent response covering it.
Mistake 03
Treating support as a cost center instead of a retention tool
Clients who view support as 'just answering complaints' under-resource it, under-prioritize it, and fail to see the connection between support quality and revenue. Every support interaction is a retention event — or a churn event.
How to Avoid It
Frame every support metric in revenue terms. A 5% churn reduction is worth X in annual recurring revenue — calculate it. A single referral from a well-served customer has a CAC of near zero. Present CSAT scores alongside revenue retention figures in monthly reports so the client sees the financial connection directly.
Mistake 04
Building a KB no one can find
The KB gets 10 articles published, the AI Agent references them in chat, but no customer ever finds them independently. It becomes a support tool only — not a self-serve resource that deflects tickets and reduces workload.
How to Avoid It
Embed the KB link prominently: in onboarding emails, in the email footer, on the website, and as the first response in the AI Agent widget. Every support ticket resolution email should include: 'You can find more answers at [KB link].' Track KB article views monthly and expand the articles with the highest search demand.
Section 07
Omni-Service Activation Checklist
All items must be verified before the client activates Omni-Tracking.
Support Infrastructure
Buffollow support pipeline configured with categories and priority levels
Support team trained — all tickets handled inside Buffollow (not personal email)
Knowledge Base live with 10+ articles, organized by category
AI Agent configured, trained on KB, and live on website or chat widget
Service Voice Agent configured, tested, and live on client phone number
Scheduled Services configured for all recurring service types
Survival Guides built for each service category and automation triggers set
CSAT survey automation active — fires on ticket resolution
Escalation workflow active — low CSAT triggers manager alert and follow-up task
Loyalty & Referral
Loyalty program configured — points structure, tiers, and rewards defined
Loyalty enrollment automated via Closed Won workflow
Loyalty program communicated to existing customer base
Referral program configured — unique links, reward structure, confirmation workflow
Referral program promoted to top 20% of existing customers
First referral-sourced lead documented
Reviews & Reputation
Review request workflow active — 4–5 CSAT triggers Google review ask
Review response SLA agreed with client (target: respond to all reviews within 48h)
Review count and average rating baseline documented
Reporting & Handoff
Monthly retention report template live (CSAT, churn, reviews, referrals)
NPS survey configured and first send scheduled
Client can pull CSAT and ticket data independently from Buffollow
Service metrics reviewed alongside revenue figures in monthly report
Omni-Service → Omni-Tracking transition meeting scheduled
Omni-Tracking Is Ready to Activate
Omni-Service is complete when the client's service systems are operating independently inside WundertreOS, CSAT scores are above 4.0, and at least one referral-sourced lead has been generated. Omni-Tracking ties every tenet together into a unified revenue intelligence system, so the machine can be measured, optimized, and fed back into itself.