diff --git a/src/pages/guide/node/validator-lifecycle.mdx b/src/pages/guide/node/validator-lifecycle.mdx
index 81d6b175..d9a476a1 100644
--- a/src/pages/guide/node/validator-lifecycle.mdx
+++ b/src/pages/guide/node/validator-lifecycle.mdx
@@ -27,7 +27,7 @@ The node will finish processing the current block before shutting down. Avoid us
 **You cannot reset a validator's data and continue with the same identity.** Doing so risks inconsistent voting, which can cause irrecoverable network safety failures.
 :::
 
-If you need to reset your validator's data, you must rotate to a new validator identity. This requires coordinating with the Tempo team to deactivate your old identity and register a new one. Don't hesitate to reach out — even with the Tempo team, this is a routine operation.
+If you need to reset your validator's data, you must rotate to a new validator identity. This requires coordinating with the Tempo team to deactivate your old identity and register a new one. Don't hesitate to [reach out](mailto:partners@tempo.xyz) — even with the Tempo team, this is a routine operation.
 
 :::info
 Self-service data resets are coming soon. Once available, you will be able to rotate to a new identity and reset your data without coordinating with the Tempo team. See [Rotate validator identity](#rotate-validator-identity).
diff --git a/src/pages/guide/node/validator-status.mdx b/src/pages/guide/node/validator-status.mdx
index 72ddb3fd..453d2010 100644
--- a/src/pages/guide/node/validator-status.mdx
+++ b/src/pages/guide/node/validator-status.mdx
@@ -127,6 +127,6 @@ curl -s localhost:8002/metrics | grep consensus_engine_dkg_manager_ceremony_fail
 
 If `how_often_dealer` or `how_often_player` is increasing, your node is actively participating in DKG ceremonies. After your validator has been added to the network, you should alert on these metrics, as they indicate that your validator is actively participating in the network.
 
-If your validator is not connected to other peers, but at least 3 epochs have passed, check that your node is properly configured — e.g. firewall settings are open to other peers. If you have reset your validator's state, your validator might have been blocked due to double-signing a block. In that case, please reach out to the Tempo team — even with the Tempo team, resolving this requires coordinating a new validator identity.
+If your validator is not connected to other peers, but at least 3 epochs have passed, check that your node is properly configured — e.g. firewall settings are open to other peers. If you have reset your validator's state, your validator might have been blocked due to double-signing a block. In that case, please [reach out to the Tempo team](mailto:partners@tempo.xyz) — even with the Tempo team, resolving this requires coordinating a new validator identity.