# Ecosystem Touchpoints

Below you can find common channels and means of contacts used by Node Operators to enable tailored communications across the diverse types of stakeholders.

{% hint style="info" %}
Stakeholders highly individual and therefore preferences for communication channels can differ. These individual channel preferences need to be identified in advance.
{% endhint %}

### 🖥️ **Website**

* Service offering
* Contact details
* Target Group: [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders), [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#mixed-stakeholders)

### **@ Email**

* Available for any means of contact
* Target Group:  [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders), [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#mixed-stakeholders)

### **🔔 Telegram (Public)**

* Focus on community engagement, incident updates, and information sharing
* Public accessibility to provide contact channels for anonymous stakeholders
* Target Group: [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders), [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#mixed-stakeholders)

### **🔔 Telegram (Private)**

* Direct communication with relevant stakeholders
* Target Group: [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders)

### **💬 Discord/Slack**

* Direct communication channels with relevant stakeholders
* Focus on dialogue, community management, status updates, detailed updates in case of incidents and mitigations
* Target Group:  [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders), [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#mixed-stakeholders)

### **🗯️ X (Twitter)**

* Focus on marketing, high-level publication of updates, information in case of incidents, and mitigations
* Target Group:  [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#known-stakeholders), [Stakeholder Overview](/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/stakeholder-overview.md#mixed-stakeholders)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/communications-toolkit/stakeholder-strategy/ecosystem-touchpoints.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.