Answer visitor, student and supplier questions in chat, and keep technical and security matters with your people
Organisations that carry out space research and technology programs, such as national and regional agencies, research centres, ground station operators and mission support teams, are contacted by students, teachers, researchers, journalists, hobbyists, suppliers and visitors.
Most messages are about access, events, opportunities and process: how do I apply for an internship, when is the next open day, how do I register as a supplier.
Spaces connects the messaging account those people already write to, so an AI agent such as Claude, Grok, ChatGPT or your own code can read the message and reply in the same chat, using the information your organisation gives it.

- Space organisations receive many repeat questions about visits, events, internships, school resources and supplier registration that an agent can answer from your published material.
- Technical data, export-controlled information, security arrangements, procurement decisions and media statements stay with named people.
- Students, researchers, suppliers, journalists and visitors need different replies, so the agent needs separate reference material for each.
- Launches, anniversaries, open days and funding calls produce sharp bursts of messages that an agent can absorb if briefed in advance.
- Spaces carries the conversation and does not connect to mission, ticketing or procurement systems, which the agent reaches through its own tools.
The agent can carry the public-facing and partner-facing conversation. It does not discuss controlled technical data, security arrangements, procurement decisions or anything that speaks for the organisation in public, and it hands those to a person.
Spaces handles the messages only, and any lookup in a calendar, ticketing or supplier system is done through your agent's own tools.
- Subsector
- NAICS 927
- Part of
- Public Administration
- Inside it
- 1 industry groups
- Last updated
Here is one conversation, start to finish.
An example of how an AI agent handles a message in space research and technology. The names and details are made up.
Who writes to a space research and technology organisation
The public face of space work attracts a lot of curiosity. Teachers ask for classroom resources and speakers. Students ask about degrees, placements and internships.
Families ask about visitor centres, tour times and accessibility. Amateur astronomers ask whether a bright object seen last night was a launch or a satellite pass, and enthusiasts ask where to watch a launch from.
The professional side is quieter but more consequential. Universities and research institutes write about joint projects, data access requests and funding calls. Suppliers and contractors write about registration, tender notices, delivery windows and site access.
Small companies ask how to take part in technology programs and what the application window is.
A third group are journalists, bloggers and content creators who want a spokesperson, a photograph, a fact check or access to an event. They write fast and expect a quick answer.
The agent can point them to the press office, and it must not speak for the organisation on the substance.
Questions an agent can answer well
For visitors and the public, the agent can give opening times, how to book a tour or an event, what accessibility arrangements exist, how to reach the site, and what may or may not be brought in.
It can describe in general terms the missions and facilities your organisation chooses to publish, and it can share a launch viewing guide you wrote for the public.
For students and educators, it can list the resources and programs you offer, how to apply for placements and internships, the usual closing dates, and what an application normally includes. It can explain how school visits are requested and which team coordinates them.
It should say plainly that the agent is not deciding any application.
For suppliers and partners, it can explain the registration process, the notices page, the usual order of steps in a tender or a collaboration request, and where to send documents.
It can gather a company name, the area of work and a contact route, so that the right person starts with the facts.
- Visitor hours, tour booking, access and accessibility
- Public events, talks, school visits and open days
- Internship, placement and graduate program steps
- Supplier registration and where tender notices are published
- How to reach the press office and what it handles
What your organisation must tell its agent
Write a short public-facing guide in plain language. Include the sites and their opening times, the programs and events open to the public, the education offers, the supplier and partner process, and a list of frequently asked questions with the answers you want given.
Be careful about describing missions: use text that your communications team has already published.
Draw the line around what is public. List the categories of information that are never discussed in chat, such as technical specifications that are not published, details of security arrangements, launch or operational schedules not yet public, unpublished contract terms and personal data of staff.
A clear list protects both the agent and the organisation.
Provide contacts and calendars: who runs school visits, who handles supplier registration, who answers the press, which dates are fixed.
If something changes at short notice, such as a launch scrub, a closed site or a postponed talk, one person should be able to update the reference quickly.
What always goes to a person
Technical and controlled information is the first category. A message that asks for detailed specifications, design data, test results, software, or anything that might fall under export or access controls should go to a person who understands the rules.
The agent should not judge what may be shared and should avoid sending technical material in chat.
Security and safety questions follow. Requests about site access for unusual purposes, questions about restricted areas, reports of a drone or a person near a facility, and anything that touches on the protection of people or assets should reach the right team immediately.
The agent should give emergency instructions and not discuss arrangements.
Representation matters too. Press statements, positions on policy or funding, interpretations of mission results, and comments on an incident belong to your communications and programme leads. Procurement decisions, award status and contract questions belong to the contracts team.
The agent can say who owns them and how long a reply normally takes.
How the calendar drives the messages
Space programs run on events that the public can see. A launch window, an eclipse, a mission anniversary, an astronaut visit or a new exhibit will each generate a burst of questions about timing, viewing and tickets.
A briefing before each event, with the times, the viewing guidance and the plan for a delay, keeps the replies consistent.
Education has its own rhythm. Placement and internship applications open and close, school terms bring visit requests, and competitions and challenges run on fixed dates. Suppliers follow budget and tender cycles. Ask each team to send the agent's owner their key dates once a quarter.
When plans change, speed matters more than detail. A short message saying that a launch has moved, with a pointer to the live notice and no speculation about the reason, is better than silence.
Prepare the wording in advance so that someone can approve it in minutes.
Setting it up step by step
Start with the public enquiry line, since the information is mostly published and the risk is lowest.
Connect the messaging account the public already writes to, give the agent the reference, and run it read-only at first so staff can compare its suggested replies with their own.
Add the education and supplier lines next, each with its own reference and its own named owner. Keep press and technical enquiries on handover from day one.
Test the handover with sample messages from each group, including a sensitive one, to confirm that the right team is reached.
Review regularly. Read the handed-over conversations and a sample of the routine ones. Spaces enforces per-account limits, pacing and warm-up, and sends are safe to retry, but the content, the limits and the staffing behind the handover are yours.
Common mistakes
A frequent mistake is letting an enthusiastic agent explain missions in its own words. Details get distorted, and the organisation ends up appearing to say something it did not.
Keep to published text, and have the agent quote it and link nothing the reference does not contain.
Another is treating a polite technical question as harmless. Someone asking for a drawing, a test result or a software tool may be entirely innocent, but the decision about what can be shared belongs to people who know the rules. Hand it over.
A third is broadcasting. Spaces is for conversations people start and for people who expect to hear from you, such as a student who asked to be told when placements open.
Its Terms rule out bulk unsolicited messages, cold outreach and bought or scraped lists, including lists of enthusiasts or suppliers.
Judging whether it is working
Look for qualitative signs. Do visitors and students get a clear reply quickly? Do the replies match your published pages? How often are conversations handed over, and do the summaries make life easier for the press office, the education team and the contracts team?
Ask staff whether the questions that reach them are now the ones that need them. If the education team still answers the same opening time question every day, the reference needs improving.
If the press office receives technical requests with no context, the handover summary needs more detail.
Spaces is not a ticketing platform, a mission operations tool, a secure transfer service or a place for controlled data. Keep those jobs in the systems built for them, and use the chat to explain and to direct.
What does an agent actually see?
Examples of first messages to businesses in space research and technology. They are illustrations, not real conversations.
- Maya R.What time does the visitor centre open on Saturday and can we bring a wheelchair user in a group of ten?
- Tom B.Where is the best place to watch the launch on Thursday and what happens if it is delayed?
- Priya S.I am a physics undergraduate. When do summer placement applications open at your research centre?
- Daniel K.Our school would like a speaker for a class of fourteen-year-olds. How do we request one?
- Amara O.We make small precision components. How do we register as a supplier and where are tender notices posted?
- Maya R.I am writing a feature for a science magazine and need to speak to someone about the new ground station.
- Tom B.Could you send me the design drawings and test results for the antenna on the last mission?
- Priya S.I saw a drone hovering near the perimeter fence of the tracking site this morning.
What always goes to a person.
Your agent answers what it can and hands the rest to someone on your team. These are the conversations to hand over every time.
Requests for technical specifications, design data, software or test results that are not already published.
Reports of drones, intruders, suspicious behaviour or any safety or security concern at a site.
Press requests for comment, interviews, positions on policy or funding, or statements about an incident.
Procurement questions about the status of a tender, an award, a contract term or a payment.
Questions about restricted site access, special visits or visitors who need vetting.
Messages containing personal data about staff, contractors or participants, and any complaint about how someone was treated.
Explore the industry groups.
Thirty free tools for space research and technology programs.
Checklists, ready-to-send messages, scorecards and calculators. They run in your browser and send nothing anywhere.
- First-reply checklist for space research and technology programs
- Hand-over rules checklist for space research and technology programs
- First-week checklist for space research and technology programs
- Weekly chat review checklist for space research and technology programs
- Busy-season checklist for space research and technology programs
- Customer privacy checklist for space research and technology programs
- Do and don't guide for your agent: space research and technology programs
- Greeting messages for space research and technology programs
- All 30 tools
Questions, answered.
01Can the agent discuss our missions?
It can share text that your organisation has already published and point to your public pages. It should not paraphrase freely, speculate about results or comment on incidents, because it would then appear to speak for you. Keep those to your communications team.
02Can it handle requests for technical documents?
It should not send technical material through chat or judge whether it may be shared. It can explain how data access requests work in your organisation and pass the person to the team that decides.
03How should it respond to a report about a drone or a security concern?
It should give your emergency instructions and hand the conversation to the right team at once, without discussing arrangements. Agree the route in advance, test it, and make sure it is monitored outside normal hours if your site needs that.
04Can we announce launch changes to everyone who follows the program?
Only to people who expect to hear from you, for example because they asked to be told about a particular event. Spaces is not for mass broadcasts or purchased lists, and its Terms rule out bulk unsolicited messages.
05Does it connect to our ticketing or supplier system?
Spaces does not connect to those systems. If you want the agent to check a booking or a supplier status, it needs its own tool for that. Spaces carries the messages and the agent does the rest.
06Can teachers and students use the same chat as suppliers?
They can write to the same account, but give the agent separate reference material for each group and a separate owner. A teacher asking for a speaker and a supplier asking about tenders need very different answers.
07Will the agent reply without a person checking?
That depends on how you configure your agent. You can have it hold replies as drafts for staff to review, or begin with read-only access. Many teams start with drafts for public enquiries and keep press and technical messages on handover.
08Does this mean a space agency has endorsed Spaces?
No. Spaces carries messages for whichever organisation connects it and makes no claim of endorsement by any agency or government. Your organisation is responsible for what the agent is told and for every reply that goes out.
Closer guides for specific businesses.

Supermarkets
Let an AI agent answer the messages shoppers send your store about stock, hours and order pickup. Customer-started conversations only.

Restaurants
Let an AI agent answer guests' messages about bookings, menus, hours and takeaway, in the chat they started.

Retail stores
Let an AI agent answer customers' messages about sizes, stock, store hours and reserve-and-collect, in the chat they started.

Online stores
Let an AI agent answer order, delivery, return and sizing questions from your customers in the chat they started.

Salons
Let an AI agent answer clients' booking, rescheduling and price questions in the chat they started, while you're with a client.

Real estate
Let an AI agent reply to people who message about your listings: availability, viewings and details, in the chat they started.