Spaces

First-week checklist for an AI agent at an aerospace maker

This checklist walks an aerospace maker through the first week of letting an AI agent answer routine customer and supplier messages, from picking one narrow stream to reading every chat.

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

Before you start

Aerospace firms rightly move carefully. The first week with an AI agent should be small and watched, not a grand launch. The safest start is one narrow stream of messages, such as parts enquiries from repair shops or delivery questions from suppliers, with a short list of things the agent may say.

Use the list below as a plan for the week. Spread it over five working days, give each step an owner, and tick items off as they are done. Do not skip the reading steps. Reading every chat in week one is how you find the missing rule before a customer does.

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

[ ] Pick one stream of messages to start with.
[ ] Write down who writes to you in that stream.
[ ] List the ten questions you answer most in that stream.
[ ] Build a contact map by topic, with a name and a backup.
[ ] Write the do-not-answer list with engineering, quality and export.
[ ] Collect site access, delivery gate and visitor pass details.
[ ] Tell your team, in person, what the agent will and will not do.
[ ] Run five practice messages, including one grounded-aircraft case.
[ ] Switch on the agent for working hours only at first.
[ ] Read every conversation at the end of each day.

A simple shape for the week

Spend the first two days on paperwork: the stream, the questions, the contact map and the do-not-answer list. Day three is rehearsal with your team. Days four and five are live, in working hours only, with a named person reading everything that comes in.

At the end of the week sit down for twenty minutes and list what surprised you. Each surprise is either a missing ready answer or a missing rule, and both are quick to add.

Common mistakes in week one

These are the traps that trip up new setups in technical industries.

  • Starting with every customer group at once.
  • Giving the agent a long product manual and no short rules.
  • Forgetting to tell the night shift how urgent handovers will arrive.
  • Never reading the chats and assuming silence means success.

FAQ

Which message stream should an aerospace maker start with?

Pick the most routine and least technical one, such as visitor logistics or parts enquiries from repair shops. Avoid anything involving technical data until the handover rules have proved themselves.

How long should we keep the agent to working hours?

Keep it there for at least a few weeks and until the daily chat reviews turn up no surprises. Then extend to evenings, with a clear route for urgent parts.

Who should read the chats in week one?

Someone close to the customers, such as a sales engineer or customer service lead, ideally with a quality or export colleague checking a sample for anything that should have been handed over.

More free tools for aircraft, engine and space parts makers

Read the guide: Handle routine aerospace supplier and customer messages.