Heads-up SMS (meetings)
A heads-up SMS is the short text message the agent sends before a scheduled meeting to confirm the meeting bot is dispatching, give the user options to switch modes or skip recording, and surface any context the user should bring.
Why it matters
Meeting recording tools that just-show-up-without-warning are a privacy and consent problem. The user might be entering a meeting where they specifically do not want a recording (a sensitive HR conversation, a client they have not gotten consent from, a personal call that ended up on the calendar). Without a heads-up, the bot dispatches and the user has no chance to intervene.
The heads-up SMS is the consent layer. A few minutes before the scheduled start, the agent texts: "Meeting with [other party] at 2pm. Bot will record unless you say STOP. Reply INVISIBLE to record in browser instead, or SKIP to not record." The user has 60 seconds to redirect or cancel.
This solves three real problems:
- Privacy by default. The user always knows when the agent is about to record.
- Mode switching. If the meeting context is sensitive, the user can switch to invisible mode (their own browser, no external bot) or skip entirely.
- Recording fatigue. Users who never want recordings can tell the agent generally "do not record meetings" and the heads-up disappears for that user.
The interaction is short. Most users acknowledge by ignoring the heads-up (silence = proceed with bot mode); the small fraction that need a different mode have the option.
How Ajeris handles this
Ajeris's meeting agent sends a heads-up SMS to the user during the pre-dispatch window. The message is short: meeting name, scheduled time, default mode, and the three reply commands (STOP, INVISIBLE, SKIP). Replies parse into the agent's session config in seconds.
Users who consistently want a different default can change it in their Soul preferences; the heads-up reflects the new default.
