FiskWiseFiskLens
Demo · sample data

  1. Message 01Leak
  2. Message 02Text
  3. Message 03No unit
  4. Receipt

Case file · morning inbox

Oakline FiskLens

Take the office manager’s chair at fictional Oakline Property Management. Three maintenance messages are waiting, and every call is yours.

About a minute · 3 decisions · nothing is sent anywhere

The full walkthrough is written out below. Nothing here is sent anywhere.

  • EmailSink leak, Unit 4B
  • Text“did anyone get my email??”
  • VoicemailHeater noise. Which unit?

Message 1 of 3 · Email

A sink leak, unit named

Incoming email

EmailFrom Marisol T.

Hi, the kitchen sink in Unit 4B at Maple Court is leaking under the cabinet. It started last night and there’s a small puddle, so I put a bucket under it. I’m home after 3 today. Thanks, Marisol

FiskLens · facts pulled from the email

One ticket · OAK-1042

Issue
Leak under kitchen sink
Unit
4B · Maple Court
From
Marisol T. · email on file
Access
“Home after 3 today”
Urgency
A person decides
Vendor
A person decides

Draft reply · not sent

Hi Marisol, thanks for letting us know. We’ve logged the leak under the kitchen sink in Unit 4B as request OAK-1042. Our office will review it and be in touch about next steps.
Oakline Property Management
  • No arrival time
  • No repair promise
  • Not sent

Approved · simulated

Held for review

Approve this reply? Simulated · nothing is sent

If the manager approves: Approved, as a simulation. Nothing was sent. Ticket OAK-1042 is logged; urgency and vendor are still yours to set.

If the manager holds it: Draft held for your review. Ticket OAK-1042 is logged and nothing goes out until you say so.

Message 2 of 3 · Text

The same leak, by text?

Incoming text message

TextMobile on file for Marisol T.

its marisol in 4B. sink is still dripping under the cabinet, did anyone get my email??

FiskLens · possible match, not merged

Evidence for OAK-1042

EmailText
Unit4B4B
IssueLeak under kitchen sinkSink dripping under cabinet
SenderMarisol T., email on fileMarisol, mobile on file
Time8:12 AM8:47 AM

Unit, issue and sender line up, 35 minutes apart. Nothing merges until a person says so.

Original ticket · OAK-1042

Leak under kitchen sink, Unit 4B. Opened from the 8:12 email. Its confirmation was approved or held by the manager.

  • No second work order
  • Not sent

Linked · 1 work order

Manual review · not linked

Same request as OAK-1042? Simulated · nothing is sent

If the manager links it: Linked. The text now sits on OAK-1042 beside the email. Still one work order.

If the manager declines: Not linked. The text goes to manual review. No second work order was created and OAK-1042 is unchanged.

Message 3 of 3 · Voicemail

A heater report, no unit

Incoming voicemail, transcribed

VoicemailCallback number provided

Hi, it’s Devin. The heater in my hallway is making a loud banging noise and there’s no heat coming out. Can someone take a look? You can text me back at this number. Thanks.

FiskLens · a fact is missing

No ticket yet

Issue
Heater banging, no heat
Caller
“Devin” · number not on file
Unit
Not stated · not guessed
Dispatch
Blocked until a unit is confirmed
Urgency
No heat can be urgent. A person decides.

Draft text back · not sent

Hi Devin, this is Oakline Property Management. We got your voicemail about the heater. Which unit are you in? We’ll log your request as soon as we have it.
  • No guessed unit
  • No dispatch
  • Not sent

Unit requested · simulated

Held · manual follow-up

No unit. What now? Simulated · nothing is sent

If the manager asks: Unit request approved, as a simulation. Nothing was sent. No work order and no dispatch until a unit is confirmed.

If the manager holds it: Held for manual follow-up by a person. No work order, no dispatch, no guess.

Morning inbox · 3 messages reviewed

Your intake receipt

Oakline morning inbox
Case receipt

Demo · sample data · simulated actions

  1. 8:12 · EmailSink leak, Unit 4B. Ticket OAK-1042 opened. Confirmation approved (simulated)Confirmation held for review
  2. 8:47 · TextText about the Unit 4B sink. Linked to OAK-1042. No new work order.Sent to manual review. No new work order.
  3. 9:05 · VoicemailHeater report, no unit given. Unit requested (simulated). No dispatch.Held for manual follow-up. No dispatch.

This run · actual counts

Messages handled
3
Work orders opened
1
Linked to an existing ticket
0
Drafts you approved
0
Held for a person
0
Units guessed
0
Really sent or dispatched
0

Decisions made by you: 3 of 3

Intake reviewed · demo

Restarting clears every choice.

The takeaway

What this shows

The version to pass along: FiskWise does the reading, retyping and matching. A person keeps every judgment call. FiskLens shows where that split would help in one specific business.

Automated

  • Pull the facts from a message into one ticket
  • Draft a reply with no promises and no invented ETA
  • Lay out the evidence for a possible duplicate
  • Flag what’s missing instead of guessing

Stays with a person

  • Approving anything that goes out
  • Judging real-life urgency
  • Choosing and dispatching vendors
  • Deciding whether two messages match

What FiskLens produces

  1. A map of your actual workflow, step by step
  2. Measurements of the retyping and the waiting
  3. A ranked list of fixes
  4. One pilot, with an approval step built in
  5. A results check after 30 days

Illustration only · invented figures

84 requests a month× 4.5 minutes avoided each= 378 minutes= 6.3 hours a month

Not guaranteed savings and not a client result. It is separate from the three messages in this demo.

Open the sample intake FiskLens reportSample intake FiskLens reportFictional Oakline · stays on this page

Sample · Oakline Property Management (fictional)

1 · Trace: the map

  1. A message arrives by email, text or voicemail
  2. Someone reads it and types it into a work order retyping
  3. Duplicates are caught from memory waiting
  4. A reply is typed from scratch retyping
  5. Missing details are chased by phone waiting
  6. A person sets urgency and picks a vendor

2 · Measure: retyping and waiting

  • How often the same facts are typed again
  • How long a request sits before its first reply

3 · Decide: ranked fixes

  1. Draft one ticket for a new request once its unit is known
  2. Possible duplicates shown with their evidence
  3. Ready-to-approve “which unit?” replies

4 · Build: one pilot

Start with new requests that identify a unit. The manager reviews possible duplicates and missing details, and approves every reply before it goes out.

5 · Verify: the 30-day check

Measure the retyping and waiting again against the starting map, then keep, adjust or drop the fix.

Try this week: for five working days, make a tally mark each time a request is retyped or sits waiting on a reply. That tally is the first page of your own map.