2Admin + escalations, ENVIE palette
Both admin surfaces are mobile — the day-of team is standing at a venue. 2a merges the two admin ideas: live conversations arrive at the top of the list as they land, with the question tally underneath. 2b is the clock queue, sorted by how long a guest has actually been waiting. Palette and type come from your case study; the flat rules and flush-left structure come from Modernist.
2aAdmin — live conversations arriving on top of the tally. Pause the feed, filter to escalations, tap a row for the transcript.
ENVIE Concierge
Sipho & Naledi
LIVE
{{ s.v }}
{{ s.label }}
What guests keep asking
{{ g.name }}
{{ q.q }}{{ q.n }}
{{ adOpen.guest }}
WhatsApp transcript
{{ m.t }}
2bEscalations — clock queue. Waits tick up in real time; claim a guest, reply, resolve.
ENVIE Concierge
Escalations
{{ ebCount }} WAITING
Sorted by how long a guest has actually been waiting — longest first.
{{ r.guest }}
{{ r.clock }}
{{ r.q }}
{{ r.statusLabel }}
Queue is clear — nothing waiting on a person right now.
{{ ebOpen.guest }}
Waiting {{ ebOpen.clock }}
{{ m.t }}

Try next: "make the tally in 2a collapsible so the live feed fills the screen" · "add a 'nudge the bot' action to 2b" · "show me the couple's post-event report"

1Guest thread, re-skinned
1aGuest WhatsApp thread. Type anything or tap a chip — answers come from the couple's real event record; anything unmatched hands off to a person.
EN
ENVIE Concierge
Sipho & Naledi · 12 Oct
ONLINE
Today
{{ m.t }}
{{ m.meta }}

Try next: "try a 'still typing' delay closer to real WhatsApp" · "add the couple's names to the bot's first message" · "show the escalation as it looks to the guest"