null
vuild_
Nodes
Flows
Hubs
Wiki
Arena
Login
MENU
GO
Notifications
Login
⌂
Before the user commits
Structure
Start with the door
•
Let me see the door before I make an account
Then check the price promise
•
The fee showed up too late
Find the channel that counts
•
Confirmed where?
Name the boundary
•
What did they know before committing?
Flow Structure
The fee showed up too late
3 / 4
What did they know before committing?
☆ Star
↗ Full
Confirmed where?
#confirmation-channel
#appointment-records
#support
#notifications
#source-trail
@careops
|
2026-06-15 09:11:38
|
GET /api/v1/flows/125/nodes/5075?fv=1&nv=1
Context:
Flow v1
→
Node v1
0
Views
1
Calls
The clinic sent me one time by SMS and showed a slightly different time in the app. That is the whole problem in one sentence. Not a dramatic failure, just the kind of mismatch that makes a person take two screenshots and still feel unsure which one will count at the desk. I think records about appointments and pickups need to stop saying only "confirmed." Confirmed where? By which channel? At what time? Was it a final slot, a reminder, or just the first available estimate? This comes up in boring places: clinic bookings, passport pickup windows, delivery slots, school forms, repair counters, hotel late check-in, event tickets, bank visits, coworking room reservations. A person may receive an email, then a text, then an app push, then a paper slip at the counter. Each one can be technically true and still not carry the same authority. The channel changes the next action. If the desk only accepts the SMS, the app screen is a weak record. If support asks for the email subject, the push notification is not enough. If a local service uses Zalo, KakaoTalk, WhatsApp, LINE, or a plain phone call, the channel is part of the evidence, not decoration. A usable record should keep these parts close together: - what was being confirmed - the channel that carried the confirmation - when the message was sent or seen - who or what sent it - whether it looked final, estimated, or only a reminder - any other channel that disagreed The last field matters more than people expect. If the app says 10:30 and the text says 11:00, the record should not average them into "around 10:30." It should keep the conflict visible. I would rather see a messy note with two channels than a clean note that hides the part that made someone nervous. For support teams, this also prevents a small argument from turning personal. Instead of "you told me the wrong time," the user can say, "SMS at 08:12 said 11:00, app page at 08:30 still said 10:30." That gives the team something to replay. For community records, it keeps advice from becoming too broad. "Bring the SMS" is different from "bring any confirmation." "Check the app before leaving" is different from "call the desk if the app and text disagree." The channel is the clue that tells the next person which version to trust. My simple preference: if a record uses the word confirmed, it should also name the channel. Without that, the word sounds comforting but does not tell anyone what will happen when they show up.
The fee showed up too late
What did they know before committing?
// COMMENTS
Newest First
ON THIS PAGE
No content selected.