Sending Validation Requests

Sending effective validation requests is an art. This guide covers everything from crafting the perfect message to handling responses and following up appropriately.

When to Send Validation Requests

High-Priority Situations (Always Validate)

Financial Transactions:

• Wire transfers of any amount

• Payments over 00

• Banking information changes

• Investment decisions

• Real estate transactions

Sensitive Information Requests:

• Someone asking for passwords or credentials

• Requests for Social Security numbers or IDs

• Personal health information requests

• Confidential business data requests

• Legal documents requiring signature

Suspicious Communications:

• Unexpected money requests

• Urgent demands for action

• Communications bypassing normal procedures

• Requests with grammatical errors or odd phrasing

• Messages creating pressure or urgency

Medium-Priority Situations (Validate When Uncertain)

New Business Relationships:

• First-time vendor communications

• New client introductions

• Partnership proposals

• Contract negotiations

• Employment opportunities

Changed Contact Information:

• Updated email addresses

• New phone numbers

• Different bank accounts

• Modified mailing addresses

Out-of-Character Requests:

• Unusual requests from known contacts

• Communications outside normal hours

• Different communication style

• Requests bypassing usual channels

Low-Priority Situations (Optional Validation)

Routine Communications:

• Regular business correspondence

• Known contacts using verified channels

• Social interactions with verified friends

• Newsletter or marketing subscriptions

How to Send Validation Requests

Step-by-Step Process

Step 1: Search for the Identity

• Use TripleValidate search function

• Find the person by email, phone, or username

• Review their ZTRS score and zone level

Step 2: Initiate Validation

• Tap "Send Validation Request" button

• Validation form appears

Step 3: Craft Your Message

• Write clear, specific message (more on this below)

• Include context about what you're verifying

• Keep it professional and concise

• Maximum 500 characters

Step 4: Review and Send

• Double-check your message

• Verify you're sending to correct person

• Tap "Send"

• Request is delivered instantly

Step 5: Track Status

• Request appears in your Validation History

• Status shows as "Pending"

• You'll receive notification when they respond

Crafting Effective Validation Messages

Message Best Practices

Be Specific:

✅ Good: "Can you confirm you sent the wire transfer request for ,000 to Project Alpha?"

❌ Bad: "Is this you?"

Provide Context:

✅ Good: "I received an email from john@company.com asking for sensitive client data. Can you confirm this is your email?"

❌ Bad: "Did you email me?"

Include Details:

✅ Good: "Can you verify the new bank account ending in 4567 for invoice payments?"

❌ Bad: "Is this right?"

Stay Professional:

✅ Good: "Hello, I'm verifying the authenticity of a contract I received. Can you confirm you sent it?"

❌ Bad: "Hey are u legit???"

Be Direct:

✅ Good: "Is sarah.johnson@company.com your email address?"

❌ Bad: "I was wondering if maybe possibly this could be your email?"

Message Templates

Money Request Verification:

"I received a message from [email/phone] requesting 0. Can you confirm you sent this and the details are correct?"

Email Verification:

"Can you verify that [email@domain.com] is your email address? I received [type of communication] from this address."

Phone Number Verification:

"I received a call/text from [phone number] claiming to be you. Can you confirm this is your number?"

Social Media Verification:

"Someone with the handle [@username] on [platform] contacted me claiming to be you. Can you confirm this is your account?"

Banking Information Change:

"I received notification that your bank account has changed to [account ending in XXXX]. Can you confirm this change is legitimate?"

Document Verification:

"I received a [contract/invoice/document] from [email]. Can you confirm you sent this document and it's authentic?"

General Identity Verification:

"I want to verify your identity before proceeding with [transaction/communication]. Can you confirm [specific detail]?"

Message Length Guidelines

Ideal Length: 50-200 characters

• Long enough to provide context

• Short enough to be read quickly

• Gets to the point immediately

Too Short ( 300 characters):

• Rambling explanations

• Unnecessary details

• Multiple questions

• Life story

Just Right:

• "Can you confirm you sent the wire transfer request for 0,000 to vendor XYZ?"

• "I received an urgent email from this address. Is it yours?"

• "Verifying you own the Instagram handle @yourname before sharing sensitive info."

What Happens After Sending

Recipient Experience

They Receive:

1. Push Notification (Immediate)

• Alert on their mobile device

• Shows your username

• Preview of your message

• Tap to open in TripleEnable

2. TripleEnable In-App Notification

• Appears on Home screen

• Full validation request details

• Your message displayed

• Options to Approve/Decline/Ignore

3. Email Notification (within minutes)

• Sent to their TripleEnable email

• Contains validation details

• Link to respond in app

Response Timeline

24-Hour Window:

• Request automatically expires after 24 hours

• Most responses come within 1-4 hours

• Urgent requests often answered within minutes

• Business hours requests typically faster

Typical Response Times:

• 1-2 hours: Most common for legitimate requests

• 2-6 hours: If recipient is busy or away from phone

• 6-12 hours: May be sleeping or in different timezone

• 12-24 hours: Unusual delay, may indicate issue

• No response: Could be suspicious or recipient not checking app

Understanding Response Statuses

⏳ Pending (Awaiting Response)

What It Means:

• Request has been sent

• Recipient hasn't responded yet

• Still within 24-hour window

Your Action:

• Wait for response

• Check periodically for updates

• Don't proceed with transaction yet

• Consider urgency level

When to Follow Up:

• After 6 hours for urgent matters

• After 12 hours for important matters

• After 24 hours (request expires)

✅ Approved (Asset Confirmed)

What It Means:

• Recipient confirmed ownership

• Identity verified

• Asset belongs to them

• Safe to proceed

Your Action Based on Risk:

Low-Risk Transactions ( ,000):

• Proceed with additional verification

• Call to verbally confirm

• Use multiple verification methods

• Document everything thoroughly

Best Practice: Even with approval, follow your normal security procedures for high-value transactions.

❌ Declined (Ownership Denied)

What It Means:

• Recipient says asset is NOT theirs

• Communication was NOT from them

• MAJOR RED FLAG

• You're being targeted by scammer

Immediate Actions:

1. STOP Everything

• Do not send money

• Do not share information

• Do not proceed with transaction

• Do not respond to original message

2. Document the Fraud

• Screenshot the declined validation

• Save original communication

• Note all details (time, date, content)

• Prepare evidence

3. Report the Incident

• Report in TripleValidate

• Alert the real person (their account may be compromised)

• Report to your IT/security team (if business)

• File police report for significant fraud attempts

4. Warn Others

• Alert colleagues if business scam

• Inform friends/family if personal scam

• Report to relevant authorities

• Help protect community

Example Scenario:

You validate an email asking for 0,000 wire transfer. Recipient declines - they never sent it. You just prevented a 0,000 loss!

⏰ Expired (No Response in 24 Hours)

What It Means:

• Recipient didn't respond within 24 hours

• Request is now closed

• Cannot be reopened

Possible Reasons:

Legitimate:

• Recipient is traveling without phone access

• In a location with no internet

• Very busy and missed notifications

• Doesn't regularly check TripleEnable

• Different timezone and unusual hours

Suspicious:

• Scammer avoiding validation

• Compromised account

• Fake identity

• Deliberately ignoring to pressure you

Your Action:

For Urgent Matters:

• Use alternative verification (phone call)

• Contact through different channel

• Verify through mutual connections

• DO NOT proceed without verification

For Non-Urgent Matters:

• Send new validation request

• Try different contact method

• Wait for them to reach out

• Proceed with extreme caution

Decision Matrix:

Transaction ValueRisk LevelAction

Any amountUnknown personDO NOT PROCEED Known contactProceed with caution 00-,000Known contactCall to verify

,000Known contactDO NOT PROCEED until verified Any amountSuspicious contextDO NOT PROCEED

Following Up on Validations

When to Resend

Appropriate Times:

• Original request expired with no response

• Recipient says they missed the first one

• New information has emerged

• Different asset needs validation

How Long to Wait:

• 24+ hours after expiration

• At least 48 hours between requests

• Don't spam the same person

When to Use Alternative Methods

Call Instead:

• Urgent matters (wire transfers, emergencies)

• High-value transactions (> 0,000)

• No response after 6-12 hours

• Multiple expired validations

Email/Text Instead:

• Recipient may not use TripleEnable regularly

• Need to explain validation process

• Can provide more context

When to Escalate

Escalate to Management/Security:

• Declined validation on business transaction

• Pattern of suspicious requests

• Multiple fraud attempts

• Account compromise suspected

Validation Request Limits

Rate Limits

Per User:

• 10 validation requests per hour

• 50 validation requests per day

• Prevents spam and abuse

Per Target:

• 3 requests to same person per day

• Prevents harassment

• Multiple requests flagged

If You Hit Limit:

• Wait for reset period

• Use alternative verification methods

• Contact support if urgent business need

Best Practices Summary

DO:

✅ Be specific about what you're verifying

✅ Provide context in your message

✅ Wait for response before proceeding

✅ Document all validations

✅ Use multiple verification methods for high-risk transactions

✅ Report declined validations

✅ Follow up through other channels if no response

DON'T:

❌ Send vague validation requests

❌ Spam the same person repeatedly

❌ Proceed without response on high-risk matters

❌ Ignore declined validations

❌ Rely solely on TripleValidate for critical transactions

❌ Share sensitive info in validation message

❌ Use TripleValidate for harassment

Troubleshooting

Cannot Send Validation:

• Verify you have Secure Zone access

• Check that recipient is findable (not Anonymous Zone)

• Ensure recipient's privacy allows validations

• Check you haven't hit rate limits

Request Not Delivered:

• Verify internet connection

• Check recipient account is active

• Confirm you selected correct person

• Try again in a few minutes

No Response on Urgent Matter:

• Use phone call immediately

• Try alternative contact methods

• Contact through mutual connection

• Don't wait for expiration on urgent matters

Next Steps

Now that you understand sending validation requests:

• Validation History (Section 4.6) - Track and manage all your validation requests

• Advanced & Business Use Cases (Section 4.7) - Enterprise validation strategies

• Navigation (Section 4.8) - Master the TripleValidate interface