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.
You can change anything before sending.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Describe the enquiries you receive and the information missing from an initial assessment.
Have a quick question? Get in touch.