Issue a prepared batch in one action
Review the recipient batch, publish once, and let Verifycate issue and email every certificate with the credit cost shown before it runs.
Sending certificates one at a time does not survive a real event. A workshop may have 80 attendees; a college fest may have 5,000 participants across 60 events. The bottleneck is not the design, it is the repetition.
A prepared recipient batch can be issued in one action.
The flow
Import or add the recipients, review the list, then publish the certificate. The confirmation shows how many recipients will be issued and what the batch costs in credits. Publishing issues the certificates and sends the delivery emails; recipients who are not ready stay in the list.
Open the certificate, go to Recipients, review the prepared rows, and choose Publish.
What it protects
The confirmation is there because issuing is the point where credits are spent and emails become visible to recipients. It shows the count before it commits, and it states the outcome in the same shape for issue, reissue, remind, and expire actions. If the balance runs out, the batch stops rather than half-finishing; recipients stay pending until credits are added.
Where it fits
A training provider can issue a cohort after the final session. A fest can issue participation certificates after the closing ceremony. A conference can issue speaker, volunteer, and attendee certificates as separate batches with different designs.
One issued certificate spends one credit. Importing and reviewing do not.
Related