How to Handle an Email Drumkit Misread

Last updated: March 10, 2026

Drumkit reads and interprets email content using AI, and while it is highly accurate, it may occasionally misread an email — extracting incorrect load details, misidentifying a shipper or carrier, or surfacing a suggestion that doesn't match the actual message. This article explains how to identify a misread, correct it, and report it so the issue can be addressed.

What a Misread Looks Like

A misread occurs when Drumkit extracts or displays information that doesn't accurately reflect the email content. Common examples include:

  • A pickup or delivery date that doesn't match what the email says

  • An incorrect origin or destination city or state

  • The wrong load number, PO number, or BOL number

  • A carrier or customer name that doesn't match the email sender

  • A suggested action that doesn't make sense for the email (e.g., creating a new load when the email was actually a rate update)

  • A drafted reply that contains incorrect or inapplicable information

Step 1: Do Not Confirm the Action

If something in the Drumkit sidebar doesn't match the email, stop before confirming. Do not submit data to your TMS or send a message until you have corrected the issue. An incorrect TMS entry or outbound message is harder to fix after the fact.

Step 2: Correct the Fields Manually

Most misreads can be corrected directly in the sidebar without needing to restart or leave the email:

  1. Click into the field that contains the incorrect information.

  2. Edit or replace the value with the correct information from the email.

  3. Review all other fields to confirm nothing else was affected.

  4. Once everything looks accurate, proceed with confirming the action.

If the entire suggestion is wrong and cannot be easily corrected (for example, Drumkit created a new load when the email was clearly about an existing one), do not confirm the action at all. Handle the email manually and move on to the reporting step below.

Step 3: Report the Misread

Reporting misreads is important — it helps the Drumkit team identify patterns and improve accuracy over time. Here's how to report one:

  1. Note the details. Before moving on, jot down the basics: what the email was about, what Drumkit got wrong, and which field or action was affected.

  2. Contact your team lead. Let your team lead know about the misread, especially if it involves a high-value load or if you've seen it happen more than once with similar emails.

  3. Reach out to Drumkit support. For persistent or recurring misreads, email support@drumkit.ai with the details. The more specific you can be, the more helpful it is — include the type of email, what was misread, and what the correct information should have been. Do not include any sensitive shipment or customer data unless asked.

When to Escalate Immediately

Contact your team lead right away if:

  • A misread caused incorrect data to be submitted to your TMS before you could catch it

  • A draft message with incorrect information was sent before you reviewed it

  • You are seeing the same type of misread repeatedly across multiple emails

These situations may require corrective action in your TMS or follow-up with a carrier or customer, and your team lead should be looped in promptly.

Tips for Minimizing the Impact of Misreads

  • Always review before confirming. The best way to prevent a misread from causing a problem is to catch it before it goes anywhere. See Reviewing and Confirming AI Actions for guidance.

  • Pay extra attention to complex emails. Emails with multiple loads, date changes, forwarded threads, or non-standard formatting are more likely to result in a partial or incorrect read.

  • Forward clean versions of messy emails. If an email is heavily formatted, contains a long chain of replies, or has attachments with key details, try forwarding just the relevant portion as a new message to give Drumkit a cleaner version to work from.

Common Questions

Q: Drumkit got the load details wrong and I already confirmed the action. What do I do?

  • A: Contact your team lead immediately. Incorrect TMS entries should be corrected as quickly as possible to avoid downstream issues with scheduling, tracking, or billing. Drumkit cannot reverse a submission once it has been confirmed.

Q: Is a misread a bug I should report to IT?

  • A: Not necessarily. Misreads are typically a matter of AI accuracy rather than a technical malfunction. Report them to your team lead and to Drumkit support rather than to IT, unless the sidebar itself is not loading or functioning properly.

Q: What if Drumkit consistently misreads emails from one specific carrier or customer?

  • A: This is exactly the kind of pattern Drumkit support wants to know about. Send an email to support@drumkit.ai describing the pattern — the carrier or customer name, the type of email, and what gets misread. This kind of feedback directly improves accuracy.

Q: Can I flag a misread inside the Drumkit sidebar itself?

  • A: At this time, misreads should be reported via email to support@drumkit.ai or through your team lead.

Getting Help

If you run into an issue not covered here, reach out through the following channels:

  • Internal Support: Contact your team lead or IT administrator

  • Drumkit Support: support@drumkit.ai

For updates or corrections, please submit a request by reaching out to support@drumkit.ai.