1. Check your access

Open SayIntentions.ai VA-Link. The page identifies CEO, Dispatcher or View only access. Management controls depend on that access. These steps describe the flyLAT configuration; follow the service instructions for obtaining the required account and keys.

2. Keep airline and pilot keys separate

The CEO enters the VA API Key supplied for the airline. This is separate from a pilot key. Individual pilots opt in through Settings > 3rd Party. A configured readiness indicator shows that configuration is present; check the integration result before assuming every pilot is connected.

3. Write role-specific guidance

Use Cabin Crew for service style and announcements, Dispatcher / Operations for route policy and operational context, Copilot / Flight Deck for cockpit procedures, and SkyOps / Special Operations for mission context. Keep instructions specific to your airline and avoid contradictory guidance between roles.

Choose Save changes with authorised access, then reopen the page to verify the saved configuration. Never include secret keys in the guidance text.

4. Review messaging separately

The page also offers authorised messaging and CEO controls for automatic company TELEX. Review intended recipients and content before sending or enabling automatic communication. Saving guidance is a different action from sending a message. If delivery is unclear, inspect the available status before retrying.