When I’m routing an artist, I either spin up five separate inquiries to lock holds quickly (better response rate, but inbox chaos) or bundle all dates into one thread (tidier, but agents miss details and stall). Could we get a proper multi-date offer/hold flow that keeps one conversation but tracks discrete cities/dates with statuses and counters?
Yes - one thread with per‑date cards that track city/date, hold level, offer status, counters, and expiry, with per‑date accept/decline and nudges, would solve the split vs bundle tradeoff. Do you also need per‑date deal terms (fee/split/radius) and independent deadlines, or would a shared header with per‑date overrides cover it?
Same pain here — spinning up five separate inquiries gets faster holds but turns my inbox into chaos. A single thread with per‑date cards (city/date, hold level, offer/counter, expiry) and per‑date accept/decline and nudges would keep context while moving each date independently. A quick per‑date recap/summary in the thread would help agents avoid missing details and stalling.