Booking a Meeting on a Rep's Travel Day Is an Easy Mistake

The rep lands at 4pm on Tuesday. The event starts Monday. Someone scheduled a meeting for Tuesday at 2pm.

Nobody planned for it to happen that way. The person who booked the Tuesday 2pm meeting did not know when the rep was arriving. The rep's travel dates were in an email somewhere. The schedule was built in a spreadsheet and there was no field for arrival window. The conflict did not exist on paper. It existed in reality.

The rep either pushes the meeting, takes a call from the airport, or the customer gets notified that the person they were expecting is not going to be there.

The Problem with Manual Availability Tracking

A trade show team is not all arriving the same day. Some fly in Sunday to be there for setup. Some arrive Monday night because they have a client dinner Sunday. Some are presenting Tuesday and flying out Wednesday before the floor closes.

Managing that across a spreadsheet requires a separate column per person, manual updates every time something changes, and someone whose job it is to check all of it before any new meeting gets booked. That person does not exist at most companies. So the check does not happen, and the conflicts land.

How Knowhere Handles It

Every team member in Knowhere sets their availability per event. They enter arrival and departure dates. They mark any time slots within event hours that they are not available for meetings: early flights, dinners, booth coverage shifts, presentation prep. Managers can set availability for team members as well.

Once availability is set, conflict detection respects it. A meeting proposed during a rep's departure window gets flagged. A meeting scheduled for someone who does not arrive until Tuesday afternoon shows as a conflict on Monday. The check runs automatically every time a meeting is created or edited.

Personal Time Blocks

Beyond arrival and departure, team members can block specific time as Personal Time on the schedule: travel, lunch, break, or a custom label. Those blocks protect the slot from scheduling the same way a confirmed meeting does. The rep's lunch hour is not available for a customer to be accidentally booked into.

External Busy Time

If a team member has an outside commitment that is not in Knowhere, an investor dinner, an internal sync, a call that runs over, they can forward the calendar invite to their personal Knowhere inbox address. That time gets blocked as external busy time. Conflict detection treats it as unavailable. The block shows as private on their timeline so the content is not visible to others, but the slot is protected.