Skip to main content
Personalization tokens let your script address each participant by name. Write a token in your meeting script or welcome message and Waterr replaces it at the moment the session starts, using the identity provided by the embed prejoin form, the signed embed token, or the signed-in user.

​
Available tokens

The fastest way to insert one is to type @ in the Meeting Script editor and pick from the Variables group — the token is inserted as a chip. You can also type the token text directly; both syntaxes work interchangeably. Tokens are case-sensitive. Any unknown {something} is left in the text untouched — your script can safely include curly braces for other reasons.

​
Where you can use them

  • Meeting Script (the Instructions tab of your scenario) — personalizes the AI’s behavior, greetings, and questions.
  • Welcome Message — the very first line the AI says on the call.
  • Sub-agent scripts in Multi-Agent scenarios — each persona a caller hands off to keeps addressing the participant by name.

​
Example

If Ada Lovelace joins with [email protected], the AI sees:

​
Where the identity comes from

Depending on how the participant reaches the meeting, Waterr resolves tokens from a different source:

​
Fallbacks

When a token can’t be resolved — the visitor skipped the field, or the embed didn’t collect it — Waterr substitutes a neutral placeholder rather than leaving the raw {{USER_FIRST_NAME}} in the prompt:
  • Missing name -> there (so Hey {{USER_FIRST_NAME}}! reads Hey there!)
  • Missing email -> (not provided)
If your scenario depends on knowing who the participant is, turn on Ask visitor for name & email in the Embed share modal, or mint a signed embed token with the person_name / email claims populated. Otherwise plan for the fallbacks — write your script so Hey there! still reads naturally.