How Dealers Can Share Feedback and Request Features
How to turn a floor frustration into a useful feature request: what to include, how to gather input from your team and how to give feedback that product teams can act on.
Every dealership has a rep who says, "It would be great if it just did X." Usually the sentence is said in passing, at the desk, between customers. Then the shift ends, the idea evaporates and the next time the tool gets in the way, the same rep says it again. Nothing reaches the people who build the product, so nothing changes, and the rep concludes that software vendors do not listen.
Often the vendor never heard the idea. This guide explains how dealers can share feedback and request features with PostToMarket in a way that is actually useful: how to collect input from your floor, how to describe a problem so it can be acted on, what to expect and what not to expect, and how to keep your own team from submitting twelve conflicting requests. It is written for the internet director, GM or manager who ends up as the store's voice to the vendor.
PostToMarket is an independent tool and is not affiliated with, endorsed by or sponsored by Meta. Sending a request does not guarantee that a feature will be built or on what timeline; this article makes no promises about the roadmap.
Why Dealer Feedback Matters
Dealers use posting tools in conditions that product teams cannot reproduce: a crowded Saturday, a half-complete import from a DMS export, an associate on his second day. That context is the difference between a feature that looks good in a demo and one that works on a lot.
What feedback is most valuable
The most useful input is not a feature name. It is a description of a real moment where the workflow broke or slowed down. For example:
- A step that your reps repeat for every vehicle.
- A place where managers lack visibility they need.
- A mistake that keeps happening despite training.
- A report you need and currently build by hand.
What feedback is least useful
- "Make it better."
- "Add everything the other tool has."
- A request that conflicts with a Facebook rule or Meta policy. Check Meta's current commerce policies before asking for something that depends on a workaround.
- A request that arrives without context on who needs it and why.
Collect Input Inside Your Store First
A single, well-organized message is worth ten scattered ones. Build a lightweight internal process.
Assign one owner
Pick one person, usually the admin or the manager responsible for the posting workflow, to receive team input and send it on. This mirrors the approach to support described in getting help: how to contact PostToMarket support.
Gather input by role
Different roles see different problems:
| Role | What they tend to notice |
|---|---|
| Admin | Billing, account structure, team size |
| Manager | Queue visibility, assignment, analytics, leads |
| Sales rep | Speed of posting, queue order, mobile use |
| Sales associate | Clarity of assigned work, what to do when a unit looks wrong |
A simple weekly note
Ask each person to note one friction point per week in a shared document. In the monthly meeting, review the list, group duplicates and choose the top three to send. This takes five minutes and filters noise.
Distinguish a bug from a request
- A bug is something that is supposed to work and does not. Report it with the details in the support guide: affected login, unit, time and what happened.
- A feature request is something you want that does not exist. Describe the job you are trying to do.
- A training issue is something that already exists but your team has not found. Check with your manager first.
How to Share Feedback and Request Features That Can Be Used
Write for a reader who has never set foot on your lot.
The structure
- Who you are: dealership name, your role and plan.
- The job: what you are trying to accomplish, in one sentence.
- The current workflow: what you do today, step by step.
- The friction: where time is lost or errors occur.
- The ideal outcome: what would be different, described as a result, not as a design.
- How often it happens: every unit, daily, weekly, occasionally.
- Who is affected: which roles and how many people.
An example, labelled illustrative
A used-car manager at a mid-size independent lot with a Dealership plan writes: "On the mornings after an auction run, I spend a long stretch deciding which new arrivals go to which associate before anyone can start posting. I would like a faster way to review the new units and split them up fairly. This affects me and two associates, and it happens every week."
The example describes a job, the current workflow and the frequency without prescribing a specific button or screen.
What to leave out
- Specific design instructions. Describe the problem; the product team will weigh solutions.
- Complaints about other vendors. Focus on your workflow.
- Requests for guaranteed outcomes with Facebook. No tool can guarantee that Facebook will distribute every listing.
- Anything that would require sharing credentials or sensitive customer data in a message.
What to Expect After You Send It
Be realistic and professional about the process.
A reply is not a commitment
You may receive a reply with questions, a note that the request is under review or an explanation of how to do something with existing tools. None of these is a promise of a release. Product teams balance many requests, and the capabilities that exist today are the ones you can rely on.
Check whether it already exists
Before sending, scan the current capabilities. Existing features include:
- Bulk CSV and Excel import with import history and row-level error logs.
- Capture of vehicles from auction and wholesale sites into inventory.
- AI-generated titles and descriptions and a Facebook photo picker.
- Personal and per-rep queues, manager assignment to associate queues and a team queue view.
- Posting analytics by rep and source and a leads inbox for managers.
- A mobile dashboard you can install on a phone's home screen.
If your idea overlaps with something here, the better first step might be a support question rather than a feature request. For example, capturing vehicles from third-party sites with PostToMarket covers one workflow people often overlook.
Close the loop internally
Tell the person who raised the idea what you sent. People who see their input acted on keep contributing. People who never hear back stop.
How PostToMarket Automates This
Feedback is only useful when you have a stable workflow to compare it against. These are the pieces already in place:
The workflow your feedback builds on
- Chrome extension posting to Marketplace, your Facebook profile and Facebook groups, one vehicle at a time, with human-like delays and server-enforced daily limits. Sign in with email, with no API keys.
- Inventory statuses (draft, posting, posted, sold, failed) and unlimited vehicles in inventory on every plan.
- Mark as sold and archive from inventory or the queue.
The team layer
- Roles (admin, manager, sales rep, sales associate) with queues, assignment and a team queue view.
- Team analytics by rep and source and a leads inbox for managers.
Where to send input
Write to info@posttomarket.com or use the contact page. Include the details in the structure above so your note is easy to act on.
Help Shape the Tool Your Floor Uses Every Day
The best software for a dealership is shaped by the people who use it on the lot. A short, specific note from a GM or manager about a real workflow is more valuable than any amount of general praise or complaint.
Try it with your own inventory first. The Starter plan is $59 per month for a solo seller or independent lot with one login. The Dealership plan is $299 per month for up to 13 team logins.
Start your 10-day free trial with secure Stripe checkout, run your real workflow for ten days and note where it helps and where it gets in the way. Then share feedback and request features based on what you saw. Cancel anytime.