diff --git a/docs/guidance/evaluating.md b/docs/guidance/evaluating.md
index 8e1be376..74d09fb4 100644
--- a/docs/guidance/evaluating.md
+++ b/docs/guidance/evaluating.md
@@ -8,7 +8,7 @@ It is not possible to fully automate checks of whether disclosures from a partic
 
 ## Getting started
 
-*The following steps might require support from a technical expert. You can also contact the OC4IDS Helpdesk ([data@open-contracting.org](mailto:data@open-contracting.org)) for guidance.*
+*The following steps might require support from a technical expert. You can also contact the [OC4IDS Helpdesk](../../support) for guidance.*
 
 ### (1) Check your data formats
 
diff --git a/docs/guidance/identifiers.md b/docs/guidance/identifiers.md
index 30be4c74..9f39a961 100644
--- a/docs/guidance/identifiers.md
+++ b/docs/guidance/identifiers.md
@@ -40,7 +40,7 @@ Project identifiers in OC4IDS need to be globally unique; this means that, acros
 
 If local project identifiers are available in existing systems or data, these ought to be reused to create globally unique project identifiers for use in OC4IDS. Otherwise, if local project identifiers are not available, publishers are allowed to assign local identifiers to projects in the new systems used to generate OC4IDS data.
 
-To make local project identifiers globally unique for use in OC4IDS, a publisher requests a project identifier prefix from the [OC4IDS Helpdesk](mailto:data@open-contracting.org). The publisher needs to then use the assigned prefix in all its project identifiers, according to following structure: `[project identifier prefix]-[local project identifier]`.
+To make local project identifiers globally unique for use in OC4IDS, a publisher requests a project identifier prefix from the [OC4IDS Helpdesk](../../support). The publisher needs to then use the assigned prefix in all its project identifiers, according to following structure: `[project identifier prefix]-[local project identifier]`.
 
 For example: CoST Honduras requests a project identifier prefix from the OC4IDS Helpdesk. The OC4IDS Helpdesk assigns the randomly-generated prefix `oc4ids-qu8r7p`. CoST Honduras then creates globally unique project identifiers, by combining its assigned prefix with each local project identifier from its SISOCS system.
 
diff --git a/docs/guidance/language.md b/docs/guidance/language.md
index d43d3071..38b62cf4 100644
--- a/docs/guidance/language.md
+++ b/docs/guidance/language.md
@@ -37,7 +37,7 @@ The fields whose values can be translated are listed in the [internationalizatio
 
 In order to ease access for non-English speakers, instead of using the field *names* as column headers (which are always in English), you can use the field *titles*.
 
-The titles are currently available in English and Spanish. If you would like to translate the titles to your own language, please [contact the OC4IDS Helpdesk](mailto:data@open-contracting.org).
+The titles are currently available in English and Spanish. If you would like to translate the titles to your own language, please contact the [OC4IDS Helpdesk](../../support).
 
 For example, this CSV excerpt uses field titles from the Spanish translation of OC4IDS:
 
diff --git a/docs/guidance/publishing.md b/docs/guidance/publishing.md
index 21e22463..24833267 100644
--- a/docs/guidance/publishing.md
+++ b/docs/guidance/publishing.md
@@ -16,7 +16,7 @@ For example, [Highways England](https://highwaysengland.co.uk/roads/) provides l
 
 ## Getting started
 
-*Some of the following steps might require support from a technical expert. You can also contact the OC4IDS Helpdesk ([data@open-contracting.org](mailto:data@open-contracting.org)) for guidance.*
+*Some of the following steps might require support from a technical expert. You can also contact the [OC4IDS Helpdesk](../../support) for guidance.*
 
 ### (1) Make a commitment
 
diff --git a/docs/guidance/using.md b/docs/guidance/using.md
index b3522c29..aacba558 100644
--- a/docs/guidance/using.md
+++ b/docs/guidance/using.md
@@ -16,7 +16,7 @@ Even when an OCDS publisher does not provide data for every stage of the contrac
 
 ## Getting started
 
-*The following steps might require support from a technical expert. You can also contact the OC4IDS Helpdesk ([data@open-contracting.org](mailto:data@open-contracting.org)) for guidance.*
+*The following steps might require support from a technical expert. You can also contact the [OC4IDS Helpdesk](../../support) for guidance.*
 
 ### (1) Evaluate the Open Contracting Data
 
diff --git a/docs/projects/index.md b/docs/projects/index.md
index 568e2992..4d1adfd3 100644
--- a/docs/projects/index.md
+++ b/docs/projects/index.md
@@ -182,5 +182,5 @@ Review the [CoST IDS mapping](https://standard.open-contracting.org/infrastructu
 ```{admonition} Are you ready to start using OC4IDS?
 :class: Tip
 
-Complete the [OC4IDS scoping template](https://www.open-contracting.org/resources/oc4ids-scoping-template/) and share it with the [OC4IDS helpdesk](mailto:data@open-contracting.org).
+Complete the [OC4IDS scoping template](https://www.open-contracting.org/resources/oc4ids-scoping-template/) and share it with the [OC4IDS Helpdesk](../../support).
 ```