Home and your actions

What Home shows

Home shows how today is going: today's events with how many are in, bookings and rentals going out or due back, the last seven days' takings beside the week before, and what's coming up. When something needs you, the most pressing one is the first thing on the page, with a button that opens where you deal with it, and a link to the rest.

Actions: what needs someone

Actions, under Overview in the menu, lists everything across what you run that needs someone, most pressing first: escalated items, then overdue ones, then by when they're due. You see only what your role can act on, so gate staff aren't shown refunds and finance isn't shown proofs. It's different from Notifications: a notification is news; an action stays until it's done.

• Booking and rental requests to decide, and organizers asking to link one of your bookings to their event.
• What can stop an event in the next 60 days: a venue booking that doesn't cover the event's times, setup or teardown, tickets for more people than the space holds, a rental the vendor may not cover, or an order that will arrive late. A venue sees the same about the organizers' events in its bookings.
• Proofs whose print file failed, and proofs waiting for approval.
• Balances due before a production order is dispatched.
• Production orders the partner now promises for after the day you need them, until you accept the new date.
• Rentals past their return that haven't been checked back in, and deposits to claim against before the window closes.
• Cases: renters' deposit disputes (and Durbar support's requests for your evidence), gifts a recipient says didn't arrive, and Studio orders you reported wrong or missing; and graduands' disputes about their records.
• Votes that look unusual, for you to check.
• Refunds the payment provider refused.
• Deadlines: an event starting within a week that's still a draft, a contest about to open that's still a draft, graduands who haven't confirmed before the last day, gift campaigns waiting for approval, and gift kits that may miss their arrival date.
• Messages Durbar couldn't send, such as emails, text messages or invitations.

Each item says why it needs someone, the record and the event or place it belongs to, when it's due and who has it. Its button opens the page where you resolve it. Once it's resolved there (the request decided, the return checked in), the item goes from everyone's list on its own.

Assign, snooze or escalate

1. 1Open the item's menu (the … button).
2. 2Choose Assign to a teammate to give it to someone. Only teammates whose role can act on it are listed. It shows under Assigned to you on their Actions page.
3. 3Choose Snooze to hide it until a time: in 3 hours, tomorrow morning, in 3 days, next Monday, or a time you choose. Say why: your team sees the reason. It comes back on its own, or choose Bring it back now under Snoozed.
4. 4Choose Escalate when it can't wait. It goes to the top of everyone's list, and whoever can act on it is told now, by SMS and email too if they chose that.

Messages that couldn't be sent

Durbar tries each email, text message, refund and round of invitations up to 8 times over several hours. If it still can't, the item says how many couldn't be sent, and owners and admins see it (refunds go to finance). Choose Try again to send them again with a fresh set of tries; anything already sent isn't sent twice.