How do I submit a feature request?

At Drumkit, we are always working to improve — and the best source of inspiration for what to build next is the people using the product every day. Feature requests from end users help us understand what matters most to the people on the ground, identify gaps we might be missing, and make informed decisions about what to prioritize on our product roadmap.

If there is something Drumkit does not do today that would make your workflow faster, easier, or more accurate, we want to hear about it. No idea is too small.

How to Submit a Feature Request

To submit a feature request, send an email to support@drumkit.ai with the subject line: Feature Request: [Brief Description]

For example: Feature Request: Auto-populate carrier contact from TMS on quote emails

We are actively exploring more structured and on-demand ways for end users to submit feature requests — so stay tuned for updates on that front.

What to Include in Your Request

The more context you provide, the better equipped the Drumkit product team is to understand your request, evaluate its impact, and prioritize it appropriately. Here is what is most helpful to include:

1. Describe the feature you are requesting What would you like Drumkit to do that it does not do today? Be as specific as possible. A clear, concrete description is more useful than a general idea.

Example: "I would like Drumkit to automatically detect when an email contains a rate confirmation and flag it as such in the sidebar, rather than treating it as a new load request."

2. Describe the problem it would solve What is the pain point or friction you are experiencing today? Help us understand the "why" behind the request — what workflow breaks down, what takes too long, or what you have to do manually that you wish Drumkit handled.

Example: "Right now, rate confirmations trigger a load creation suggestion, which I have to dismiss manually before handling the email correctly. It slows me down and creates extra steps."

3. Additional details to help us evaluate your request

Including the following makes it much easier for the product team to assess priority and scope:

• Frequency — How often do you encounter this? Multiple times a day, a few times a week, or occasionally? The more frequent, the higher the potential impact.

• Who else is affected — Do your teammates run into this too? If so, note the role or team (e.g., ops team, account managers). Requests that affect multiple users carry more weight in prioritization.

• Your email platform — Are you using Drumkit in Gmail, Outlook, or Front? Some features may be platform-specific, and this helps the team scope the request accurately.

• Current workarounds — If you have found a way to work around the missing feature, describe it. This helps us understand the real-world impact of the gap and confirm we are solving the right problem.

• Visuals — Screenshots, screen recordings, or example emails (with sensitive details removed) are incredibly helpful. Seeing the workflow in context often helps the product team understand a request much faster than a written description alone.

What Happens After You Submit

Your request goes directly to the Drumkit team, where it is reviewed alongside feedback from other users. While we cannot guarantee that every request will be implemented, all feedback is taken seriously and factored into roadmap planning. Requests that reflect patterns across multiple users — or that unlock significant time savings — are weighted accordingly.

We appreciate every piece of feedback we receive. It is how we learn what matters most and keep getting better.

Getting Help

If your submission is about a bug or an existing feature that is not working as expected, check out How to Handle an Email Drumkit Misread or Getting Help & Contacting Drumkit Support instead.

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