Striker

Use cases · Reminder

Confirmation and rescheduling without friction.

Cut no-shows by confirming every visit a day ahead.

Reminder 24h ahead · the team's calendar

A sales-room reception with the printed visit schedule and a phone on the counter.

The challenge

Cut no-shows by confirming every visit a day ahead.

Case context

  • 01

    Visit booked: Saturday 10:00

  • 02

    Rule: reminder 24 hours before

  • 03

    Team calendar connected

Conversation

The customer can't make Saturday; asks to move it.

Voice

Fictional examples based on real product flows.

Striker agent

Hi Marcela, a reminder of your visit tomorrow, Saturday at 10:00, at Costanera Norte. Shall we confirm?10:00
Oh — tomorrow won't work. Can we move it?10:18

Striker agent

No problem. I have Sunday at 11:00 or Tuesday at 18:30. Which works for you?10:19
Sunday at 11 is perfect.10:24

Striker agent

Done: Sunday 11:00. The updated invitation is on its way. Have a great weekend!10:24

How Striker operates

The customer can't make Saturday; asks to move it.

  1. Remind once, never insist

  2. If they can't make it, offer at most two alternatives

  3. Changes always reflected on the team calendar

Next step

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

Striker · a Tyrell product

Bring your operation. We will design the flow with you.

We connect your channels, documents, and rules to show a complete case before it goes live.

All cases
ChannelsContextFollow-upTeamStriker sales layerTyrell infrastructure