> ## Documentation Index > Fetch the complete documentation index at: https://hiremav-mintlify-84cd4ac7.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # SMS Conversations in Mav.next: Two-Way AI Texting > How Mav.next agents hold natural two-way SMS conversations — message timing, texting hours, and built-in HELP and STOP keyword handling. SMS is where most conversations start. A Mav.next agent texts each contact and holds a natural, two-way conversation — qualifying, answering questions, and following up. ## A natural back-and-forth The agent reads each reply in the context of the whole conversation and responds like a person would. If a contact fires off several texts in a row, the agent waits a moment and treats them together rather than replying to each fragment — so the exchange feels natural, not robotic. ## Texting hours Mav.next only sends outbound texts within appropriate hours, so your outreach stays courteous and compliant. Off-hours messages wait until the contact's window opens. State-specific timing rules are also enforced automatically — see [State rules](/mav-next/state-rules). ## Built-in keyword handling Every customer-facing agent honors standard messaging keywords automatically: * **STOP** (and similar opt-out words, in English and Spanish) — unsubscribes the contact immediately. * **HELP** — returns a support response. The first outbound message of a conversation also carries the required rate/HELP/STOP disclosure. See [Opt-out & HELP](/mav-next/opt-out-and-help). ## Moving to a call An SMS conversation isn't limited to text. When it makes sense — or the contact texts “call me” — the agent can place a [phone call](/mav-next/voice) and continue the same conversation by voice, then return to SMS afterward. Everything said over SMS and voice lives in one thread, so the agent never loses context when the channel changes. See [How Mav.next works](/mav-next/how-mav-works).