Spaces

"Let me check" replies for space organisation chats

These replies let an AI agent say honestly that it is not sure and that a person will confirm. They suit space organisations, where a wrong guess about a date or a mission can cause real trouble.

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

Before you start

In space work, the confident wrong answer is the dangerous one. A guessed launch time sends families on a long drive. A casual comment on a mission result ends up quoted. When your agent does not know, the best thing it can do is say so, kindly, and tell the person who will find out.

Fill in the team that will check and how long a check usually takes. Copy the reply that matches the question. These messages keep the sender calm, and they protect the organisation from sounding sure about things it has not confirmed. Keep the promised time one you can meet.

Date or time not published

Thank you for asking. I do not have a confirmed answer on that yet, and I would rather not guess. I have asked [check team] to check, and someone from [business] will reply [check time].

Question about a mission

That is a good question about our work at [business]. I only share what we have already published, and I cannot answer this one. [check team] will look at it and reply [check time].

Unusual access request

I am not sure whether that is possible at [business], so I have asked [check team] to confirm. Please do not make travel plans until they reply, which should be [check time].

Question about a placement

Thanks for asking about placements at [business]. I do not want to give you the wrong date, so [check team] will confirm the details and reply [check time].

Supplier question

I cannot confirm that for you, and I do not want to mislead you. [check team] at [business] will check and reply [check time]. If you have a document to send, tell me and I will note it.

Why honesty works

People rarely mind waiting if they trust the answer. A short, humble reply like the ones above tells them a real person is on it, and it stops a second and third message asking the same thing.

It also gives you a list. Every not-sure reply is a gap in your written reference. Read them each week and fill the most common ones, so the agent knows more next time.

  • Keep the not-sure reply short and warm.
  • Name a team, not just somebody.
  • Say when, in words people can plan around.
  • Log the question so you can add the answer.

FAQ

Does this make the agent look unhelpful?

Not at all. People trust an organisation that admits what it does not yet know. A quick, clear promise to check feels much more helpful than a vague answer that has to be corrected.

When should the agent say it is not sure?

Whenever the answer is not in the written reference, whenever dates are unconfirmed, and whenever the topic is technical, security-related or about decisions other people make.

What if nobody checks in time?

Then the promise was too short or the hand-over too weak. Lengthen the promised time, name a back-up person, and review late replies each week until the habit is steady.

More free tools for space research and technology programs

Read the guide: Answer visitor, student and supplier questions in chat, and keep technical and security matters with your people.