Nit: Token registration callout (#2194)

* Nit: Token registration callout

* nit

---------

Co-authored-by: aelmanaa <aelmanaa@gmail.com>

Author: thedriftofwords

src/content/ccip/concepts/cross-chain-tokens.mdx

@@ -92,8 +92,9 @@ Before enabling an ERC20-compatible token in CCIP, it's important to understand
   - `getCCIPAdmin()`: This function returns the token administrator's address and is recommended for new tokens, as it allows for abstraction of the CCIP Token Administrator role from other common roles, like `owner()`.
 
     <Aside type="note">
-      In the event that these functions are not available, registration can be performed by submitting a form
-      [here](https://chain.link/ccip-contact).
+      If these functions are not available, use [this contact
+      form](https://chain.link/ccip-contact?v=Tokens:%20Token%20admin%20registration) to request assistance with
+      registration.
     </Aside>
 
 - **Requirements for CCIP token transfers**: The token's smart contract must meet minimum requirements to integrate with CCIP.
@@ -256,7 +257,7 @@ If the token contract includes the necessary functions (`getCCIPAdmin()` or `own
 
 #### Non-Self-Service Registration Flow
 
-If the token contract does not have the necessary functions (`getCCIPAdmin()` or `owner()`), the token developer must manually initiate the registration by submitting a request [here](https://chain.link/ccip-contact).
+If the token contract does not have the necessary functions (`getCCIPAdmin()` or `owner()`), the token developer must manually initiate the registration by submitting a request [here](https://chain.link/ccip-contact?v=Tokens:%20Token%20admin%20registration).
 
 #### Sequence Diagram: Proposing the Administrator