Dynamic variables are placeholders you type into an email subject or body. Vome replaces each one with real information about the recipient and their shift at the moment the email sends, so one template can greet every person by name and quote their own details. The set of variables available to you depends on where in Vome you are writing.

A placeholder that Vome fills in automatically when an email or notification sends.
$first_name.$Shift_Title does nothing.{first_name} and not {{first_name}}.A variable only resolves when the email is about one single thing. An email about one shift can name that shift. A summary email covering ten shifts cannot, so it offers fewer variables. Each editor shows only the variables that work there, in its { } picker.

Shift notification policies (Schedule, Notification policies). The only place where variables merge in both the subject line and the body.
$first_name, $last_name, $shift_title, $shift_description, $opportunity_title, $category_title, $shift_date, $shift_start_time, $shift_end_time, $shift_location. $kiosk_pin also resolves here even though it is not in the picker.Saved email templates (Emails, Email templates). The base set. A template created inside a notification policy also carries the full shift set, and one created inside an achievement carries the achievement set.
$first_name, $last_name, $kiosk_pin.Emailing profiles (Emails, Send email). Variables merge in the body only, and the subject sends exactly as typed. Sent from a shift call-out, the shift variables resolve too.
$first_name, $last_name, $kiosk_pin.Approve, invite, assign composer.
$first_name, $last_name, $kiosk_pin, $opportunity_title, $role_title, $organization_name. Assigning a sequence adds $sequence_title. Assigning several opportunities at once, or deactivating in bulk, resolves nothing beyond the personal variables.Course automations.
$first_name, $last_name, $course_title, $chapter_title, $section_title, $score, $days_since_start, $expiry_date, $organization_name.Achievement notifications.
$first_name, $last_name, $full_name, $achievement_title, $achievement_description, $window_key.Sequence step automations.
$first_name, $last_name, $sequence_title, $days_pending, $organization_name.Form question automations. These resolve on the per-rule notification only. The merged summary sent to administrators covers several questions at once, so it does not personalize.
$first_name, $last_name, $kiosk_pin, $form_title, $question_title, $answer, $submitted_on, $organization_name.Resources, announcements, birthdays.
$first_name, $last_name, $kiosk_pin, plus $resource_title or $announcement_title and $organization_name where relevant.The email still sends, but the variable prints as literal text, so the recipient reads $shift_title. Some editors warn you first.
It is replaced with nothing. A shift with no description leaves a blank line, not an error.
It depends on the screen. Notification policy emails merge variables in both the subject and the body. The Send email screen merges the body only, and the subject sends exactly as typed.
Yes. In notification policy emails, dates and times render in each recipient's own time zone (with the zone shown) and in their chosen language.
It was used somewhere it is not available, or it was misspelled or capitalized. Check the { } picker in that specific editor, which lists only what works there.

Notification policies have a bulk assignment setting. Set to send one notification for the whole workflow, the variables take their values from the first shift only. Switch it to a separate notification per shift, or use generic wording.
Push and in-system notifications do not carry email formatting such as styling, links, and line breaks. If you need different styling for each, create two separate notifications.
$opportunity_title is the opportunity itself. $category_title is the category it is grouped under. For "Food Bank Greeter" in a reminder, use $opportunity_title.