Letterbook Docs
Connect web forms
Send contact form and support form submissions into Letterbook.
Last updated June 25, 2026
What this guide covers#
Send website contact forms and support forms into Letterbook so form submissions create conversations in the inbox.
Use web forms when customers need a structured way to ask for help outside email. Forms are useful for collecting required fields, reducing back-and-forth, and attaching product context before the first reply.
Setup steps#
- Decide whether to use a hosted Letterbook form or your existing website form.
- Collect the customer email, name, subject, and message.
- Add structured fields for the support area, account ID, order ID, or product context.
- If using your own form, submit to your backend first.
- Have your backend create a Letterbook conversation with the API.
- Validate required fields and spam controls before calling Letterbook.
- Send a test submission and confirm it appears in the right inbox.
Hosted form versus API form#
| Option | Best for | Notes |
|---|---|---|
| Hosted Letterbook form | Fast setup and a standard support entry point | Use when you do not need deep product-specific fields |
| Existing form with API | Product-native support, custom fields, authenticated users, or app-specific context | Your backend should call Letterbook server-side |
Avoid forms that both create an API conversation and email the same message into a forwarded inbox. That usually creates duplicate tickets.
Recommended fields#
Start with:
- Customer email
- Customer name
- Subject
- Message
- Support category
- Account or workspace ID
- Order, subscription, or invoice ID when relevant
- Current URL or product area
- Attachment, screenshot, or error detail if supported
Keep the form short enough that customers will finish it. Add conditional fields only when they materially improve the first response.
Spam and validation#
Web forms need intake protection. Validate email addresses, require a meaningful message, and add spam controls appropriate for your traffic.
If a form is public, rate limit submissions and avoid letting untrusted users set privileged fields such as priority, assignee, or internal labels without server-side validation.