Escalation Email Wording
Proposed — pending review
The email a property manager reads under time pressure, rebuilt against the nine
rulings from 14 Aug. Everything below is the real render — the page calls the
production builders, it does not imitate them. The code change is held and will not ship
until the design pick below is made.
The pick — does the email carry a mark?
B. Small mark at the bottomRecommended
A 96px PropFlow mark under a hairline, below the signature — the size and place a person’s company logo sits in their own signature block.
A. No mark at all
An email with nothing on it but the note and the signature. Indistinguishable from mail a colleague typed.
Why B. The mark is the only thing telling a manager six months from now which system this thread lives in — and at signature size, under the sign-off, it reads as the sender’s employer rather than as a product banner. A carries a real cost: an unmarked email is one nobody can trace back when they need to. The old card-and-letterhead design is not on the list; it is the look this whole change exists to end.
Same email, same words, both times. The only question is whether a small PropFlow logo sits under the signature, the way a person’s company logo sits under theirs. Pick B and anyone can tell where the email came from; pick A and it looks like it came from a person with no company at all.
B on a phone
The same render at 390px — where most of these get read.
What changed — the same escalation, before and after
Eleven escalations at Camellia all arrived looking like the left-hand email:
the same subject shape, a banner, five labelled fields, and a Message: block
that pasted whatever raw text was nearby — a website form dump here, tour chatter from
weeks earlier elsewhere, raw voice filler (“Sure. Yeah. No, yeah, for sure…”) on the
phone cases, and the literal string “(no message body)” when the thread was empty.
The nine rulings, and how each one is satisfied
| Ruling | What you said | How the email answers it |
|---|---|---|
| 1. No daily-chase line | reacting to “Who’s fixing the lease… I’ll keep checking in daily until someone takes it” — “ill keep chaging daily” | That sentence is deleted, and so is the second closing it lived in. Every escalation email now ends the same way — first ask or fifth. Clara still follows up on her own cadence; she just doesn’t put a chase schedule in writing. A test fails if the words come back. |
| 2. Professional corporate coworker (corrected 08-14 eve) | Original: “professional blue collar coworker”. Fede corrected while reviewing this page: the persona is a professional corporate coworker. | Professional, direct sentences; no filler pleasantries that don’t carry information. The email says who is asking, what they asked, and that a reply finishes it. |
| 3. Peers, matched to real roles | “think a leasing professional, accounts payable, recievable, property manager, assitant property manager are peers and we want specialized agetnst that match those human roles” | The email is written to the property manager as an equal: no “forwarded for your review”, no reporting-upward framing. (Corrected 08-14 eve: the signature carries name + property only, no department — Clara is not just leasing; she spans leasing, renewals, and tenant questions.) |
| 4. Everyone on the team, no routing | “for now keep it simple its cc to everyone” | Unchanged on purpose: the escalation goes to the one property-team address already on the property record. No routing logic was added, and no address is ever guessed. (Rollout, Fede 08-14 eve: ship additively — every alert Camellia gets today keeps flowing unchanged, and the new escalation email runs in addition, with fede@propflowai.co as its only recipient for a few days of live testing before switching to the team address.) Role-aware escalation stays future direction. |
| 5. A regular human’s signature | “signature should be like a regular human” | “Clara / Camellia Apartments” — name and property, read off the property record; no department line (Fede, 08-14: “Clara is not just leasing”). “— Clara” is gone from both escalation emails; so is every banner and any “AI assistant” framing. |
| 6. Show me designs without the logo | “consider alternative designs without a propflow logo and it looks like a coworker sent it with a signature / maybe logo in the bottom smaller” | Both are built and rendered below — that is the pick at the top of this page. The card-on-gray-background shell with a letterhead is gone either way: that is the look of a system notification. |
| 7. Scan in 30 seconds, reply briefly | “yo ushould be able to scan in 30 secs and reply briefly” | The subject IS the question, so the inbox list alone is enough to triage. The body is four blocks and never more: who, the ask, what a reply does, signature. A one-line reply finishes the loop. (08-14 eve: Fede answered the closing-line question below — emphasize that replying is all it takes, “but dont over do it”: one plain closing line, “Just reply to this email and I’ll take it from there.” Also: bold used the way professional humans use it — i.e. almost never; the corpus counted bold twice in 8,083 staff messages.) |
| 8. Only critical detail | “only critical detail no fluff or over explaining” | Cut: the five-field header block, the raw message dump, the “why forwarded” paragraph, and “and I’ll remember it for next time” — true, but it doesn’t change the answer the reader is about to type. |
| 9. To the point, direct, precise | “to the point” / “direct precise” | Exact dates, units and dollar figures survive verbatim; hedging and throat-clearing don’t. The matter-lane email lost its “Quick one —” opener for the same reason. |
Ruling 3 also set product direction beyond this email — specialized agents matching real property roles, and escalation that knows when to go to the regional manager rather than the property team. That is recorded, not built here.
All five real escalations, rebuilt
The five Camellia escalations that broke the old template in five different ways. Contact details are fictional.
A policy question Clara didn't have on file
A lease-document error, asked again after silence
Two confirmations before signing
A request that needs a business decision
A voice call whose transcript was the old "Message:" block
The other staff email, so the two sound like one person
A second escalation email exists: when a property has named an owner for open questions, Clara also opens a tracked matter and asks that person directly. It used to be plain text with no design at all, so two emails about one escalation looked nothing alike. It now signs the same way, closes the same way, and renders in the same shell.
The one deliberate difference is “or ask me anything you need first”. That lane has a handler that actually answers a question back; a reply to the property-team email lands in a mailbox and is read by a person, so the same invitation there would be a promise Clara can’t keep.
Anything still reading wrong?
Optional — only if a sentence above still bothers you. Pick one and the template changes to match.
The email is four short pieces: who is asking, the question, one line saying “just hit reply”, and the signature. These options each remove or add one of those pieces. Doing nothing ships it as shown.
What is proven, and what is not
- Proven. Every email on this page is the output of the production builders, rendered by the same code that sends. 45 pinned examples cover the five real escalations, the fallbacks (no summary, voice fragments, several questions, an empty thread), both design variants, and a hard budget on the shape so a future “one more helpful line” fails a test instead of a review. The second staff email has 19 more, and the guard that recognises our own mail coming back has 12.
- Proven earlier, on the test property. The previous wording went out end to end through the real send path at The Willows and was read back out of the mail server — no re-rendering. That run predates these nine rulings.
- Not yet re-run. The live test property is in use by another job right now, so the end-to-end run against the NEW wording has not happened. It runs before this merges.
Held draft — nothing here is live. Once the pick above is made, the end-to-end run goes first and the change ships behind it.