For the host whose audience wants proof
Some audiences expect proof they turned up — for an employer, a professional body, their own records. Here is what the page does with that expectation, and what it does not.
My Joyfullday does not generate certificates. There is no signed PDF produced at the end of your session, no automated award to attendees, no verification service behind the name on the page. If a certificate exists for your webinar, it exists because you made it, or because you pointed people at something that did.
What the product does have is the other half of that promise: the page can carry a link you supply, and the attendee list keeps a status for every name and exports as CSV or PDF. Put those two together and a host can run an honest certificate process. What you cannot do is advertise a proof-of-attendance feature the software does not have.
Four requests that come in before a session, and the plain response to each.
Usually hours logged against a topic. Your exported list with attended status is the record of who was there; the formal document, if one is needed, comes from the body itself or from you.
Often a name, a date and a duration is enough. The session page already states the date and the agenda durations, and a confirmation email carries the details they registered against.
That is a decision for you and your own tooling. If you issue badges, the page's certificate link is where people find them after the session.
Say on the page, in the description, exactly what someone gets: the recording, the workbook, and a signed certificate from the host if you issue one. Specific wording beats a vague promise of documentation.
If you already produce certificates — a document you fill in yourself, a form you send to attendees, a signing service you use for other training — the webinar page treats it like any other material. You paste its link into the resources area beside the replay and the slides, and the note you send to the attended segment points people at it.
Two details make that work smoothly. Put the certificate link in the follow-up message rather than only on the page, because it goes to the names who actually came; and write on the page, before the date, what people must do to qualify. An attendance expectation that appears after the session is a complaint waiting to happen.
If someone asks whether your page issues certificates, the honest sentence is short: the host does, and the page keeps the record. That answers the question without inventing a feature, and it keeps your expectations aligned with what you can actually deliver at eleven o'clock on the night.
For hosts who do not want the paperwork at all, there is an equally honest route: leave the certificate line out of the invitation and offer what you genuinely supply — the recording, the slides, the workbook, and a list of people you can confirm attended if an employer asks.
How it works
A name on a record, a document you sign, or nothing at all. Choose before the invitation is written, because the page needs to say it.
Put the sentence about certificates, and the attendance requirement, where people read it before registering rather than in a message afterwards.
After the session, statuses on the attendee list separate the people who came from those who registered and did not appear.
Take the CSV or PDF for your records and broadcast the certificate address to the attended segment. Keep that link on the page beside the replay and slides.
Questions
No. Nothing is generated, signed or awarded automatically. If your audience receives a certificate, it comes from you or from a service you already use, and your page simply carries the link attendees need to reach it.
You have the record rather than a service. The attendee list keeps attended, no-show and waitlisted statuses, which you mark from what happened in the session, and exports as CSV or PDF for exactly this kind of question later.
Yes, and precisely. Say whether a certificate is issued, by whom, and what attendance requirement applies. An expectation stated after the date reads as an apology; stated up front it just sounds like good planning.
The honest answer today is that we do not generate documents, and no date to promise. A link to a certificate you produce yourself is the supported route, and it covers most of what people actually need from this feature.
That they had no seat, and that a place at the next date is theirs if they want one. A waitlisted name should not be in the certificate run, so the follow-up message to that segment is worth writing separately.
Get Started
No generated certificates here — a host-supplied link and an attendee list with statuses. Written plainly on the page, that is more trustable than a feature nobody can verify.
