Look inside the finished work.
Read a complete procedure, inspect cleaned records, and try a request-routing example. These samples show deliverable formats, not customer results or guaranteed outcomes.
From a new inquiry to a clear next action.
Fictional company: Northstar Office Care · SOP OPS-001 · Version 1.0 · 26 September 2026
Before you begin
Use the approved intake inbox and customer tracker. You need the original inquiry, the service list and the current approved response templates. Do not request payment details or passwords in the inquiry record.
- Capture the original request. Create a record ID and record the received date, customer-provided name, reply address and requested service. Keep the original message linked to the record.
- Check for an existing record. Search by email and request reference. Link a repeat inquiry to its earlier record; do not overwrite a different request.
- Check the minimum information. Confirm that the request states the service, location and preferred timing. Mark missing details explicitly; do not guess.
- Choose the next action. Route a complete standard booking inquiry to Scheduling, a quote request to Sales Review, and a billing question to Financial Admin. Use Owner Review for anything outside the service list.
- Prepare the response. Draft from the approved template and verified facts. If information is missing, request only that information. No new price or delivery promise may be added.
- Assign accountability. Select the responsible queue and due date. Use the next business day as this fictional team's internal review target, not a promise to the customer.
- Review before any external action. The authorized reviewer checks the recipient, source facts, scope and proposed message. An incomplete or unusual request remains on hold.
- Record the outcome. Save the approved next step, review date and reviewer. Close this intake task only when the next owner has accepted it; keep the service task open until its own completion criteria are met.
Exceptions & escalation
- Missing service address: mark “Needs information”; do not schedule.
- Conflicting customer records: preserve both sources and ask the reviewer to resolve them.
- Complaints, refund requests or unfamiliar scope: refer to the business owner without promising a resolution.
- Unavailable system: keep the inquiry in the approved inbox and record the interruption; never copy it into a personal account.
Acceptance checklist
Record ID present · source linked · duplicates reviewed · service classified · missing details flagged · owner and due date set · external action approved · handoff recorded.
Example completed handoff
DEMO-001 — Avery Cole: office-cleaning quote requested; location and preferred timing supplied; assigned to Sales Review; next action “review requirements and prepare quote”; no message sent.
From inconsistent rows to a usable tracker.
A fictional US-date-format source contains 10 rows representing 8 records. The clean version removes two duplicate records after normalization, trims spaces, standardizes approved service names and formats dates as YYYY-MM-DD. No missing address is invented.
8 cleaned records · 2 duplicate rows removed
| Record ID | Customer | Service | Next action | Due date | |
|---|---|---|---|---|---|
| F001 | Avery Cole | avery@northstar.example | Window cleaning | Confirm appointment | 2026-10-02 |
| F002 | Jordan Lee | jordan@pine.example | Office cleaning | Review quote | 2026-10-03 |
| F003 | Morgan Reed | morgan@cedar.example | Window cleaning | Request missing address | 2026-10-03 |
| F004 | Taylor Kim | taylor@maple.example | Office cleaning | Confirm appointment | 2026-10-05 |
| F005 | Riley Brooks | riley@lake.example | Floor care | Review quote | 2026-10-05 |
| F006 | Casey Park | casey@birch.example | Floor care | Confirm appointment | 2026-10-06 |
| F007 | Jamie Diaz | jamie@elm.example | Window cleaning | Review quote | 2026-10-07 |
| F008 | Alex Rowan | alex@oak.example | Office cleaning | Confirm appointment | 2026-10-07 |
| Record ID | Customer | Service | Next action | Due date | |
|---|---|---|---|---|---|
| F001 | avery cole | AVERY@NORTHSTAR.EXAMPLE | Window cleaning | Confirm appointment | 10/02/2026 |
| F002 | Jordan Lee | jordan@pine.example | office CLEANING | Review quote | 2026-10-03 |
| F003 | Morgan Reed | morgan@cedar.example | Window cleaning | missing address | 2026-10-03 |
| F004 | Taylor Kim | taylor@maple.example | Office cleaning | Confirm appointment | 2026-10-05 |
| F005 | Riley Brooks | riley@lake.example | Floor care | Review quote | 2026-10-05 |
| F006 | Casey Park | casey@birch.example | Floor care | Confirm appointment | 2026-10-06 |
| F007 | Jamie Diaz | jamie@elm.example | Window cleaning | Review quote | 2026-10-07 |
| F008 | Alex Rowan | alex@oak.example | Office cleaning | Confirm appointment | 2026-10-07 |
| F001 | Avery Cole | avery@northstar.example | Window cleaning | Confirm appointment | 2026-10-02 |
| F004 | Taylor Kim | taylor@maple.example | Office cleaning | Confirm appointment | 2026-10-05 |
Quality checks: 10 input rows = 8 retained + 2 duplicates. Record IDs are unique after cleanup. Every retained email is traceable to the source. Morgan's missing address remains a follow-up action.
Try a request-to-owner handoff.
This browser-only demonstration uses three fixed fictional requests. It does not contact a CRM, save customer data or send messages.
Explore intake & classification · $1,500, scope confirmed first →