# Intake Forms
An intake form is how requests get into a [[Service Desk]]. Build the form, publish it, and anyone with the link can send you a request without an account.
> [!quote] Two ways in, one destination
> Use the hosted form when you want something you can link to or embed today. Use the API when you already have a form on your own site and just need somewhere for it to post. Both create the same task in the same desk.
## Building a form
A Service Desk has a **Forms** tab that Team Projects don't. Open it to create a form and edit it in the builder, with a live preview beside your changes so you can see the form as your submitters will.
The builder is organised into a few sections:
| Section | What you set |
|---------|--------------|
| **Form details** | The form's name and the introduction submitters see |
| **Questions** | Which standard and custom fields appear, their wording, order, and whether they are required |
| **Submission actions** | Labels, hidden field values, automatic assignees, and an optional internal comment |
| **Branding** | Your logo and whether to show it |
| **Appearance** | Light or dark theme, and an accent colour |
| **Spam protection** | Whether to require a captcha |
### Questions
Each form starts with standard questions for the request title, description, requester name, and email address. Request title and email are required. Attachments, Priority, and Due date are available as optional questions, alongside the [[Custom Fields|custom fields]] you define for the desk.
For every included question, you can:
- Drag it into the order requesters will see
- Replace its default label with wording that fits your audience
- Add help text with examples or guidance
- Mark it as required. The request title is required on every form
Priority offers Urgent, High, Normal, and Low. If it is optional and left blank, the new task uses Normal priority. A Due date answer becomes the task's native due date, so both fields are ready for sorting and triage as soon as the request arrives.
> [!tip] Ask for less than you think
> Every required question is a reason for someone to abandon the form. Ask for what you need to route the request, and get the rest in the follow-up conversation.
### Appearance and branding
Set a light or dark theme and an accent colour, and upload your logo. The hosted form uses all of it, so the page looks like it belongs to you rather than to Zaphiri.
> [!note] Save before you share
> While you have unsaved edits, the builder pins a reminder that the live form and the API are still serving the last saved version. Your drafts do not reach submitters until you save.
## The hosted form
Every form has a public link. Anyone can open it, fill it in and submit, with no Zaphiri account and no login. They see a confirmation with a reference code for the task that was created.
![[service-desk-intake-form.png]]
- **Share it directly** by sending or linking the URL
- **Embed it** in your own site or help centre
- **Pause it** by turning off **Accepting responses**, which closes the form without deleting it or losing anything already submitted
- **Rotate the link** if the URL gets scraped or shared somewhere you didn't intend, which retires the old one
## The API
If you already have a contact or support form on your own site, you can point it at the desk instead of rebuilding it. The form's endpoint accepts a JSON POST with answers for the standard and custom questions configured on that form.
- **A GET returns the form's definition**: its question labels, help text, required flags, types, options and branding. A custom front end can then render the right fields without hardcoding them
- **A successful POST returns the new task's reference**, which you can show your submitter
- **Validation errors come back as 400** with the problem named, so an unconfigured field or a missing required answer is easy to debug
- **No member or project data is exposed** through the public endpoint
> [!tip] Migrating an existing form
> If you already collect requests somewhere else, you can often keep the form and only change where it posts.
## Spam protection
A public form is a public target, so several protections run by default:
- **A honeypot field** silently discards automated submissions without creating a task
- **Rate limiting per IP address** stops a flood of submissions from one source
- **A size limit** on the request body
- **Captcha**, optionally, if the other measures aren't holding the line on their own
> [!warning] Turn captcha on if you're getting junk
> The default protections handle ordinary bot traffic. Captcha is there for when a form is being targeted specifically, and it's a toggle in the builder's Spam protection section.
## What happens on submission
You can set up actions that run whenever the form creates a task, so requests arrive already sorted:
- **Apply labels** to everything from this form
- **Preset custom field values** that the submitter doesn't see or set
- **Assign active Service Desk members** to every submitted task without sending an assignment notification
- **Post an internal comment**, optionally @mentioning someone so it reaches their [[Team Notifications|inbox]] immediately
> [!success] Routed before anyone reads it
> A form for bug reports can collect priority and due date, add a "bug" label, assign the triage team, and post an internal comment before anyone opens the request.
---
**Next:** See how requests get worked in [[Service Desk]].