Spaces

Do and don't guide for your agent at a space organisation

This guide gives plain do and don't rules for an AI agent answering chats for a space research or technology organisation. It keeps replies friendly, factual and inside your limits.

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

Before you start

An agent works best with clear instructions that a person could read aloud. Short do and do not rules beat long policy documents, because they are easy to check and easy to fix. This guide covers the habits that matter most for a space organisation.

Read through the rules and change any that do not suit you. Then give the final list to whoever sets up your agent, and keep a copy for your staff. When a reply goes wrong, you can point to the rule that should have prevented it and improve it.

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

[ ] Do greet people warmly and use the name of your organisation.
[ ] Do quote your published facts, dates and opening times exactly.
[ ] Do ask which group the sender belongs to when it is unclear.
[ ] Do hand over press, technical, security and procurement questions.
[ ] Do say honestly when you do not know and a person will confirm.
[ ] Don't explain missions or results in your own words.
[ ] Don't share technical drawings, test data, software or unpublished schedules.
[ ] Don't describe security arrangements or restricted areas.
[ ] Don't promise placements, visits, tickets or contract outcomes.
[ ] Don't message anyone who has not written to you or asked to hear from you.

Why the Don't rules matter most

In space work, the risky replies are rarely rude. They are helpful. An agent keen to please might explain a failed test in friendly words, or describe where the loading gate is for a delivery. Both feel kind and both can cause real trouble.

The Do rules make the agent pleasant. The Don't rules keep it safe. Write both, test them with awkward sample messages, and keep adding examples as real ones appear.

Turn rules into examples

A rule is clearer with a sample message beside it.

  • Rule: do not explain missions. Example: a message asking why a launch failed goes to the press office.
  • Rule: do not promise placements. Example: say when applications open and how to apply.
  • Rule: do hand over security. Example: a report of a drone near the fence goes to the security team at once.

FAQ

How many rules should we give the agent?

Ten to fifteen short rules cover most needs. Too many rules become hard to follow and to test, so add a new one only after a real message shows a gap.

Should the rules be shared with staff?

Yes. Staff who take hand-overs should know what the agent will and will not do, so they are not surprised, and so they can suggest better rules from experience.

Can the agent be friendly and still follow the Don't rules?

Yes. A warm tone and a firm limit go together well: thank the sender, say what you can do, and explain kindly that a colleague will take the rest.

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.