For the established (legacy) Volunteer Management portal. These steps differ from the newer Volunteer Management interface. Staff access is determined by their assigned administrator role(s). Administrator roles have fixed capabilities; the configurable volunteer roles described here are separate from staff administrator roles.
The legacy VMS test flow sends a [Test] message to the selected volunteer's email when present, otherwise the acting user's email. It can therefore differ from the address an administrator expects when working as a volunteer. The test merge uses sample constituent values; it is not a copy sent to the entire selected audience. A success notice is not proof of inbox delivery. For a missing test, inspect the expected address and message delivery record/error before assuming a platform-wide outage or repeatedly sending the real outreach.
Why does my volunteer email preview or test still say Taylor?
In the legacy Volunteer Management portal, the Email Preview and Send Test to Me use sample constituent values. Names such as Taylor or Taylor Jones are dummy preview data; selecting a different recipient does not turn this test into a preview of that person’s record.
Open the volunteer’s Email screen, select the template and review the greeting token. If the greeting contains the correct merge token, seeing Taylor in the preview or test is expected. Actual sends substitute the selected constituents’ data. If Taylor was typed as ordinary text instead of inserted as a token, replace that text with the appropriate token in My Templates and select the corrected template.
Do not change constituent names, shared email addresses, or imported records solely because the test uses a sample name. This legacy volunteer test is different from GC Outreach’s option to test using a constituent’s details. Send Test to Me does not send the message to the selected constituent audience.
Comments
0 comments
Please sign in to leave a comment.