Submitting a Feature Request

How to Submit

Email Support@TrackMyDebtor.com with the subject line:

Feature Request: [brief name]

For example: "Feature Request: CSV export for alert history" or "Feature Request: Email digest frequency settings." A clear subject line helps us tag and categorize your idea correctly so it doesn't get lost.

What Makes a Great Request

The most useful feature requests describe the problem you're trying to solve, not just the solution you have in mind. We may already have a better way to solve the same problem, or your framing may reveal a use case we hadn't considered.

A great request includes three things:

• The problem you're facing. What can't you do right now, or what takes longer than it should? Be specific about the friction point.
• Your use case. What are you ultimately trying to accomplish? Are you an attorney with dozens of debtors? A collection agency? A solo judgment creditor? Context helps us understand how broadly a feature would apply.
• How often you'd use it. Is this a daily need or a once-a-month edge case? Features that address frequent pain points move up the priority list.

Good vs. Vague Requests

Here's the difference between a request that helps us and one that doesn't:

What We Do With Requests

Every feature request that comes in is read by a team member. We don't have a public-facing idea board, but requests are tracked internally. Here's honestly what happens:

• All requests are considered. Even ideas we can't build right now get catalogued. The patterns we see across many requests are what tell us where the product needs to grow.
• Popular requests get prioritized. When multiple users independently ask for the same thing, that's a strong signal. Your request adds weight to the pattern even if you're not the first person to ask.
• We may follow up for more context. If your request is interesting but we need more detail to evaluate it, we'll reply with questions. A reply means we're taking it seriously.

No Commitment to Implement

Submitting a request doesn't mean it will be built. Building the wrong feature wastes time that could go toward something that helps more users. We have to make hard calls about what gets prioritized.

That said: requests definitely influence what gets built next. The product today looks substantially different from what it was a year ago, largely because of feedback from users like you.

What's Coming

We're not in the habit of publishing detailed roadmaps or committing to shipping dates, but a few things are on our radar. UCC filings and lien data are areas we're actively exploring for future monitoring coverage. The product is growing steadily — more data sources, better alert tooling, and improved account management are all directions we're moving in.

If your request aligns with any of those areas, mentioning your specific use case helps us understand the priority from the user's perspective.

If Your Request Is Urgent

If you have a workflow that's genuinely blocked because a feature doesn't exist yet — not just "it would be nice," but "I can't do my job without this" — say so explicitly in your email. Explain what workaround you're using now and why it's insufficient. That context helps us understand whether fast-tracking something is worth it.