If a Digital Reception form's token does not match the name shown in the form list, nothing is broken. The token is generated from the form's name the first time it is saved, and it stays that way for the life of the form even if you rename it afterwards.
Why the two differ
The token is the unique code used to reference the form across the platform. It is created once, from the form's original name, and never changes.
The form name is the display name. You can edit it whenever you like.
So a form created as "F-Test" and later renamed to "D-TEST" keeps the token f-test. Rename it five more times and the token is still f-test.
This is deliberate. If the token changed with the name, every campaign, page, or integration already pointing at the old token would break the moment someone edited the title.
Sending a form in a campaign
You do not need to know the token to send a form. Pick it from the list by name.
Go to Campaigns and open the campaign you want to edit.
Scroll to the Content section.
At the bottom of the content, click Digital Reception, then select Form.
Choose the form you want from the list.
What this does not do
Tokens cannot be renamed. A token is tied permanently to the form's first saved name. Renaming the form does not update it, and there is no way to edit it afterwards.
The platform does not flag the mismatch. There is no warning when a token and a form name have drifted apart, so if you are working with tokens directly, check which form a token belongs to rather than assuming from the name.
What to do next
If a token name matters to you, get the form's name right before you save it the first time. For forms that already exist, use the form list rather than the token to identify them.
Getting help
Open Talk to Us in the left menu of the platform, or email support@bookboost.io.