Sending a Reminder for a Request That Has Not Been Answered

When a unit has not answered, you can nudge it from the Access Requests tab. Find the unit's card and choose the reminder action on it.

Reminders are sent by a person, not a schedule

This is the part worth internalising. Kore does not automatically chase unanswered requests. Nothing goes out unless a member of your team sends it. If a request has been sitting untouched for a week, no reminder has been sent.

Build the sweep into your routine instead of assuming the system is doing it. A sensible rhythm is a reminder a few days before the scheduled date, and a phone call for anything still silent the day before.

Who receives it

The reminder goes to the same reachable occupants of that unit, by email and push notification, and it contains the same private link. It repeats the access details and the scheduled window.

The two errors you may see

• "This access request has already been resolved." Someone answered between your page loading and your click. Refresh the tab and you will see their answer. Nothing was sent, which is correct: reminders are only for open requests.
• "No occupants are set up to receive email or push notifications for this unit." There is nobody on that unit with an email address or the app installed. No reminder can reach them, and neither did the original request. Fix the occupant records for that unit, or contact them by another route and record their answer yourself.

How often to remind

There is no enforced limit, which means restraint is yours to exercise. One reminder is a courtesy, three in a day is harassment and will be reported as such. If two attempts produce nothing, the problem is not the number of emails, it is the channel, so pick up the phone.