CO Bingo

CO Bingo Card
Preview

This bingo card has 51 words: Used the #wrong_driver_info, Have a HOT shipment, Used an OS&D email template to request info when overages, damages, or load rejection was reported, Got DR’s current location when told they are not MT yet (dispatch task), Sent the breakdown email template when a carrier reported a mechanical issue, Input HD times according to SOTC, Sent correct tracking instructions via SMS (must add load number on the square & DR’s name), Opened a comcheck issue, Opened Customer: DETENTION-Notify Customer issue, Updated the owner of an issue to coverage if the person is OOO, Used #dummyresolved, Ensured the driver had enough HOS and tracking on a Henkel load before dispatch, Assisted/ troubleshoot and got a driver actively tracking via IBC/OBC (Add load #), Have an Amazon vendor load, Marked an LG load as delivered before the cutoff (midnight the day of the appt), Marked a load that has 3 or more stops for delivery as delivered on the day of appointments, Used the Pulling Driver SOP on a Niagara load when OTD was compromised, Snoozed the load after a first outreach for 30 min, Used #dummy, Got a load tracking that is 900+ miles & L ¾, Used the Lumper: Receipt for Reimbursement (Reminder) email template, Followed up with a carrier for missing paperwork on an OS&D (EX: COD form), Got a driver tracking on a Nutrafol, Costco, LG, Niagara, or GNC load, Confirmed OTD is feasible when notified of a late ETA for pickup on a Niagara load, Used the Lumper Request email template when the carrier requested a payment code, Left a note under Failure to Track issue to notify team you attempted or got the driver tracking, Tagged or made a CM the owner of an email (escalation/ carrier requested response from CM), Costco Load: Confirmed the driver has HOS and trailer is free of holes, Opened an Early/Late Driver issue and provided the reason for the delay and solid ETA in the note (Add load #), Opened Accessorial issue for TONU request and snoozed task accordingly (Add load #), Opened a bounce issue at least 1.5 hours before PU if late ETA or carrier NA after 2x outreach, Enjoys hiking or outdoor adventures, Requested missing truck/trailer numbers/updated/ notated on shipment (Add load #), Uploaded the repair receipt/invoice under the Escalation - Breakdown issue (Add load #), Opened a Missing/ Wrong Carrier Info issue after attempting to get the correct info (Add load #), Volunteers for a cause, Has had the internet/power cutout during a work meeting, Followed up with the carrier within 1 hour of opening carrier unresponsive issue (Add load #), Requested photos of the trailer when the carrier reported a rejected trailer, Opened the Facility issue for the correct reason and left a detailed note/ snoozed (Add load #), Opened the Appointment issue for the correct reason and left a detailed note/ snoozed (Add load #), Wrong address: requested a copy of the paperwork and the address to confirm (Add load #), Driver loaded overweight: Requested a copy of the scale ticket and BOL (Add load #), Carrier requests specific PU/DEL #; you found it on the load page and relayed it (Add load #), Opened a Reschedule Issue + provided a reason for the R/S and time/date to R/S in the note (Add load #), Opened Requested Detention on Behalf of Carrier issue, submitted request, and uploaded paperwork, Return to shipper: you requested and uploaded the BOL and seal to the open issue for RMA approval (Add load #), Enjoys spicy cuisine, Plays an instrument, Forwarded an email requesting load booking info to booking@nfiindustries.com (include email link) and Requested an SS of a weather-related app or photo of inclement weather when carrier reports weather delay.

More like this:

TRAC Bingo | NCS Bingo | Bingo - Afterhours Logistics Edition | Carrier Sales Bingo | Disputes Bingo

Play Online

Share this URL with your players:

For more control of your online game, create a clone of this card first.

Learn how to conduct a bingo game.

Call List

Probabilities

With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.

Tip: If you want your game to last longer (on average), add more unique words/images to it.