> ## Documentation Index
> Fetch the complete documentation index at: https://chainpatrol.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ongoing Communication

> Stay connected with ChainPatrol via Telegram, Slack, and email to report threats, share upcoming events, and keep your organization assets up to date.

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:

> [card] Telegram Group
>
> Direct group messaging for quick updates and discussions

> [card] Slack Connect
>
> Dedicated channels for enterprise customers

> [card] Email
>
> Formal communications via [support@chainpatrol.io](mailto:support@chainpatrol.io) and [disputes@chainpatrol.io](mailto:disputes@chainpatrol.io) (for disputes and false positives). Dispute-related emails sent to the support inbox are automatically forwarded to the disputes workflow.

> [!NOTE]
>
> 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:

> [tab] 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

> [tab] 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

> [tab] 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
>
> > [!TIP]
> >
> > 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

> [!WARNING]
>
> **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

> [accordion] Event Type & Date
>
> * Product launches
> * Token sales or airdrops
> * Partnership announcements
> * Rebrands or major updates
> * Conference appearances

> [accordion] Expected Impact
>
> * Anticipated traffic volume
> * Social media campaign details
> * Press coverage expectations
> * Community engagement plans

> [accordion] New Assets
>
> * Landing pages or microsites
> * New social media accounts
> * Campaign-specific domains
> * Promotional materials

> [accordion] Timing & Duration
>
> * Event start and end dates
> * Peak activity windows
> * Geographic focus areas

> [!TIP]
>
> **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.

> [card] Regular Updates
>
> Review and update your asset list periodically (at least quarterly)

> [card] New Assets
>
> Notify us immediately when you launch new domains, social accounts, or other assets

> [card] How to Update
>
> Contact your point of contact or use the ChainPatrol dashboard

> [!NOTE]
>
> The more complete your asset list, the better we can protect your brand and avoid false positives.

### When to Update Your Assets

> [tab] 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

> [tab] Regular Reviews
>
> **Schedule quarterly reviews for:**
>
> * Deprecated assets to remove
> * Temporary campaign assets
> * Employee turnover updates
> * Rebranded assets
> * Changed contact information

> [tab] 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.

> [card] Complete View
>
> A comprehensive record of the threat at the moment of detection

> [card] Visual Evidence
>
> Screenshots and archived content

> [card] Technical Details
>
> Domains, IPs, and hosting information

> [card] Action Timeline
>
> When detected and when action was taken

### What data do they contain?

Each snapshot includes comprehensive information:

> [accordion] Visual Evidence
>
> * Screenshots of the malicious content
> * Archived copies of web pages
> * Social media post captures
> * Visual similarity analysis

> [accordion] Technical Metadata
>
> * Domain information (WHOIS, DNS records)
> * Hosting details (provider, IP addresses)
> * Infrastructure data (CDN, nameservers)
> * SSL certificate information

> [accordion] Detection Details
>
> * When the threat was first detected
> * Which detection rules triggered
> * Confidence scores and risk levels
> * AI analysis results

> [accordion] Action History
>
> * Takedown requests submitted
> * Provider responses received
> * Status updates and timeline
> * Final resolution outcome

> [!TIP]
>
> 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

> [tab] Threat Activity
>
> **Review recent threats:**
>
> * Volume and trends
> * Attack patterns
> * High-severity incidents
> * Response effectiveness

> [tab] Detection Accuracy
>
> **Evaluate performance:**
>
> * False positive rates
> * Missed threats
> * Detection speed
> * Coverage gaps

> [tab] Service Feedback
>
> **Share your experience:**
>
> * What's working well
> * Pain points or challenges
> * Communication effectiveness
> * Documentation needs

> [tab] Feature Requests
>
> **Discuss improvements:**
>
> * New integrations
> * Custom workflows
> * Reporting enhancements
> * Platform features

> [!NOTE]
>
> Your ChainPatrol representative will coordinate scheduling for these meetings, typically held quarterly or as needed.

## Best Practices for Communication

> [card] Be Proactive
>
> Don't wait for issues to escalate—reach out early and often

> [card] Provide Context
>
> Include relevant details, screenshots, and URLs when reporting threats

> [card] Use Appropriate Channels
>
> Match urgency to channel (Telegram for urgent, email for formal)

> [card] Keep Assets Updated
>
> Regularly review and update your organization's asset list

> [card] Share Event Plans
>
> Give advance notice of launches and major announcements

> [card] Attend Feedback Meetings
>
> Participate in regular check-ins to optimize service

***

## Quick Reference

| Need | Channel | Contact |
| - | - | - |
| **Urgent threat report** | Telegram/Slack | |
| **Bot integration setup** | Email/Telegram | |
| **Strategic discussion** | Email/Slack | |
| **Technical issue** | Email/Telegram | |
| **Formal request** | Email | [support@chainpatrol.io](mailto:support@chainpatrol.io) |
| **Dispute submission** | Email | [disputes@chainpatrol.io](mailto:disputes@chainpatrol.io) |

***

> [card] [Need to Get in Touch?](mailto:support@chainpatrol.io)
>
> Contact us at [support@chainpatrol.io](mailto:support@chainpatrol.io) (or [disputes@chainpatrol.io](mailto:disputes@chainpatrol.io) for disputes and false positives) or reach out through your dedicated communication channel


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.