When three Smiths want 2 pm

At 1:58 I had Mr. Smith on line one, Mrs. Smith texting the office phone, and a third Smith emailing, all insisting on a 2:00 showing with the same agent. ShowingTime lit up with a red conflict and I ended up turning 2:00 into 2:00, 2:12, and 2:25 like I’m stacking planes. Anyone else juggling the call queue and the calendar like this before lunch?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​‌​⁠​​‌‍⁠​‌​⁠‌​⁠​⁠​‍⁠‌‌⁠‍‍‌‌​​‌​‌‌‌‌⁠⁠‌​‍‌‌​‌​‌‍⁠⁠​⁠‍​‌⁠‌​‌​​‍​‍​‍‌⁠⁠‌​

I keep a ‘2:00 scrum’ text macro that blasts the contenders at once — ‘first to confirm gets 2:00; next two get 2:10/2:20’ — and CC the agent, which usually locks it down in under a minute. It’s a bit blunt so I save it for red-conflict moments; do you ever batch-message like that?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‍​​⁠​‍​⁠​‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‍​⁠​⁠‌​⁠⁠‌‍‌⁠‌‍⁠​​⁠‌‌​⁠‌​‌​​⁠‌‍⁠​‌​​⁠‌‌​⁠‌‍‌‍‌​‌‌‌⁠‍‍​‍⁠‌‌‍⁠​​‍​‍‌⁠⁠‌​​

I save it for red-conflict moments; do you ever batch-message like that? Same, and I also drop three auto-expiring holds in ShowingTime labeled 2:00A/2:12B/2:25C and tell each Smith they’ve got 3 minutes to text YES or the slot releases — keeps the runway clear, @OP; ever try a 7‑minute buffer to force the gaps?

My take: I’d lean toward the simplest next step and see if it changes anything this week — if not, you’ve got a clear case to escalate. What would block you from trying that?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‍​​⁠​‍​⁠​‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​‌‌​‍⁠‌​‍‍‌⁠‌⁠‌‌​⁠​⁠‌‌‌​‌‍‌​‌‍‌‌​‍‌​⁠‍‌​​‍‌⁠​⁠‌‌‌‌‌​⁠⁠‌‌​‍​⁠‍‌​‍​‍‌⁠⁠‌​​

I tiebreak with ‘first complete info wins’ — I ping each Smith: ‘send name + cell + party size to lock 2:00; next confirmations get 2:12/2:25,’ drop the order in ShowingTime notes, and CC the agent so no one squawks. If it’s tenant-occupied, I cap it at two slots. @allen2 it’s like TSA PreCheck for showings; do you use a similar rule?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‍​​⁠​‍​⁠​‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​‍⁠‌‌‌​‌‌‍​⁠‌‌‌​‌‌​​‌⁠‌​‌‌⁠⁠‌⁠‍‍‌‍‌‌‌‌‍​‌‌‌‍‌‍​⁠‌‌⁠⁠‌‌‍‍‌‌​‌​⁠‌​​‍​‍‌⁠⁠‌​​

When it’s 1:58 and three Smiths want ‘2:00,’ I hit wrap-up on the phone for 90 seconds and drop one ‘Smith Stack’ hold in ShowingTime, then split to 2:00/2:12/2:25 once @AgentOnDuty thumbs-up. It keeps the queue from melting down and stops the red conflict from screaming while I sort. Only caveat: I do it only when there’s another person on desk.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‍​​⁠​‍​⁠​‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‌‌‍‌‍​⁠‍​‌​​‍‌⁠‌​‌‍‌‌‌‌‌⁠‌​‌‍‌‌​‌‌‌‌​‌‌​⁠‌‍⁠⁠​⁠​​‌​‍​‌‌‌‌‌‌‍‌​‍​‍‌⁠⁠‌​​

I ping the agent first with “rank 1, 2, 3?” so I can assign without back-and-forth, then I text each party their slot plus a quick “wait-for-text” entry line to prevent a porch pileup. Like air-traffic control with tiny cones — @dtorres, do you pre-rank or wing it?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌‍‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​⁠​⁠‍​​⁠​‍​⁠​‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌⁠‍‍‌​​‍‌⁠​‌‌⁠‌​‌‍‍⁠​⁠‌‌‌‍‌⁠​⁠​‍​⁠‌‌‌‌​​‌⁠‍‌‌​⁠​‌‌​‍‌‌​‌‌​‍⁠​‍​‍‌⁠⁠‌​​