Guide
Issuing from a list.
One template, one file, one row per recipient. Batches are paced to protect the WhatsApp number, so this is built for tens of recipients per run, not thousands.
Prepare the file
Upload a CSV, .xlsx, or .xls file with a header row. Columns can be in any order.
- Required: a
namecolumn and aphonecolumn. Headers containing “recipient”, “mobile”, or “whatsapp” are also recognised. - Optional: any other column becomes a template field. Use the same keys the template expects, such as
course_name. - Use the full number with country code, for example 919876543210. A ten-digit Indian number gets +91 added.
- Rows with fewer than eight digits are skipped. Commas inside values are not supported in CSV files.
The upload screen shows a preview of the first 20 rows before anything is issued. A sample CSV is available there too.
Run the batch
Choose one template, upload the file, and confirm. Every row becomes a separate certificate with its own ID and public verification link. Rows with a phone number also queue a WhatsApp message.
- The certificate records are created first, one at a time.
- WhatsApp messages are spaced 5 to 14 seconds apart, in a shuffled order.
- The screen reports how many records were created and how many failed.
No live progress, no retry
Practical limits
- Keep a run under roughly 80 recipients so the request finishes before it times out.
- The pacing protects the sending number from being flagged. It is not configurable from the app.
- Failed rows are counted, not individually listed. Re-upload the failed rows in a new file if you need to retry.
- Batch history shows status and counts. It does not show live progress while the run is happening.
After the run
Open Certificates to search the issued records, download PDFs, or resend a WhatsApp message. Public verification works immediately for every created certificate, whether or not its message was delivered.