Spaces

First-reply checklist for engineer and buyer messages to component makers

This checklist shows what the first reply to a new engineer or buyer message should include, so a part question or sample request gets a useful answer at once. It is made for makers of chips, boards, connectors and passive parts.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

People who write to a component maker are short on time and exact in what they ask. An engineer has a prototype due, a buyer has a line waiting. If your first reply is vague, they open the next supplier chat on their list and ask the same question there.

Read each point and tick the ones your replies already cover today. Any gap is something to fix in how your team or your AI agent first answers. Pin it near the sales desk, or read it aloud before a busy week of quotes and sample requests.

Tick each one as you go. 0 of 10 done.

[ ] Repeat the part number back exactly as the customer wrote it.
[ ] Say the lifecycle status in the first line: active, last time buy or end of life.
[ ] Send the datasheet link for that exact part.
[ ] Ask for the quantity and the date they need it by.
[ ] Ask what the part is going into, only if it changes the answer.
[ ] Name the company and the contact who will receive the reply.
[ ] Say plainly what you do not quote or promise in chat.
[ ] Offer a mating or alternative part when the first choice is unavailable.
[ ] Keep it short enough to read in one glance on a phone.
[ ] End with one clear next step and who owns it.

What a strong first reply sounds like

Imagine a design engineer writes: is the 100 microfarad 25 volt capacitor still active, and is there a smaller case? A strong reply confirms the status, links the datasheet, names the smaller package if one exists, and asks how many they need and by when.

That is four useful things in four short lines. It answers the question, saves the engineer a trip to your website and gives your sales team the quantity and date they need to follow up.

Slips that lose a design win

These are the mistakes we see most in component chats.

  • Replying with the whole catalogue instead of the one part asked about.
  • Guessing at a lead time instead of saying a person will confirm it.
  • Suggesting a replacement part without checking it fits the same footprint.
  • Leaving an engineer to chase you after they have already sent the details.

FAQ

How fast should the first reply to an engineer be?

As fast as you can while staying exact. An engineer in a prototype phase will ask another supplier within the hour, so a short correct reply now beats a long perfect one tomorrow.

Should the first reply include a price?

Only if your price list is public and your agent reads it from a tool you connect. Otherwise say a person will quote, and collect the part number, quantity and delivery date first.

What if the customer does not answer my questions back?

Leave the chat open and send one polite follow-up if they were still asking. They wrote to you first, so a short nudge is fine, but do not keep chasing a buyer who has gone quiet.

More free tools for electronic component makers

Read the guide: Answer engineer and buyer messages for electronic component makers.