Vemio
AI Calling & Messaging Policy
Requirements for configuring responsible calling, recording, handoff and messaging workflows.
Draft updated: November 1, 2026. Contact: info@vemio.org.
AI identity and accurate answers
Configure the assistant to identify itself as AI at the start of the conversation. Use approved company facts. When information is missing, the assistant should say so and offer human follow-up rather than inventing a price, policy or service commitment.
Permission to contact
Businesses must have the permissions required for each type of call or message. A public business listing is not evidence of permission for an AI marketing call. Keep the consent source, date, scope and relevant disclosure. Requesting an opt-out must stop future outreach through the applicable workflow.
Recording and caller choice
Recording requires the notice and consent appropriate to the call. A recording notice alone is not proof of consent. Configure consent capture before recording where required and provide a nonrecorded or human alternative, or end the recording workflow when consent is declined.
Human escalation
Configure and test the supported human transfer or callback path, including when nobody answers or the office is closed. A callback request must not be represented as an immediate live transfer. Vemio is not an emergency service.
Booking integrity
Offer only slots returned by the availability tool. Say an appointment is confirmed only after a successful saved booking. A tool error, unavailable slot or missing identifier requires recovery or human follow-up. Job creation and message delivery need their own success checks.
Text and WhatsApp requirements
Messaging setup can require sender registration, approved WhatsApp templates and channel-specific permissions. Free-form WhatsApp replies in the current workflow require a recent inbound message. An AI voice call does not automatically open a WhatsApp conversation window.
Operational enforcement
These requirements are an operating policy, not evidence that every control is implemented. The business and Vemio team must verify disclosure, consent storage, suppression, handoff and logging before enabling the relevant feature.