Reviewing and confirming AI actions
Last updated: March 10, 2026
Drumkit is designed to automate the repetitive parts of your workflow — reading emails, extracting load details, drafting replies, and pushing data to your TMS. But every action Drumkit suggests requires your review and confirmation by default before anything is submitted or sent. This article explains what that review process looks like and why it matters.
The Golden Rule: Always Review Before You Confirm
Drumkit is highly accurate, but it is not infallible. Email language varies, shippers and carriers don't always format things consistently, and edge cases happen. A quick review of the sidebar before confirming any action is the single most important habit to build — especially for high-value shipments.
Think of Drumkit as a capable assistant who has done the prep work for you. Your job is to give it a final check before it goes out the door.
Types of Actions Drumkit Will Suggest
Depending on the email content, Drumkit may surface one or more of the following:
Load creation or update — Drumkit extracts shipment details from the email and pre-fills a load in your TMS. Review origin, destination, dates, commodity, weight, and reference numbers before confirming.
Carrier quote request — Drumkit reads a truck list or rate inquiry and prepares a quote request. Review the lane details and carrier information before submitting.
Appointment scheduling — Drumkit drafts a pickup or delivery appointment based on the email. Review the time, location, and contact details before confirming.
Customer update — Drumkit drafts an outbound status update to a shipper. Review the message content and recipient before sending.
Outbound reply drafts — Drumkit may draft a reply to an incoming email. Review the full message before hitting send.
How to Review a Suggested Action
Open the email — The Drumkit sidebar will automatically read the message and populate the relevant fields.
Check the extracted data — Review each field in the sidebar. Ask yourself: does this match what the email actually says?
Edit if needed — Any field in the sidebar can be edited before you confirm. Click into the field, make your correction, and proceed.
Confirm the action — Once you're satisfied everything is accurate, click the confirm or submit button. Drumkit will push the data to your TMS or send the message on your behalf.
What to Watch for During Review
Origin and destination — Verify city, state, and any facility-specific details match the email.
Dates and times — Confirm pickup and delivery windows are correct, especially for time-sensitive loads.
Reference numbers — Load numbers, PO numbers, and BOL numbers should match exactly.
Carrier or customer name — Make sure Drumkit has matched the correct record in your TMS.
Draft message content — For outbound messages, read the full draft before sending. Tone, accuracy, and recipient all matter.
When to Pause and Escalate
Do not confirm an action if:
Something in the sidebar doesn't match the email and you're not sure how to correct it.
The load details seem unusual or don't align with your existing records.
A draft message contains information you're not confident is accurate.
In any of these cases, stop, correct what you can, and contact your team lead if you're unsure. It is always better to pause than to push incorrect data to your TMS or send a message with wrong information.
Tips for Staying Accurate
Slow down on complex emails. Emails with multiple loads, date changes, or special instructions require extra attention during review.
Never skip review for high-value shipments. Drumkit is built to speed up your workflow, not replace your judgment on critical loads.
Report persistent errors. If Drumkit is consistently misreading a particular type of email or carrier, flag it to your team lead so it can be investigated and improved.
Common Questions
Q: Can I undo an action after I confirm it?
A: Once a load is submitted to your TMS or a message is sent, Drumkit cannot reverse it. This is why reviewing before confirming is so important. If you submit something incorrectly, correct it directly in your TMS or contact your team lead.
Q: What if Drumkit doesn't suggest any action on an email?
A: Not every email will trigger a suggested action — Drumkit only surfaces actions when it detects something actionable. If you expected a suggestion and didn't get one, the email may have arrived before your installation date or Drumkit may not have been able to parse it. Try forwarding the email to yourself, or contact support if the issue persists.
Q: Can I edit a draft message that Drumkit wrote before sending it?
A: Yes. All drafted messages are fully editable before you send them. Always read and adjust as needed before confirming.
Q: Will Drumkit ever send something without my approval?
A: No. Every action — whether it's a TMS entry or an outbound message — requires your explicit confirmation. Drumkit will not send or submit anything automatically.
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.