A prospect filling out an intake form is trying to get a reply from a person. When none of the dropdown options describe their situation, they still pick one. The nearest option gets stored, and the routing rules treat it as something they said on purpose.
I watched a demo request go this way. The buyer ran marketing and events at a company of about 80 people, and they wanted the form answers in the CRM before a sales meeting on Thursday. The dropdown offered Lifecycle, Product analytics, and Enterprise security. They chose Product analytics, the only label that mentioned anything they could picture. The sequence that fired talked about dashboards. They replied once, confused, and the rep marked them unresponsive. The confirmation page had already counted a clean submit.
The list is written for the CRM
Dropdown options usually get their wording in a reporting meeting, copied from the CRM picklist so the sync will accept the create. Industry, role, company size, product interest, and reason for contact all arrive that way. The stranger on the form still has to find themselves in that list.
Buyers describe the job. They say demo requests keep disappearing, or a colleague forwarded a screenshot and they cannot tell which product name matches it. The list says Lifecycle, PLG, RevOps platform, Workspace admin. A buyer talking about a missed handoff will not recognize that request in those labels. They scan, choose the first option that sounds adjacent, and move on. The CRM stores a guess they do not expect you to read back.
Other is supposed to catch that miss, and people skip it. It sits at the bottom, it feels like failing the question, and selecting it often opens a blank box with no hint, or no box at all. If almost nobody chooses Other, the misses are sitting inside the popular options. People would rather be slightly wrong than look like an exception.
Past eight options, many people stop comparing and start skimming. Alphabetical order puts the common answers in the middle. A long industry dropdown fills up with "Professional services" and "Technology" from people who got tired, including people who had a specific answer and nowhere to put it. Company size fails when the ranges skip the company in front of you. Someone with 60 employees, looking at "11-50" and "201-500," picks a side. Routing then treats that side as a measured fact.
A single department field drops a split you needed. Marketing has the tab open and sales ops owns the budget, or support is already on the thread because the current tool is broken and someone still wants to add seats. One dropdown forces a winner, usually the person who was willing to submit. If the queue needs one owner, ask who should receive the reply, and ask who else is involved in a second field.
Check the default before you blame the person who submitted. If the first option is already selected, a hurried person leaves it and the integration writes it as a choice. If the placeholder "Select an option" lands in the CRM, that string becomes a segment. I have opened a queue where the same company-size value sat on lead after lead, because the field looked finished and the page allowed submit.
Urgency options teach a faster bad habit. Anyone who has filled out a form learns that "ASAP" gets a quicker reply than "This quarter" or "Just researching." They pick it. The SLA report then treats the queue as one urgent pile, the pool gets skipped, and the leads with a deadline sit next to people who were being cooperative. Once one option is known to move people up, the field stops telling you who has a deadline.
A wrong pick still gets a queue
The bad value shows up after the thank-you screen, and it looks solid because a dropdown produced it. Conditional questions raise the cost. Choose Analytics, and the form can open a second page about data sources and refresh schedules. The person fills it in, because they want the conversation and the page sits in front of the button. You then have detailed answers to the wrong interview. The record looks finished, so nobody challenges it until a rep is on a call and the notes do not match the buyer's first sentence.
Role and company size decide who works the lead, and how fast. A rule that sends directors and above, at companies over 200 employees, to a senior AE will follow the dropdown even when the person was guessing. The founder who rounded up sits in a queue built for a different kind of deal. The director who chose "Manager," because their title was missing, waits in the pool. Both show up later in a capacity meeting about headcount. The buckets that sorted them stay on the form, because submissions are still arriving and the report looks busy.
Reason for contact splits sales and support in the same pass. Someone with a broken invoice who also wants to add seats picks "Billing question" or "Talk to sales," whichever row sits higher, or whichever sounds less likely to end in a help center. Sales receives a ticket and support receives a buyer. Each team assumes the other one owns the thread, and the submitter gets a reply that covers only half of the comment they typed.
After enough of these, reps ask again on the call. You hear it in the first line: "I see you selected enterprise security, but tell me what you need." The rep still has to recover the request, and the dropdown has already chosen the queue. People who have been through that will skip the value next time. The original choice sits uncorrected in the CRM, and more options will not change their habit.
Edit the list from replies you already have
Take 20 recent submissions and the notes or first replies that followed them. Write down the phrases people used once someone asked what they wanted. If several of them said they need the answers in the CRM before a demo, put a plain version of that phrase on the form. If nobody said "demand generation platform," a campaign name is a weak reason to make it a top-level option.
Keep the first dropdown short enough that the likely options are visible without a long scroll, and put those options near the top for a phone. Finer detail can wait for a follow-up that appears only after a matching choice. A short first list and one relevant next question will route more cleanly than a flat list of every value the CRM is able to store.
Order the options by how often you hear them. Alphabet and org-chart order both bury the answer a tired person would have given you. If Other stays, put a text field under it and read the entries every week. When the same phrase keeps showing up, add it as an option, or replace the categories with the phrases from the notes. If nobody reads that text, Other never changes the form, and the popular options keep absorbing the misses.
Write the labels the way a person would answer, and map them to the short CRM values in one place. "I want a demo of the reporting product" takes more room than "Reporting," and it can still sync to a picklist value with that shorter name. When the CRM value changes, leave the wording on the form alone. The submitter should be able to land in the right queue without knowing an API name.
If people often need more than one choice, or they are not sure yet, put that on the list and pick the route yourself. "Not sure" should reach a person who can ask a follow-up. Point it at a default product sequence and the doubt is stored as a product vote. Leave "Not sure" off the form and people still submit, choosing a product so the button will work.
After the change, set a week of dropdown values next to the call notes for those same leads. If one option takes most of the volume, or a default never moves, the list still does not match the calls, so change the options. A validation error that sends the person back to choose again cannot supply a choice the list never offered.
Some questions should stay as a sentence. If you cannot write a short list a buyer would recognize from their own week, use one text field and a line of helper text, such as "Need the responses in HubSpot before Thursday's demo." You will get messier text than a picklist, and a rep can route that sentence on the same day.