3 ways in
Gmail, Microsoft 365 or any SMTP
Failover
to the next relay when one hits its limit
Paced
to your provider's quota, not ours
Per recipient
sent, bounced or retried, exportable
Your own sender
OAuth to Gmail or Microsoft 365, or plain SMTP. Recipients see your name and address — deliverability and trust follow.
Saved email layouts
Branded, bilingual email templates with the certificate attached and the verify and LinkedIn buttons built in.
Retries and failover
Transient failures retry on their own; if a relay hits its limits, sending fails over to the next one instead of stalling the batch.
Rate-limit aware
The platform paces sending to respect provider quotas — a 5,000-recipient batch does not get your mailbox flagged.
Per-recipient outcomes
Sent, bounced, failed-and-retried — visible per recipient, exportable per batch.
English and Arabic presets
Ready-made message presets in both languages, editable and saveable as your own.
How it runs
- 1
Connect a mailbox
Gmail, Outlook or SMTP — or use the platform sender.
- 2
Pick or design the email
Saved layouts, bilingual presets, your branding.
- 3
Send with confidence
Paced, retried, tracked, and attributable to you.
Who runs this every week
What teams ask before they start
What if I do not want to connect my own mailbox?
You can send from the platform sender and start immediately. Connecting Gmail, Microsoft 365 or an SMTP server is the step that makes certificates arrive from your name and address, which is what most teams want once they see the difference in replies and trust.
What does the recipient actually receive?
An email from your sender with your saved layout, the certificate attached as a PDF, and buttons to open the public verification page and add the credential to LinkedIn. The message can be written once in Arabic and English, or in one language only.
Will a large batch get my Gmail or Outlook flagged?
Sending is paced to the provider's published limits and spread over time rather than fired at once. If a relay does reach its quota, the queue fails over to the next relay in your list instead of stalling, and the batch continues from where it was.
Can I see who did not get theirs, and why?
Yes. Every recipient carries an outcome: sent, delivered, bounced or failed-and-retried, with the provider's reason where it gives one. The batch report exports the whole list, so a bounced address is a fix-and-resend, not a mystery.
The rest of the platform
Your first certificates are minutes away.
Free to start — design a template, send yourself a test, and see the verification page live.