Home
/
Learn
/
Tools and control
/
Greetings, Disclosures and Long Sessions on Athena
Guide
3
 MIN READ

Greetings, Disclosures and Long Sessions on Athena

Open reliably, deliver required disclosures in the right words, carry history into a new conversation, and keep long or dropped sessions on track.

ON THIS PAGE

Most of a conversation can be left to judgment. A few moments cannot: the opening words, anything legally required, and what happens when a session runs long, drops or comes back later. Plan these on purpose.

Decide what is fixed at the start

The voice, the core instructions and the worker are chosen when a conversation begins. Further instructions and facts can be added along the way, but a different voice means a new conversation. You can also begin with a head start, such as a summary of last time or the details you already hold, so nobody has to repeat themselves.

Making the first words dependable

If Athena speaks first, tell it which language to use, what to say and to stop and listen afterwards. Then check that the greeting really played. A generated opening can vary, and now and then it will not come at all. When the wording has to be exact, or you need to know exactly when it ended, play a recording.

Disclosures need proof, not hope

If something must be said, such as a notice that the call is recorded, send it as a direction with the exact wording, since ordinary updates may be rephrased. Then verify it. An instruction being accepted only tells you that it arrived, and it does not tell you that anyone heard it. Check the audio that was produced. Where the law or your policy calls for exact words and evidence of playback, use a recording.

Long conversations

On long sessions, Athena condenses older parts of the conversation so that it can carry on. In practice, early details may survive only in summary. So anything that matters, like confirmed choices, completed actions and the current state of a task, should be stored outside the conversation and supplied again when needed. Long-running work should keep its own record of progress for the same reason.

Picking up after a drop

Save your task state as you go. When someone returns, start again with that history, and check on anything that was in flight before doing it again. If an order went through just before the line dropped, confirm that first. Send fresh results to the new conversation only, so that a late answer from the old one cannot overwrite newer work.

Do not leave sessions open

An open but silent session is still a running session, and a muted microphone does not end it. If your product has long gaps, close after a period of inactivity once audio has finished and no work depends on it. Offer an obvious way back, and restore the context when the person returns. If you restart as soon as someone speaks, hold on to their first words while the new session connects, so that nothing is lost.

Ending well

Finish or cancel outstanding work before you close, then make sure the session really has closed. Record why each one ended, since a normal goodbye, a time limit, a safety stop and a lost connection all call for different follow-up.

Checklist

  • The greeting is verified in audio.
  • Required disclosures are confirmed as played.
  • Important facts are stored outside the conversation.
  • Returning after a drop does not repeat completed work.
  • Idle sessions close by themselves.