A certificate support request should leave the next person with a clear question, the right credential reference and a named owner. For training teams, the useful handoff is more specific than \u201cplease fix this certificate.\u201d It explains what the recipient reported, what has been checked and which decision is still needed.<\/p>\n
This guide provides suggested intake and reply templates for your existing support system. They are not a built-in Sertifier ticket workflow, an approval to change an award or a promise of response time.<\/p>\n
Sertifier\u2019s recipient contact guide<\/a> directs questions about missing credentials, incorrect names, changed details and email addresses to the issuing organization. It also states that Sertifier cannot edit or delete credentials on the organization\u2019s behalf. On the credential viewing page, the Contact icon next to the issuer name leads to an email contact route.<\/p>\n Before a cohort receives its credentials, have the responsible team check that the published contact route reaches a monitored destination. Name a primary owner and a backup in your internal process. If a recipient has no credential link yet, give them a contact route in your course or event materials rather than assuming they can use the credential page.<\/p>\n Copy these fields into an approved private ticket or form. Keep unknown values marked unknown; do not ask a recipient to invent a credential number they have never received.<\/p>\n Collect only what the case needs through your approved private channel. Do not request passwords or place a participant roster, identity documents or private correspondence on a public credential page. If a screenshot helps explain an error, ask for the relevant area with unrelated personal information removed.<\/p>\n An intake owner does not have to perform every correction. They do need to make the next handoff actionable:<\/p>\nUse a short certificate support intake template<\/h2>\n
\n
Route the question before attempting a fix<\/h2>\n
\n