From a first question to a structured enquiry

Your customer does not need to know where to start. They describe their idea, answer a few questions and review the enquiry before sending it.

Discuss an RFQ implementationExplore the example

From your idea to an enquiry
Start with a few words

“We need a website where customers can explore our products and ask for a quote.”

Your enquiry takes shape

Need
Product catalogue
Scope
Specifications and documents
Timing
To be agreed

You can change anything before sending.

An example enquiry built from a short message.

GIVE IT A TRY

See how an enquiry takes shape

Choose a situation similar to yours and work through a few questions. At the end, review the enquiry and change any answers you wish.

Try it — nothing will be sent.

01 / Need: catalogue02 / Scope: specifications and documents03 / Timing and budget
04 / Draft for review

Need
Organise a catalogue
Scope
Records with specifications and documents
Timing
To be agreed
Budget
Not provided — optional
Next step
Review and revise the answers

When guided questions help

An RFQ journey is useful when the next question depends on the type of need and the team requires specific information to decide what happens next. A short contact route remains suitable for a simple question. Not every visitor should have to complete a lengthy journey.

For a more involved service, “please send a quote” rarely provides enough information for an initial assessment. An RFQ journey organises the need, scope and timing, and lets the sender review a draft before submitting. We design that journey around an agreed handling process.

Context instead of one form for everything

We define the areas and questions for each agreed journey. STAR Conversion Flows guides the path; STAR Forms Builder handles fields and storage according to the configuration. A rules-based journey is not a generative adviser and does not decide pricing or feasibility.

Timing, budget and a draft to revise

We ask about the preferred timing and scope. A budget can remain optional. Before submitting, users should see a summary and be able to return to their answers. We agree required fields, understandable error messages and information that should be shared later through a more suitable secure channel.

Information for the responsible team

We agree what information reaches your team, who can access it and who follows up. Before implementation, we also define notification wording, retention and any attachment handling.

Three separate checks after submission

01 / StorageThe enquiry in one place
02 / NotificationA message for your team
03 / ReceiptCheck that the message arrived

Storage: was exactly one enquiry created, including after a retry? Notification: did the system pass the message to the agreed notification service? Receipt: did it reach the intended recipient? A browser message does not replace these checks.

You receive the agreed journey, configuration, messages, check scenarios and an operator guide. Prepare the information you need to collect, recipients, handling and retention rules, and approved privacy wording. Acceptance also covers validation, returning to answers, corrections and exceptions. An enquiry does not confirm an order or a delivery date.

What should a manufacturer’s RFQ form collect?

Start with information that helps the manufacturer decide whether the enquiry fits its offer and contact the buyer. Questions should follow the actual quotation process at the plant.

  • The item and its application: what needs to be made or solved.
  • Material, process or key requirements, allowing the buyer to say they need help defining them.
  • Quantity and production pattern where these matter to the initial assessment.
  • A preferred date or “To be agreed”; a budget only if the buyer wishes to provide one.
  • An email address, optional company details, selected service context and contact language.
  • A summary that can be checked and edited before submission.

For example, someone enquiring about a batch of components can describe its purpose and quantity without being forced to select an unfamiliar technology. Sales or engineering staff can clarify requirements after an initial review.

Drawings and follow-up

Attachments need not be part of the first contact. Enabling them requires agreed file types and sizes, access controls and arrangements for confidential documentation. An initial enquiry on the IRiTS website does not require attachments. Do not send passwords, keys or other people’s personal information.

Acceptance checks distinguish the conversation, one stored enquiry, notification handover and confirmed receipt. A “sent” message alone does not establish all four. The recipient and responsibility for follow-up are agreed before publication.

See also our manufacturer website preparation guide. This page describes the solution; the “Ask about implementation” link starts a genuine enquiry to IRiTS.

Next step

Describe the enquiries you receive and the information missing from an initial assessment.

Discuss an RFQ implementation

Have a quick question? Get in touch.