Spaces

Hand-over rules: space chats that must go to a person

This checklist lists the space-related chats an AI agent should always hand to a person, such as technical data, security and press requests. It helps you decide the rules before a message goes wrong.

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

Before you start

A space organisation holds information that is not for general chat: designs, test results, site security arrangements, unpublished schedules and contract terms. Most messages are harmless, but a few carry real risk if answered casually. An agent should be able to spot them and stop.

Go through the rules and keep the ones that fit your organisation. Then write down who takes each kind of message, with a back-up name. A rule that points to nobody is worse than no rule, because the sender waits and the message goes stale.

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

[ ] Any request for technical specifications, drawings, test data or software.
[ ] Questions about security arrangements, restricted areas or unusual site access.
[ ] Reports of a drone, a person or a vehicle near a facility.
[ ] Any request for a statement, quote, interview or comment.
[ ] Questions about tender results, awards or contract terms.
[ ] Requests about unpublished launch or operations dates.
[ ] Messages from anyone who says they were injured or distressed on site.
[ ] Requests involving the details of staff, such as names and contact numbers.
[ ] Anything the agent cannot answer from the written reference.
[ ] A sender who asks to speak to a person.

Make the hand-over useful

When a chat moves to staff, the person should not have to ask the same questions again. A short note saying who wrote, what they want, what was already said and how urgent it is saves the press office or the contracts team several minutes each time.

Tell the sender what happens next in one line, for example: I have passed this to our press office, who will reply within one working day. Do not hint at what the answer might be.

Settle these with your team

Before you switch anything on, agree answers to these questions.

  • Who covers technical and security messages out of hours, and how are they alerted?
  • What counts as urgent: a safety report, a journalist on deadline, a supplier at the gate?
  • Which words in a message should always trigger a hand-over?
  • Who reviews handed-over chats each week to improve the rules?

FAQ

Should the agent ever refuse to discuss technical topics?

It can explain general, published facts about your work. For anything detailed, unpublished or specific, it should hand over without judging the request, because it cannot know the access rules.

What if a hand-over happens at night?

The agent should tell the sender a person will reply the next working day, and give emergency contacts for safety matters. Urgent security reports need a real on-call route set up in advance.

Does handing over mean the agent stops listening?

It stops answering the sensitive part, but it can keep helping with routine questions in the same chat, such as opening hours, as long as a person is clearly looking after the main issue.

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.