Email delivery with KIDUART
Email is where longer school communication belongs: circulars, fee receipts, report card links, staff notices and account verification. KIDUART sends through your provider plain SMTP or a delivery service like SendGrid, Amazon SES or Mailgun so mail arrives from your school domain and lands in inboxes rather than spam.
What you get
- Mail sent from your school domain, not a generic address
- Fee receipts and circulars delivered as records parents can keep
- Account verification and password reset mail handled reliably
- Choice of SMTP, SendGrid, Amazon SES or Mailgun
- Provider event webhooks recorded so bounces are visible
The connection, hop by hop
How Email delivery actually works here
No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.
Provider chosen
Start with your existing SMTP mailbox, or move to SendGrid, Amazon SES or Mailgun as volume grows.
Domain authenticated
SPF and DKIM records are published once so mail sent on your behalf is trusted by inbox providers.
Mail queued and sent
Circulars, receipts and account mail are queued, so a large send never blocks the person who triggered it.
Events recorded
Delivery, bounce and complaint webhooks are stored so a wrong address is corrected rather than repeated.
Keys, data and the bill
Who holds the credentials
Your SMTP or provider API credentials and your own from-address on your school domain.
Where the data sits
KIDUART stores what was sent, to whom, and the delivery outcome.
Who gets billed
Your provider bills your account. Plain SMTP on an existing mailbox costs nothing extra to start.
Where it lands in the product
The modules this integration writes into
An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.
Setup, step by step
Connecting Email delivery
Pick the provider your school already uses, or start with SMTP
Add the sending credentials and the from-address for your domain
Publish the SPF and DKIM records your provider asks for
Send a test circular to a staff mailbox
Enable the events that should generate email
What you need on your side
- A school email domain you control
- Provider credentials, or SMTP details from your IT team
- DNS access to add SPF and DKIM records
Questions schools ask
Email delivery, answered plainly
Do we have to buy an email service?
No. Plain SMTP from your existing school mailbox works for lower volumes. A delivery service becomes worthwhile once you are sending circulars to hundreds of parents at once.
Why do SPF and DKIM matter?
Without them, mail sent on your behalf is far more likely to land in spam. They are a one-time DNS change that protects every future circular.
Also in messaging and notifications
Related integrations
WhatsApp Business
Reach parents on the channel they actually read, using approved WhatsApp Business templates from the school's own number.
SMS notifications
Send attendance alerts, fee reminders, OTPs and urgent notices as SMS the one channel every parent can receive.
Twilio
Use Twilio as your SMS gateway, including messaging services and delivery status callbacks.
See Email delivery in a live demo
We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.
30-minute walkthrough
Booked around your school hours
Run on your own data
Your fee heads, classes and staff roles
No card, no lock-in
Nothing is charged to see the product