Clear controls for customer data and AI actions.
Know how a workspace line is managed, when Vee can contact you, and what sits behind a cited answer. Explore the controls for conversations, customer data and AI actions.
Read the security and administration guide →Phone, SMS and evidence controls reviewed November 2026
A Vee line belongs to one workspace
Workspace administrators provision and manage a dedicated Vee line. The number called identifies the workspace, and phone access checks registered caller identity and workspace membership. An optional PIN adds a check to phone calls.
Personal caller bindings and the outbound-call preference are separate from workspace number ownership. Browser calling uses the signed-in identity and requires its own configuration. Provisioning, recurring number rental, available countries and carrier capabilities determine availability.
Provisioning and line management →Phone and SMS traffic uses Twilio
Twilio processes the phone and messaging traffic used by Call Vee, including call connections, media streams, text messages and carrier delivery callbacks. Vesso validates signatures on Twilio webhook requests and uses callback status to track calls and messages.
Queued, sent to carrier and delivered are distinct states. Provider acceptance does not guarantee delivery. Where configured, Twilio’s opt-out handling supplies carrier acknowledgments and opt-out events; Vesso also checks its own suppression state before sending.
Understand delivery states →Provider reference: Twilio’s Advanced Opt-Out documentation.
Separate consent and suppression for SMS
Automatic text updates require a verified mobile, a selected destination and a separate texting preference for the member in that workspace. STOP suppresses messages for the mobile and Vee-line conversation and turns automatic updates off.
START restores conversational replies; automatic updates remain off until the member explicitly re-enables them in Vesso. Explicit text requests can bypass automatic-update preference and quiet hours, but never STOP suppression or daily limits. These controls describe member-to-Vee messaging, not a permission to text prospects.
SMS consent and opt-outs →Consent depends on the capture workflow
Teams should inform participants and obtain the permissions appropriate to their recording and transcription use. The sales dialer provides recording modes and a configurable consent announcement. These settings do not establish consent for every Call Vee, browser meeting or Mac capture workflow.
Call Vee processes speech and can retain the resulting conversation and debrief. An available voice-note fallback records audio for transcription; Vesso attempts to delete that carrier recording after processing. This is not a promise that audio is never stored. Review the relevant workflow and participant expectations before capture.
Call Vee capture and fallback →Deal Stories link claims to evidence
Deal Stories attach source references to claims and exclude claims without validated evidence references. Readers can inspect available source links, dates, last-confirmed labels, changes and version history. Account and deal access checks still apply.
A citation establishes a traceable source, not a guarantee of accuracy or completeness. Missing sources and stale evidence can limit a story. Buyer-scoped Vee is a separate surface restricted to room documents, selected published knowledge articles and approved sales content; it does not receive internal CRM notes or general account memory.
Reading evidence citations →Scoped, auditable AI connections
MCP connections use explicit scopes for CRM, tasks, meetings, knowledge, and search. OAuth grants act as the approving member, and API keys act as their creator. Vesso checks the credential, workspace, and actor before running tools.
Members can revoke their own OAuth connections; workspace administrators can revoke connections across the workspace. API keys are revoked separately. Tool calls and OAuth lifecycle events are audited, with redacted argument summaries instead of free-text payloads.
MCP scopes, audits, and revocation →Hierarchy enforced in Data Explorer
Data Explorer requires effective read permission and applies ownership and reporting hierarchy to query results. Related records inherit the visibility of their parent or account; workspace-shared sources are classified separately.
These checks apply to visual queries, AI-generated queries, source statistics, and Custom Reports. A source without a visibility classification is withheld from restricted users. Query cost limits also bound joins and row processing.
Data Explorer visibility →Sensitive analytics fields require an administrator
Within Data Explorer and its reporting surfaces, meeting transcripts and summaries, recording URLs, event descriptions, task comment content, and form responses require workspace administrator access.
These fields are removed from non-admin schemas and results. Explicit references are rejected in queries and report grouping or detail requests. Access in the original product surface is governed by that surface’s own permissions.
Sensitive-field boundaries →Separate source content from AI instructions
AI workflows that process agreement text, web research, workspace search passages, and external agent triggers label source material as untrusted data and instruct the model to ignore embedded commands.
Document and trigger boundaries are escaped or sanitized in the applicable prompts. Action guardrails and server-side permissions provide additional checks. These layers reduce prompt-injection risk; they do not make AI output infallible. Review proposed changes and outbound content before acting.
Honor recipient preferences across the workspace
Full email opt-outs are shared across the workspace, so changing reps does not bypass suppression. Category preferences are checked for matching sends, and full unsubscribes end active cadence enrollments for the address.
Supported outreach sends include signed preference links and one-click unsubscribe headers. Administrative removal from the unsubscribe list requires a workspace administrator. These controls support a team’s compliance process without replacing its responsibility for consent, content, and applicable rules.
Unsubscribe and suppression controls →Security fundamentals and review
Vesso uses TLS in transit and encryption at rest in AWS-managed storage. Workspace roles, multi-factor authentication, and administrator exports support everyday control. OIDC single sign-on is included on every business plan; SAML and SCIM are not supported today.
The SOC 2 audit is not yet complete. Contact us to discuss current controls, plan availability, and your security review requirements.
Discuss a security review →