Gate your UI on availability

Gate a custom chat field or microphone button on conversation availability so player input waits until a character can hear it.

Bind your own chat field, microphone button, or send action to ConvaiManager.ConversationAvailability so it only accepts input once the addressed character can actually hear it. Use this page when you are building custom input UI rather than using the shipped chat field, which already gates itself — see Customise the chat field prompts if that is what you are configuring.

Prerequisites

• A scene with ConvaiManager and at least one active ConvaiCharacter. See Scene components reference.
• Familiarity with the conversation availability states. See How conversation availability works.

Read the current verdict

ConvaiManager.ConversationAvailability returns the current ConvaiConversationAvailability for ConvaiManager.AddressedCharacter. Call CanAcceptPlayerInput() on the result to get the single boolean a UI needs:

using Convai.Runtime.Components;
using UnityEngine;
using UnityEngine.UI;

public class SendButtonGate : MonoBehaviour
{
    [SerializeField] private ConvaiManager _manager;
    [SerializeField] private Button _sendButton;

    private void Update()
    {
        _sendButton.interactable = _manager.ConversationAvailability.CanAcceptPlayerInput();
    }
}

React to the change event instead of polling

ConvaiManager.ConversationAvailabilityChanged fires whenever the verdict moves, including when the player starts addressing a different character whose availability differs. Subscribe to it to update UI on the moment rather than on the next frame:

private void OnEnable() => _manager.ConversationAvailabilityChanged += HandleAvailabilityChanged;
private void OnDisable() => _manager.ConversationAvailabilityChanged -= HandleAvailabilityChanged;

private void HandleAvailabilityChanged(ConvaiConversationAvailability availability)
{
    _sendButton.interactable = availability.CanAcceptPlayerInput();
}

Gate on a specific character instead of the addressed one

A UI element tied to one particular character — a name plate, a per-character indicator in a multi-character scene — should read ConvaiCharacter.ConversationAvailability on that character directly, rather than ConvaiManager.ConversationAvailability, which always answers for whoever is currently addressed:

[SerializeField] private ConvaiCharacter _character;
[SerializeField] private Image _indicator;

private void Update()
{
    _indicator.color = _character.CanAcceptPlayerInput ? Color.green : Color.gray;
}

ConvaiCharacter.ConversationAvailability is not the same as ConvaiCharacter.IsCharacterReady. IsCharacterReady is set once by the character-ready signal from Convai and does not clear when the character later loses its seat in the room. Use ConversationAvailability for anything that gates player input.

Verify the gate

Enter Play mode, connect, and try to type or press send before the character has been confirmed. The gate should block the action until availability reports Ready or Answering. Disconnect the character mid-conversation and confirm the gate closes again.

Next steps

React to the player starting to speakConversation availability reference