Skip to main content
General

SMTP Setup for System Email

Written By Anand Raj

Last updated 3 months ago

SMTP setup lets the Agency send all system emails — notifications, OTP login codes, verifications and other transactional messages — from its own domain instead of a default Kickcall sender.

Using your own SMTP improves deliverability and trust because emails arrive from your brand.

Where to get SMTP credentials

You can use any email service that provides SMTP — for example:

  • Mailgun

  • AWS SES

  • ZeptoMail

  • SendGrid, Postmark, Brevo, etc.

Create an SMTP user / API key in your provider, verify your sending domain, and copy the credentials they give you.

Fields to fill

  • SMTP Username — the username or API key from your email provider.

  • SMTP Password — the password or secret paired with the username.

  • SMTP Address — host of your provider, e.g. smtp.zeptomail.in, smtp.mailgun.org.

  • SMTP Domain — your verified sending domain, e.g. kickcall.ai.

  • SMTP Port — usually 587 (TLS) or 465 (SSL).

  • SMTP From Email — the address recipients see, e.g. support@kickcall.ai.

  • SMTP From Name — the sender name shown in inboxes, e.g. Support Kickcall.

Click Configure to save. Once saved, all platform emails will go out through this SMTP.

Frequently Asked Questions

All system-generated emails — login OTPs, user invitation notifications, onboarding emails, billing notifications and any other transactional communications.

Emails will fail to send. Re-check the username, password, host and port from your provider's dashboard and update the configuration.

Yes. Most providers require SPF, DKIM and sometimes DMARC records on your domain so emails are not marked as spam. Follow your provider's domain verification steps before going live.

Yes. You can update the SMTP credentials any time from this screen — the new settings apply to all emails sent after the update.

More in General:

Was this helpful?

Still need help? Ask the team