# POST /agent/v1/voice/verify-client

**Resource:** [Voice Agent Toolkit](./agent-toolkit-voice.md)  
**MCP tool:** `voice_toolkit_verify_client`  
**Scopes:** `agent_toolkit:use`  
**Write operation:** yes

Voice agent toolkit: confirm a service caller is an existing client. Their full name, phone and email must all match one CRM contact. Answers yes or no only, never record details or which detail failed. A match unlocks calendar tools whose URL carries require_verified_client=1 for the rest of the call; after two failed checks the hosts of escalate_event_type_id (a tool URL param) get a follow-up task and email.

## Parameters

| Name | In | Type | Required | Description |
|------|----|------|----------|-------------|
| `full_name` | body | string | yes | The caller first and last name, as they said it. |
| `email` | body | string | yes | The caller email address, as they said it. |
| `phone` | body | string | no | The phone number the caller gave. Omit only when they said to use the number they are calling from, and set use_calling_number instead. |
| `use_calling_number` | body | boolean | no | True when the caller said the number they are calling from is the one on file. |
| `reason` | body | string | no | In a few words, what the caller needs help with. |
| `require_approval` | body | boolean | no | Optional. Set true to route this write into the approval queue for human review instead of executing it immediately (returns 202 + an approval_id). Works even when your key/token has permission to execute directly. |

## Request example

```bash
curl -X POST   "https://api.trustpager.com/functions/v1/api/v1/agent/v1/voice/verify-client"   -H "Authorization: Bearer YOUR_API_KEY"   -H "Content-Type: application/json"   -d '{"full_name":"...","email":"...","use_calling_number":true}'
```

---
Base URL: `https://api.trustpager.com/functions/v1/api/v1` — Auth: `Authorization: Bearer YOUR_API_KEY`