Less uncertainty at the start of a call
Give customers a way to check the organisation-created session before discussing their account.
Call & SMS verification
Give customers a way to check it’s you.
Let customers check a call or text against a session created by your organisation, then confirm the session together with a rotating return code.
For contact centres and high-trust customer communications.
Keep your existing contact centre
Add verification alongside your current phone and SMS providers, inside your agent workflow.
A confirmation you can record
Complete the two-way check once and connect its result to the customer conversation.
Explore the experience
A conversation both sides can confirm.
Your agent creates a session. Your customer checks it independently. A return code connects the two sides.
Your team
A verification step in your agent workflow
Organisation workspace
Agent workspace
Cedar Bank
- Purpose
- Scheduled account review
- Sender
- +44 20 7946 0000
- Session
- Awaiting confirmation
Share this one-time code
M7KP 92XR 4T6D
Create the session through your API integration before contacting the customer.
Your customer
Check before sharing sensitive information
Recipient experience
mimeprotect
Who’s on the other end?
Phone number or sender ID
+44 20 7946 0000
Time received
Today, 10:30
Verification code
M7KP 92XR 4T6D
Create a session before the conversation.
Your contact-centre system calls the API with an approved phone number or SMS sender ID and the purpose of the contact. MimeProtect returns a short-lived session and a one-time verification code for your agent or message.
Give the customer a place to check.
The customer visits MimeProtect independently or uses the verification experience on your own website. They enter the sender, the time they received the contact and the one-time code. The check identifies the organisation-created session.
Confirm the same session on both sides.
The customer sees a return code that rotates every 30 seconds. Your agent sees the corresponding challenge and confirms the code the customer reads back. Successful confirmation consumes the session once and records the result.
Keep the phone system you already use.
Verification sits alongside your existing telephony and SMS provider. Integrate session creation and confirmation into your agent tools, then measure completed checks as part of your normal contact-centre workflow. Start with synthetic sessions in sandbox. Enterprise customers can reserve phone numbers and Sender IDs for their organisation after ownership validation.
Where it fits
Made for the documents and conversations your business relies on.
- Scheduled account and policy reviews
- Sensitive outbound customer-service calls
- Texts that need an independently checkable source
- Contact centres that want a consistent verification step
How it works
- 01
Your authenticated system creates a short-lived verification session for a registered phone number or sender ID.
- 02
The customer visits MimeProtect independently, or your integrated website, and enters the sender, time received and one-time code.
- 03
The customer reads back the return code shown for that session. Both sides see it rotate every 30 seconds; your system confirms it once.
What you get
- One-time codes tied to an organisation and session
- Return codes that rotate every 30 seconds
- Hosted checks and an integration API
- Expiry, attempt limits and replay protection
Your questions, answered.
Do we need to change our phone provider?
No. The verification API sits alongside your existing provider. Your system creates the session and your agent or message shares its one-time code.
What counts towards our usage?
A completed two-way verification. Your subscription provides a monthly allowance; the dashboard tracks completed checks against that allowance.
Can customers verify on our own site?
Yes. Integrate the verification flow through the API, or direct customers to MimeProtect’s verification page. Customers should reach the page through an independently trusted route.
Can we test without contacting customers?
Yes. Sandbox lets your team create synthetic sessions and try the customer and agent steps without sending SMS or placing a call.
Start your next conversation with a way to check it.
Test both sides in sandbox, then connect session creation and confirmation to your agent tools.