# Scan: GetVocal AI agents > GAMMA-Ray v0.0.155 (beta, for review; every rating is experimental). An example GAMMA-Ray beta rating of GetVocal AI agents: freedom 1, 4, 1, 1 across its configurations; deployment governance not assessed. > Page: https://gamma-ray.sgit.ai/scans/getvocal-agents/ · Source: data/scans/getvocal-agents.json Example · beta rating · a product as its vendor documents it · read 2026-11-10 · not seen by the vendor GetVocal AI's voice, chat, WhatsApp and email agents for enterprise contact centres, built in its Agent Builder and supervised by people through its control console. A scan of a product as its vendor documents it, not of any one deployment. Made by the report studio: a researcher-assessor, a challenger, then the scorer. I56 is shown for the AI-disclosure fact; the Openness 1 level stands on I20 and I58. Built only from GetVocal AI's own public product, blog, customer-story, privacy and status pages, and its published llms.txt. Nothing was tested. If you are the vendor and something here is wrong, the correction will be made and dated. *Figure. The label for this rating; its contents are in the text.* 1 Freedom as shipped Answers 4 Freedom at most Acts widely 11 Controls it brings as shipped n/a Deployment governance not assessed ## How to read it This is a product, not a deployment. A product has no owner, no policy in force and no mandate until somebody runs it, so it is given **no governance level and no level held**: those belong to a deployment. What a product has is a freedom level for each way it can be configured, and a list of the controls each configuration brings. *Figure. The freedom level of each configuration; the table has the same.* | Configuration | What changes | Freedom | Controls | Turned on by the operator | |---|---|---|---|---| | **As shipped** | Agents built in Agent Builder and run on the platform with its defaults. | 1 Answers | 11 | nothing | | **With human validation nodes** | The customer's operators set which steps need a person's validation, approval or consultation before the agent proceeds. | 4 Acts widely | 12 | the agent handles routine tasks; the person is consulted on exceptions; the agent works independently; the person approves critical decisions only; high-impact actions need a person's approval | | **With a disclosure node** | The deployment opens each conversation by saying the customer is speaking with a virtual assistant; seen in one deployment, not stated as a default. | 1 Answers | 12 | it tells the people it talks to that it is an ai | | **Several agents in the Control Center** | The customer runs several agents, with conversations routed between them. | 1 Answers | 11 | nothing | The same product is a different agent in each row. A rating of a deployment starts by saying which row it is. An indicator with no evidence is reported as not evidenced; it is never read as a no. ## The profile *Figure. One square per indicator, by question; every answer is listed below.* ## The grant: what it can actually do The questions measure what is said about an agent: its purpose, its rules, its controls. The grant is the other half: what its permissions let it do, capability by capability, and what stands in the way of each. This is RiskMandate's measurement, and it depends on the permissions a deployment was given. **Not measured.** Not measured. No deployment shape for this product is published in the capability grammar. ## Seen, and not credited - There is a way to pause or stop the agent (I39). The pages describe operators taking over one conversation and supervisors overriding an agent; pausing appears only as advice on what a kill switch should include, not as a described GetVocal feature. [Source](https://www.getvocal.ai/control-tower) ## What its evidence reaches *Figure. The mashup graph with this agent's evidenced indicators lit.* ## Every answer, with its source ### What is the agent built on? - *Not evidenced.* It is a vendor's assistant, used as supplied. - *Not evidenced.* It runs on an AI platform with the organisation's own data, without executing arbitrary code. - **As shipped.** It is configured on a low-code or no-code builder and acts on real organisational data. Agent Builder is described as a no-engineering builder that makes agents from the customer's SOPs, transcripts and policies. [Source](https://www.getvocal.ai/llms.txt) (documented) - *Not evidenced.* It generates and executes code with local or cloud privileges. - *Not evidenced.* It is built in-house: the organisation controls its identity, tools and boundaries. ### Does it act, or only answer and recommend? - *Not evidenced.* It follows fixed rules, with no reasoning. - *Not evidenced.* It retrieves information and recommends actions; a person acts. - **As shipped.** It executes actions itself. An FAQ answer on the voice page (the CRM question) says agents write to connected systems through scoped integrations, such as updating a booking or a customer record. [Source](https://www.getvocal.ai/voice) (documented) - **As shipped.** It is in production: a public source names a customer or gives usage figures for what it does on its own. GetVocal's Nicomatic story names the customer and says its assistant Sam logs confirmed production events in the ISO database, notifies the supervisor and escalates when required. [Source](https://www.getvocal.ai/customers/nicomatic) (documented) ### How far does it reach? - *Not evidenced.* It works in one domain's data. - **As shipped.** It works across several domains or systems. The llms.txt says the agents work across the customer's CRM, CCaaS, telephony and helpdesk systems. [Source](https://www.getvocal.ai/llms.txt) (documented) - **As shipped.** It connects to external tools or services across a trust boundary. The handoff payload is described as sent over a REST API to the agent desktop, naming Genesys Cloud and Salesforce integrations. [Source](https://www.getvocal.ai/blog/ai-agent-escalation-logic-human-handoff) (documented) ### Does it work with other agents? - *Not evidenced.* Several agents coordinate inside the organisation. - *Not evidenced.* Agents operate across organisational boundaries or disparate stacks. - *Not evidenced.* There is a published protocol or communication layer between agents. - *Not evidenced.* Others build on it: third parties publish integrations, skills or agents for it. - *Not evidenced.* It exposes an agent interface: a published MCP server, an agent card, or an API documented for agents to call. ### What is the person's role? - *Not evidenced.* The person operates: every action is prompted and controlled by them. - *Not evidenced.* The agent suggests; the person reviews and approves each action. - **Available, if the operator turns it on.** The agent handles routine tasks; the person is consulted on exceptions. The Control Tower page says the agent consults a human expert on edge cases. [Source](https://www.getvocal.ai/control-tower) (documented) - **Available, if the operator turns it on.** The agent works independently; the person approves critical decisions only. The Control Tower page says the agent asks a human to approve critical decisions before executing them. [Source](https://www.getvocal.ai/control-tower) (documented) - *Not evidenced.* The agent has full autonomy within boundaries; the person monitors. ### Is what it is for written down? - **As shipped.** Its purpose and permitted tasks are stated in writing. The llms.txt says the agents resolve customer conversations end to end inside the customer's business rules, with human approval on high-stakes actions; the Control Tower FAQ says the agent cannot take actions its graph does not contain. [Source](https://www.getvocal.ai/llms.txt) (documented) - **As shipped.** Its autonomy limits and the tools it may use are defined. Each node of an agent's graph is described as defining the data it may access, its outputs and its escalation conditions. [Source](https://www.getvocal.ai/blog/eu-ai-act-compliance-customer-service-ai-agents) (documented) - *Not evidenced.* Its limits and known failure cases are documented for those who use it. ### Does it have its own identity and only the access it needs? - *Not evidenced.* What it can reach is enumerated: scopes, permissions, tools. - *Not evidenced.* Its authorisation is published as metadata that anyone can read. - *Not evidenced.* It asks for narrower access than the whole account. - *Not evidenced.* It has its own identity, separate from any person's. - *Not evidenced.* Its identity is cryptographic and can be checked by others. - *Not evidenced.* Its tokens are bound to the service they were issued for and are not passed on. ### Is it in a registry, with an owner? - *Not evidenced.* The organisation keeps a registry of its agents. - *Not evidenced.* Each agent has a named owner. - *Not evidenced.* Agents are retired by a defined process. ### Who is accountable for it? - *Not evidenced.* A named executive or body is accountable for the organisation's agents. - *Not evidenced.* Roles and responsibilities for AI risk are documented. ### Is there a policy that governs it? - *Not evidenced.* A governance policy for agents is published. - *Not evidenced.* Agents and use cases are classed by risk. - **As shipped.** The laws that apply to it are identified. The llms.txt names GDPR and the EU AI Act as the frameworks the platform is aligned with. [Source](https://www.getvocal.ai/llms.txt) (documented) - *Not evidenced.* New agents pass an approval or review before they run. ### Can a person step in or stop it? - **Available, if the operator turns it on.** High-impact actions need a person's approval. llms.txt says high-stakes actions such as large transactions, high-value returns and sensitive data get human-in-the-loop approval. A GetVocal blog on escalation says operators configure, in the Control Tower's Operator View, which decision nodes require validation. [Source](https://www.getvocal.ai/llms.txt) (documented) - *Not evidenced.* There is a way to pause or stop it. - **As shipped.** There is a defined escalation path. An FAQ answer on the voice page (the hallucination question) says requests outside the agent's authority are escalated to a human operator. [Source](https://www.getvocal.ai/voice) (documented) ### Is what it does logged? - **Claimed, not counted.** Its actions are logged. The vendor describes an audit trail for each agent action, recording the graph node, data sources accessed and timestamp. [Source](https://www.getvocal.ai/blog/ai-agent-escalation-logic-human-handoff) (documented; this fact has to be observed or measured to count) - *Not evidenced.* The log is tamper-evident and kept for a stated time. ### Is it watched while it runs? - *Not evidenced.* It is monitored in operation. - *Not evidenced.* Anomalies are detected in real time and raise alerts. ### What stands between it and what it should not do? - *Not evidenced.* A limit on it is enforced by something outside its own reach. - *Not evidenced.* A limit on it is a setting that its own account could change. - *Not evidenced.* A limit on it is a rule in prose. - **Claimed, not counted.** Policy is enforced as machine-readable rules. An FAQ answer on the Control Tower page says agent actions are limited to those present in the business-rule graph. [Source](https://www.getvocal.ai/control-tower) (documented; this fact has to be observed or measured to count) - *Not evidenced.* The difference between what it can reach and what it is for is stated. ### Is it tested, and are the results shown? - *Not evidenced.* Test or evaluation results are published. - *Not evidenced.* It is tested for safety and security, including by attack. - *Not evidenced.* People who did not build it take part in assessing it. ### What happens when it goes wrong? - *Not evidenced.* There is an incident process for agents. - **As shipped.** Incidents and errors are communicated to those affected. The public status page publishes incident reports with timed updates, including a call platform outage on 28 September 2026. [Source](https://status.getvocal.ai/events) (documented) - *Not evidenced.* There is a plan for a failure of a third party it depends on. ### Do people know it is an AI, and can they answer back? - **Available, if the operator turns it on.** It tells the people it talks to that it is an AI. In one deployment for an unnamed large Spanish telecom operator, each call opened with a disclosure that the caller was speaking with a virtual assistant. No GetVocal page states that agents disclose they are AI by default or documents a disclosure setting; the EU AI Act blog advises deployers to add a disclosure node. [Source](https://www.getvocal.ai/customers/large-spanish-telecom) (documented) - *Not evidenced.* There is a channel to report problems with it or contest its output. - **As shipped.** It is machine-readable for agents: it publishes an llms.txt, an AGENTS.md, an API description or an agent card. An llms.txt resolves at the site root (fetched 2026-11-10). [Source](https://www.getvocal.ai/llms.txt) (observed) ### What data does it use, and under what rules? - **As shipped.** The data it uses is described. The agents are described as grounded in the customer's call scripts, help documents, CRM records and past transcripts. [Source](https://www.getvocal.ai/enterprise-ai-agents) (documented) - *Not evidenced.* There are data quality rules for what it reads. - *Not evidenced.* Its privacy risk has been examined. ### What does it depend on from others? - *Not evidenced.* The models and third-party components it uses are listed. - *Not evidenced.* Third-party components are monitored and have risk controls. ### Has anyone independent checked? - *Not evidenced.* A public certificate or audit report covers it. - *Not evidenced.* Compliance evidence is produced continuously, ready for a regulator. ### Is the organisation behind it ready? - *Not evidenced.* There is a stated strategy for agents. - *Not evidenced.* The people who work with it are trained. - **As shipped.** Its value is measured. The Control Tower dashboard is described as tracking KPIs, escalation trends and CX quality. [Source](https://www.getvocal.ai/control-tower) (documented) - **As shipped.** It is improved on a regular cycle. Corrections, escalations and validations are described as fed back to refine the agents continuously. [Source](https://www.getvocal.ai/enterprise-ai-agents) (documented) - *Not evidenced.* The organisation's risk management covers agents. ## The vault This rating, its evidence list, its grant and the questions it was made against are kept in a public sgit vault (`qiamk6dj`, published 2026-11-10). Anyone can read it with this key: `sgit_public_read_b46064eedc934cdbb18761e1da1a30140af1ba5f7bc05ed56a8b7e95e45b44d4:qiamk6dj` With [sgit](https://sgit.ai/): `sgit clone sgit_public_read_b46064eedc934cdbb18761e1da1a30140af1ba5f7bc05ed56a8b7e95e45b44d4:qiamk6dj`. The key reads; it cannot write. An operator who wants to add what only they hold forks the vault into a private one.