Contact form

Comprehensive documentation for the KilatKoding contact form, including Resend dependencies, sender setup, and public-form verification.

The contact form is the public communication path between visitors and your team. It is simple, but important if the product wants to accept questions, partnership inquiries, or leads from the website.

What this feature includes

• /contact
• POST /api/contact
• email sending through Resend

Related routes and endpoints

Route or endpoint	Type	Purpose
/contact	Public page	Contact form for visitors
POST /api/contact	API mutation	Sends the message to the target inbox

Main dependencies

Item	Required?	Notes
NEXT_PUBLIC_ENABLE_CONTACT=true	Yes	Enables the contact form
RESEND_API_KEY	Yes	Required to actually send email
EMAIL_FROM	Strongly recommended	Public sender email
CONTACT_EMAIL	Optional	Target inbox for contact submissions

What teams usually customize

• page copy,
• placeholders and labels,
• destination inbox,
• subject or message formatting,
• contact CTA placement on the landing page.

When this feature is disabled

It is usually disabled when:

• you do not want to accept website inquiries,
• the team is not ready to receive incoming email,
• the main funnel should only go to waitlist or another CTA path.

When disabled, clean up:

• contact navigation,
• “contact us” CTA blocks,
• support copy that still points to the form.

Verification checklist

1. /contact renders correctly.
2. Form submission succeeds.
3. Email really arrives in the correct inbox.
4. The sender domain is verified in Resend.
5. Public CTA paths only expose contact when the feature is active.

If you also use onboarding or invoice emails, continue to Email and communication.