Skip to main content
FICTIONAL DEMONSTRATIONS · NO CLIENT DATA

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.

SAMPLE 01 · STANDARD OPERATING PROCEDURE

From a new inquiry to a clear next action.

Fictional company: Northstar Office Care · SOP OPS-001 · Version 1.0 · 26 September 2026

Purpose
Record every new service inquiry consistently and assign an accountable next step.

Owner
Operations coordinator. The business owner approves unusual scope, pricing and exceptions.

Starts / finishes
Starts when an inquiry arrives. Finishes when a reviewed record has an owner, due date and status.

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.

  1. 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.
  2. 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.
  3. Check the minimum information. Confirm that the request states the service, location and preferred timing. Mark missing details explicitly; do not guess.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.

SAMPLE 02 · CUSTOMER DATA CLEANUP

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

Fictional customer records — not client data
Record IDCustomerEmailServiceNext actionDue date
F001Avery Coleavery@northstar.exampleWindow cleaningConfirm appointment2026-10-02
F002Jordan Leejordan@pine.exampleOffice cleaningReview quote2026-10-03
F003Morgan Reedmorgan@cedar.exampleWindow cleaningRequest missing address2026-10-03
F004Taylor Kimtaylor@maple.exampleOffice cleaningConfirm appointment2026-10-05
F005Riley Brooksriley@lake.exampleFloor careReview quote2026-10-05
F006Casey Parkcasey@birch.exampleFloor careConfirm appointment2026-10-06
F007Jamie Diazjamie@elm.exampleWindow cleaningReview quote2026-10-07
F008Alex Rowanalex@oak.exampleOffice cleaningConfirm appointment2026-10-07

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.

SAMPLE 03 · INTERACTIVE WORKFLOW

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.

Choose a request and run the demo to see its route.

Explore intake & classification · $1,500, scope confirmed first →