Make verification part of the conversation.
Give your agent a way to check the caller’s Microsoft identity, request their Proofcall code and receive a structured result. Keep human and automated support on the same verification workflow.
Your agent handles the call.
Proofcall handles the check.
Use your preferred voice platform. A compatible integration can call Proofcall’s HTTP API or remote MCP server and interpret the outcome without inventing its own identity checks.
See the integration sequence →Illustrative result. The same flow is available to a human engineer.
“First, let’s verify your account.”
The caller completes the authentication step in their browser while the agent waits. If the check cannot be completed, the conversation moves to your escalation process.
01 Start with the right person
Your engineer or AI agent selects the organisation and caller. Proofcall binds the request to that person’s Microsoft identity.
02 Let Microsoft authenticate
The caller opens the verification link and signs in with their organisation. They use an authentication method they already have.
03 Bring proof back to the call
After authentication passes, the caller receives a separate Proofcall code and reads it to the handler. Never ask for a Microsoft sign-in or Authenticator code.
04 Record the result
The handler submits the code. Proofcall returns a result and records the authentication evidence, with the human or automated handler identified.
Verification complete
Verified- Caller
- Maya Patel
- Organisation
- Northstar
- Identity provider
- Microsoft Entra ID
- Verification
- Direct · caller authenticated
- Handled by
- Named engineer / AI agent
- Recorded
- Identity, time and outcome
A record your team can review. Available authentication details are retained with the result. Approver verification is labelled separately.
Connect through MCP or the API.
Download the AI integration brief (PDF) →
Create an agent credential in Proofcall administration, configure its capabilities and connect a compatible client to the remote MCP endpoint. Keep the credential in your platform’s secret store.
POST https://app.proofcall.io/mcp
Authorization: Bearer <your-agent-credential>
Transport: Streamable HTTPUse the following sequence for a direct verification. Agent-initiated requests declare an action tier. Configure and test your own workflow’s requirements before enabling sensitive actions.
| MCP tool | Role in the call |
|---|---|
| proofcall_list_clients | Identify the caller’s organisation. |
| proofcall_find_caller | Find the account and check registered methods. |
| proofcall_start_verification | Create the verification request. |
| proofcall_send_link | Request delivery through a configured channel. |
| proofcall_wait_for_caller | Wait for the authentication state to change. |
| proofcall_submit_code | Submit the Proofcall code read by the caller. |
Status checks and cancellation are also available. Transport compatibility does not establish a tested integration with a particular voice platform.
Design the handoff as carefully as the happy path.
- Ask only for the separate Proofcall code. Never ask for Microsoft sign-in codes or passwords.
- Handle incorrect codes, expired sessions and unavailable authentication methods explicitly.
- Define when the agent must transfer to a person, and preserve the verification reference.
- Apply transcript retention and code-redaction rules in your voice platform.
- Make the system performing the sensitive action enforce your verification policy. A successful identity check alone is not permission to make every account change.
Make your next support conversation a verified one.
Start with one Microsoft tenant and your own team. Follow the caller’s experience, review the result and build verification into your workflow.
14 days · No card required · Microsoft Entra ID P1