AI Use & Compliance
Our goal is to provide managed AI receptionist workflows that are transparent, appropriately limited and reviewed before launch. We configure each deployment for the customer's approved business purpose.
1. AI transparency
Where an AI receptionist interacts with callers, the configured greeting should identify the system as an AI assistant or virtual receptionist and should not falsely claim to be a human employee. Customers may approve the wording, subject to applicable disclosure requirements.
2. Approved scope and knowledge
We configure the agent using customer-approved business information, including services, hours, service areas, FAQs, lead questions and handoff instructions. Agents should not invent prices, availability, guarantees, credentials or policies. Unknown or unsupported questions should trigger a safe response or human handoff where configured.
3. Recording, transcription and messaging
Recording, transcription and SMS features should be enabled only after the customer selects and approves the configuration. Our voice-agent platform is Retell AI when used in a deployment; its platform may process call audio, transcripts, summaries and communications metadata, and may use telecommunications providers and other subprocessors. Customers are responsible for required notices, permissions, consent records, opt-outs and jurisdiction-specific rules. Provider settings, terms and data-processing arrangements must be reviewed for each deployment. See our Recording & Transcription Notice and SMS Terms.
4. Outbound communications
Outbound AI-voice calls and automated texts are restricted to specifically approved use cases. Customers must supply evidence of legally sufficient consent where required, maintain suppression and do-not-contact lists, honor revocations and ensure scripts and campaigns comply with applicable laws and provider rules. A customer must not assume that an inbound receptionist configuration authorizes outbound marketing.
5. Escalation and high-risk topics
Customers should define a human contact or other fallback for urgent, sensitive, disputed or unsupported requests. AI receptionists are not emergency services and must not be positioned as a substitute for medical, legal, financial or other professional judgment. The agent should direct emergencies to appropriate emergency resources rather than attempting to manage them independently.
6. Testing and maintenance
Our managed-service process is intended to include review of the approved greeting, business knowledge, caller questions, lead capture, transfer rules and failure scenarios before launch, followed by plan-based maintenance and customer-requested updates within the agreed scope. Customers should report incorrect responses or workflow changes promptly and review important call outcomes.
7. Customer duties and enforcement
Customers are responsible for lawful instructions, accurate content, caller permissions, staff readiness, and the way they use call data. We may reject or disable configurations that we reasonably believe facilitate unlawful, deceptive, abusive or unauthorized activity. We may request changes or pause service while a material risk is addressed.
8. Questions
For questions about a deployment or its controls, contact admin@aivirtualreceptionist.online.
Privacy Notice · Terms of Service · AI Use & Compliance · Recording Notice · SMS Terms
Operated by Solomon Jarman, an individual sole proprietor. SIMIAPP CLOUD is an intended trade name; its Clark County fictitious firm name filing has not yet been completed.