Confirmation and rescheduling without friction.

What the reminder needs

Confirming is easy. Rescheduling without friction is the part that needs real data.

• The booked visit. Saturday 10:00, with its development and its assigned rep.
• The timing rule. Three hours before: close enough that the visit is top of mind, with room left to say so and to move it.
• The team calendar, connected. Without it the agent can remind but cannot move anything — and half the value is in moving it.

How it operates

The agent calls about three hours ahead and asks for confirmation. When the answer is no, it neither pushes nor leaves the problem open: it reads the team's real calendar and offers two alternatives that actually exist.

Once one is chosen, the event is updated and the rep is notified. There is no later step where somebody has to carry the change over by hand.

Case context

• Visit booked: Saturday 10:00

• Rule: reminder 3 hours before

• Team calendar connected

Striker agent

Voice

Next step

Visit rescheduled to Sunday 11:00; event updated and the team notified.

Controls it respects

• Remind once, never insist
• If they can't make it, offer at most two alternatives
• Changes always reflected on the team calendar

The controls

A reminder that irritates turns a doubtful visit into a lost one. That is where the controls sit.

• Remind once, without pushing. One contact. No reply means no second call.
• Two alternatives at most. Two options get chosen; five get postponed. The limit exists so the conversation closes.
• Changes land on the team calendar. The reschedule does not live in the conversation: it lands on the calendar where the rep sees it.

The conversation

By voice, in four turns:

What is left

The visit moved to Sunday at 11:00, the invitation updated and the rep notified. Saturday morning came free in time to reassign it.

No sale was recovered: a meeting that was going to be lost in silence was — and silence is where most of them go.