Directoryz

Choose inquiry form fields that support routing

An inquiry form should collect enough context to reach the right recipient. Extra fields can add friction without improving the response.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Identify the recipient's minimum requirements and label optional context clearly. Explain who receives the message.

Worked example · illustrative

What this looks like

A provider inquiry may need a reply address, task summary, and service region; a long company survey may be unnecessary.

Before you move on

Could the recipient understand and respond to the inquiry using the collected fields?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Define the benefit and who receives it.
  2. Keep editorial relevance visible.
  3. Measure the full journey rather than one isolated click.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →