SMS quiet hours and calling windows — fleet-wide policy. Under Fulcrum Cortex, Fulcrum Lyre is the voice specialist in the fleet — powered by the Australian stack at lyre.au — so every call and SMS is orchestrated with Sessions, logged to CRM, and reported back in Discord, Telegram, WhatsApp or Slack. Think VAPI-class voice agents — then add AU data residency, ACMA/DNCR-aware calling, SMS in the same cadence, and Cortex orchestration.
Why this matters for operators
Calls open the conversation; SMS carries the proof, links and reminders so nothing dies in voicemail.
- Trigger outbound or inbound voice from a channel message or form event.
- Lyre talks, qualifies and books — natural en-AU conversation, not a robocall.
- SMS confirms, reminds, re-engages and sends links the moment the call ends (or if nobody answers).
- Cortex keeps the audit trail: human hours saved, not another siloed dialler login.
Call + SMS as one workflow
A strong cadence is call → voicemail/no-answer SMS → second call → confirmation SMS on book. Cortex runs that cadence; Lyre executes the voice; SMS carries the thread between attempts.
Deep dive: lyre.au
For the sovereign voice API — Australian data residency, sub-500ms voice-to-voice, ACMA/DNCR-aware calling, PSTN + WebRTC — read and build on lyre.au. Cortex is the execution layer that makes that API an operator-facing fleet member.
Keywords this guide targets
Primary: SMS quiet hours Australia, AI calling windows ACMA. Related fleet intent: AI phone agent Australia, SMS automation after call, Fulcrum Lyre, speed to lead, voice AI CRM logging.
Human hours returned
Every connected call, qualified lead and SMS confirmation is equivalent human labour Lyre absorbed. Measure connect rate, book rate and SMS reply rate — then watch human hours climb in Cortex.