Ongoing Communication

How to stay connected with ChainPatrol for effective brand protection

Effective brand protection requires clear, ongoing communication between your organization and ChainPatrol. This guide outlines the channels, processes, and best practices for staying connected.

Communication Channels

We use multiple channels to stay in touch with our customers:

Telegram Group

Direct group messaging for quick updates and discussions

Slack Connect

Dedicated channels for enterprise customers

Email

Formal communications via [e-mail] and [e-mail]

Each channel serves different purposes. Use Telegram/Slack for quick questions and real-time updates, and email for formal requests or documentation.

Reporting Threats

Can customers report threats directly to us?

Yes! Customers can report threats through multiple channels:

Telegram

Direct Group Reporting

Share threats directly in your dedicated Telegram group for immediate visibility.

Best for:

• Quick threat reports
• Screenshots and URLs
• Real-time discussions
• Urgent threats requiring immediate attention

Slack

Slack Connect Channel

Post threats in your Slack Connect channel for team collaboration.

Best for:

• Enterprise workflows
• Team coordination
• Documented threat history
• Integration with internal tools

Bot Integrations

Automated Bot Reporting

Use our automated bot integrations to streamline reporting without leaving your workflow.

Benefits:

• Automated threat submission
• Consistent formatting
• Faster processing
• Reduced manual work

Ask your point of contact for setup instructions to enable bot integrations.

Major Events

If your organization has upcoming launches, announcements, or major events, communication is critical:

1. Share Event Details in Advance

   Notify us as soon as you have event details to share

2. We Prepare Resources

   This allows us to dedicate extra monitoring resources and prepare response plans

3. Enhanced Protection

   We can detect and take action on threats faster during your critical moments

Why this matters: Phishing attacks are often timed to coincide with your activities. Product launches, token sales, airdrops, and major announcements are prime targets for scammers.

What to Share

Event Type & Date

• Product launches
• Token sales or airdrops
• Partnership announcements
• Rebrands or major updates
• Conference appearances

Expected Impact

• Anticipated traffic volume
• Social media campaign details
• Press coverage expectations
• Community engagement plans

New Assets

• Landing pages or microsites
• New social media accounts
• Campaign-specific domains
• Promotional materials

Timing & Duration

• Event start and end dates
• Peak activity windows
• Geographic focus areas

Better prepared, better protected: The earlier we know, the faster we can detect and take action on threats.

Organization Assets

Keeping Your Asset List Current

We need an up-to-date list of your organization’s assets to protect them effectively.

Regular Updates

Review and update your asset list periodically (at least quarterly)

New Assets

Notify us immediately when you launch new domains, social accounts, or other assets

How to Update

Contact your point of contact or use the ChainPatrol dashboard

The more complete your asset list, the better we can protect your brand and avoid false positives.

When to Update Your Assets

Immediate Updates

Notify us immediately for:

• New domain registrations
• New social media accounts
• New mobile applications
• New blockchain addresses
• New team member accounts
• Acquired brands or companies

Regular Reviews

Schedule quarterly reviews for:

• Deprecated assets to remove
• Temporary campaign assets
• Employee turnover updates
• Rebranded assets
• Changed contact information

Event-Driven Updates

Update before major events:

• Product launches
• Marketing campaigns
• Partnership announcements
• Organizational changes

Threat Snapshots

What are threat snapshots?

Threat snapshots are point-in-time records of detected threats targeting your organization.

Complete View

A comprehensive record of the threat at the moment of detection

Visual Evidence

Screenshots and archived content

Technical Details

Domains, IPs, and hosting information

Action Timeline

When detected and when action was taken

What data do they contain?

Each snapshot includes comprehensive information:

Visual Evidence

• Screenshots of the malicious content
• Archived copies of web pages
• Social media post captures
• Visual similarity analysis

Technical Metadata

• Domain information (WHOIS, DNS records)
• Hosting details (provider, IP addresses)
• Infrastructure data (CDN, nameservers)
• SSL certificate information

Detection Details

• When the threat was first detected
• Which detection rules triggered
• Confidence scores and risk levels
• AI analysis results

Action History

• Takedown requests submitted
• Provider responses received
• Status updates and timeline
• Final resolution outcome

Threat snapshots are available in your ChainPatrol dashboard and can be exported for internal reporting or compliance purposes.

Customer Feedback Meetings

We schedule regular feedback sessions to ensure we’re meeting your needs.

What We Discuss

Threat Activity

Review recent threats:

• Volume and trends
• Attack patterns
• High-severity incidents
• Response effectiveness

Detection Accuracy

Evaluate performance:

• False positive rates
• Missed threats
• Detection speed
• Coverage gaps

Service Feedback

Share your experience:

• What’s working well
• Pain points or challenges
• Communication effectiveness
• Documentation needs

Feature Requests

Discuss improvements:

• New integrations
• Custom workflows
• Reporting enhancements
• Platform features

Your ChainPatrol representative will coordinate scheduling for these meetings, typically held quarterly or as needed.

Your Points of Contact

Dedicated Support Team

Meet your ChainPatrol team members and their areas of expertise:

Michael - Bot Engineer & Customer Support

Areas of expertise:

• Bot integrations and technical support
• Day-to-day customer inquiries
• Automated reporting setup
• Integration troubleshooting

When to contact Michael:

• Setting up bot integrations
• Technical support questions
• General customer inquiries
• Integration issues

Dave - Customer Success Lead

Areas of expertise:

• Strategic partnership and account management
• Service optimization and feedback
• Onboarding and training
• Long-term success planning

When to contact Dave:

• Strategic discussions
• Service optimization
• Feedback and feature requests
• Account management questions

Maksym - Founding Engineer

Areas of expertise:

• Technical concerns about application stability
• Canary tokens integration support
• Advanced technical implementations
• Platform architecture questions

When to contact Maksym:

• Application stability issues
• Canary token integrations
• Complex technical implementations
• Platform architecture discussions

Reach out to your designated contact for any questions or concerns. If you’re unsure who to contact, start with your primary point of contact and they’ll route you appropriately.

Best Practices for Communication

Be Proactive

Don’t wait for issues to escalate—reach out early and often

Provide Context

Include relevant details, screenshots, and URLs when reporting threats

Use Appropriate Channels

Match urgency to channel (Telegram for urgent, email for formal)

Keep Assets Updated

Regularly review and update your organization’s asset list

Share Event Plans

Give advance notice of launches and major announcements

Attend Feedback Meetings

Participate in regular check-ins to optimize service

---

Quick Reference

Need	Channel	Contact
Urgent threat report	Telegram/Slack	Your dedicated group/channel
Bot integration setup	Email/Telegram	Michael
Strategic discussion	Email/Slack	Dave
Technical issue	Email/Telegram	Maksym
Formal request	Email	[e-mail]
Dispute submission	Email	[e-mail]

---

Need to Get in Touch?

Contact us at

[e-mail] or reach out through your dedicated communication channel