# Subject-field article suggestions before ticket submit

> Suggest relevant help articles while the user writes the ticket subject so the best answer can stop the request before it enters the queue.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/subject-field-article-suggestions-before-ticket-submit/
- Source: [support.zendesk.com](https://support.zendesk.com/hc/en-us/articles/4408843563418-What-are-the-differences-among-instant-search-article-suggestion-and-help-center-search)
- GrowthDex source hub: [Zendesk Help: What are the differences among instant search, article suggestion, and help center search?](/sources/zendesk-help-what-are-the-differences-among-instant-search-article-sugge/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Support, Help Center, Website
- Stages: ticket deflection, self-serve support, support-led growth, knowledge base
- Key metric: If the user clicks a suggested article from the Subject field, the support ticket is not opened.

## Why this can grow

A lot of avoidable tickets get created because the form asks for effort before it offers help. Zendesk's article suggestion flow flips that order. As the user types the subject, the help center can suggest relevant articles based on titles, content, and labels, and if the user opens one of those suggestions the ticket never gets created. That is useful because it preserves the user's original language, gives the archive one more chance to do the job, and keeps the queue from filling with questions that already had a public answer.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where subject-field article suggestions before ticket submit can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Help Center channel.
3. Use the evidence from support.zendesk.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Zendesk says article suggestion search runs from the Subject field in the help center ticket form, searches titles, content, and labels, and stops the ticket from opening if the user clicks a suggested article.

## Adjacent tactics in the same lane

- [Support funnel Tried to Resolve gap review](/growth-ideas/support-funnel-tried-to-resolve-gap-review/) - 2 shared channels, 1 shared stage
- [Help center setup mode before public activation](/growth-ideas/help-center-setup-mode-before-public-activation/) - 2 shared channels, 1 shared stage
- [Manual help-center order before automatic sorts](/growth-ideas/manual-help-center-order-before-automatic-sorts/) - 2 shared channels, 1 shared stage
- [Logged-in customer portal for request status](/growth-ideas/logged-in-customer-portal-for-request-status/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The answer should interrupt the ticket before it opens](/blog/the-answer-should-interrupt-the-ticket-before-it-opens/) - support-led growth, technical SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.