Stop losing signals.
Put every real inquiry, question, reply, and objection in one visible place before adding tools.
Mission outcome
At the end of this manual, you will have:
- One customer tracker.
- One inquiry triage rule.
- One objection library.
- One proposal snapshot.
- One follow-up rhythm.
- One proof-capture checklist.
- One communication safety lock.
Learn from the market.
Capture exact customer words, sort objections, draft next steps, and improve offers from repeated language.
Build review-only customer ops.
Use AI to summarize, classify, draft, and remind — while humans approve every customer-facing action.
Customer tracker
Signal, person, problem, fit, next step, follow-up, and proof.
Objection library
Raw market language grouped by price, trust, timing, complexity, DIY, and doing nothing.
Proposal snapshot
One-screen scope, promise, boundaries, first deliverable, review points, and next decision.
Source rule
No signal, no demand claim.
Every customer action starts from a real signal: form fill, reply, call note, comment, diagnostic result, referral, inquiry, or delivery question. If there is no real signal, label it as a hypothesis.
10-year-old mode
Customers are people who might need help.
Write down who they are, what they asked, what they need next, what you promised, and when to follow up. AI can organize notes. A person approves every message.
From Guide 05
Bridge useful content into customer operations.
When a content asset, lead magnet, guide section, email draft, or proof block creates a real response, use the bridge pack before any follow-up. It turns the signal into a customer tracker row, objection/proof request, proposal snapshot, and human-approved follow-up plan.
Content asset
Name the post, email, guide, worksheet, proof block, or local file that created the signal.
Exact market language
Capture the reply, question, objection, or proof request before polishing it into copy.
Human-approved next step
Draft the tracker row and follow-up locally. No auto-send, no live CRM writes, and no customer-facing action without approval.
Guide 06 → Guide 07 bridge
When a proposal becomes a promise, turn it into delivery work.
The Delivery Bridge Pack converts one approved customer/proposal commitment into a Guide 07 fulfillment checklist, handoff note, revision boundary, proof-capture request, and SOP update. It stays local and review-only: no sending, publishing, CRM writes, live customer-system action, checkout, analytics, account work, or deployment.
Start from approved scope
Use the proposal snapshot and customer words to write one plain delivery promise and done condition.
Make the work visible
List inputs, work blocks, QA checks, human review, handoff, and revision boundary before AI assists.
Capture the lesson safely
Request proof only with permission, remove private details, and save the repeatable SOP improvement.
Customer tracker
Seven lanes keep customer work visible.
Where did interest appear?
Form, email, DM, comment, call note, diagnostic, referral.
Who is this?
Name, role, business/context, and decision power if known.
What hurts?
Capture their exact words before translating.
Can you help?
Good fit, maybe later, unclear, or no fit.
What helps now?
Question, call, proposal, resource, or no-fit reply.
When and why?
Use real reasons, not pressure.
What did we learn?
Objection, quote, result, testimonial permission, or guide update.
Source signal
Where did this inquiry or conversation come from?
Customer words
What exact words did they use for the pain?
Fit status
Good fit, maybe later, unclear, or no fit?
Next helpful action
What is the smallest honest next step?
Approved message
What reply or proposal should a person approve?
Proof / lesson
What can improve the offer, FAQ, content, or delivery?
Intermediate workflow
Turn every signal into learning.
Capture the signal
Save the real source and exact customer language.
Sort the request
Question, objection, price, trust, timing, fit, proposal, or proof request.
Draft the next step
AI may prepare. Human reviews before sending.
Save proof and follow-up
Record the outcome, objection, and useful next date.
Advanced workflow
Build review-only customer ops.
Create statuses for new signal, needs reply, waiting, proposal sent, follow-up due, won, lost, no fit, and proof captured. Give AI only approved local notes and named draft actions: summarize, extract objection, draft reply, draft proposal snapshot, suggest FAQ update, and create local files.
Draft-only AI customer loop
AI prepares customer work. Humans approve customer contact.
ReadApproved local notes and real signals.
ExtractCustomer words, objection type, fit, and next step.
DraftReply, proposal snapshot, FAQ, reminder, or tracker row.
ReviewHuman checks truth, tone, privacy, promises, and safety.
Inquiry triage
Five questions before a proposal.
- Can we name the problem in the customer's words?
- Is the problem urgent or expensive enough to matter?
- Is the buyer allowed to decide or influence the decision?
- Do we have a small next step that helps without overpromising?
- Is every public/contact/payment/account action behind human approval?
Objection library
Market language beats guesses.
Objection
Capture
Use it to improve
Price
“That feels expensive because…”
Proof, scope, or payment options.
Trust
“How do I know this works?”
Samples, proof blocks, FAQs.
Timing
“Not right now.”
Trigger events and follow-up rhythm.
DIY / ChatGPT
“Can I just do this myself?”
Show artifact, process, and safety gates.
Doing nothing
“We are fine for now.”
Explain leakage only when truthful and specific.
Proposal snapshot
Fit the first proposal on one screen.
Problem
Use the customer's words. “Leads are coming from everywhere and nobody knows who followed up.”
After-state
One visible lead map, owner review rhythm, and safe AI draft loop.
Scope
Included: workflow map, tracker, follow-up checklist. Not included: CRM migration, outbound sending, paid ads.
Next decision
Approve the small audit/setup step, or choose the no-fit resource.
Bad follow-up
Do not pressure people.
- No fake urgency.
- No mass scraping.
- No automated cold DMs.
- No sending when there was no real signal.
- No pretending AI knows what the customer wants.
Good follow-up
Tie it to a real reason.
- Promised resource.
- Proposal answer due.
- Missing information.
- Customer-requested reminder date.
- Post-delivery proof or result check-in.
- Referral/testimonial request after a good outcome.
Ready to handle customers?
You are ready when every signal has a visible place, every reply is human-approved, and every objection becomes learning.
Ready. Begin Manual 06.
Preparation is safe. Customer contact is risk.
AI may summarize, organize, classify, draft, score, route, remind, and create local draft files. Human approval is required before sending, DMing, calling, posting, contacting, changing live CRM/account records, quoting final terms, accepting payments/contracts, or publishing proof.
- Never invent testimonials, results, screenshots, logos, or revenue.
- Never use names, quotes, screenshots, numbers, or client details without permission.