KorpKit sends important emails such as signup verification, tenant notifications, order updates, invoice notifications, support messages, and client portal messages.
If email sender setup is wrong, tenants or clients may not receive important notifications. That can break signup, billing, order workflow, or client communication.
A proper sender setup helps emails look professional and improves trust because the message appears to come from an expected sender.
The default email mode uses KorpKit-controlled sending so a tenant can start without configuring a custom sender immediately.
This is useful for free or early-stage tenants because it reduces setup steps. The tenant can sign up, verify email, and test the portal before advanced email configuration.
Default sending may show KorpKit-related sender identity depending on the platform setup and package rules.
Custom email sender setup lets a tenant send notifications from a business-branded sender. This is useful when the business wants clients to recognize the sender and trust portal messages.
Custom sender setup usually requires DNS verification. This proves that the tenant controls the sending domain and has permission to send mail from that domain.
Paid packages can unlock custom email controls depending on the KorpKit package model.
DNS records help email providers verify that a domain is allowed to send mail. Common records include verification records, DKIM-style records, SPF-style records, and other provider-specific records.
A DNS record has a type, name/host, and value/content. All three must match the instructions shown by the system.
Wrong DNS records can cause verification failure, spam placement, or email delivery issues.
Open email settings in kkx0101. Choose custom email if your package allows it. Enter the sender email address or domain information required by the system.
Copy the DNS records shown by KorpKit. Add them in the DNS provider where the domain is managed.
Wait for DNS propagation, then run verification. Once verified, test tenant emails and client notification emails before relying on the sender for live business use.
Test owner verification emails, order notification emails, invoice emails, payment-related emails, and any support or portal notification email the tenant depends on.
Check inbox and spam folders. If mail arrives in spam, review DNS records and sender reputation.
Make sure the sender name is clear. Clients should understand that the email belongs to the business or the portal they are using.
If emails do not arrive, first check whether the sending flow was triggered. Then check spam, DNS verification, sender configuration, and whether the recipient address is correct.
If verification fails, compare DNS type, name, and value carefully. Do not assume the DNS provider entered the name exactly as shown.
If a tenant changes domain or sender, verify the new sender before removing the old working configuration.
Use KorpKit default email to start quickly. Use custom email when the business wants a stronger branded sender.
Custom email needs correct DNS records and verification. Never guess DNS values.
After setup, test signup, order, invoice, and client notifications so you know emails are actually working.
Start free, set up your services, and give clients a cleaner way to order, pay, upload files, and track work.
