Intakes¶
An intake is an address that a form on your website, or another system, can send to. Every submission opens a card on the board you choose, and can find or create the person as a contact and fill the board's fields. A lead from your website arrives as a card somebody works, instead of an email somebody has to copy.
flowchart LR
A[A visitor sends the form on your website] --> B{Doubtful?}
B -- No --> C{Open card from an intake for this person?}
C -- No --> D[New card in the intake's column]
C -- Yes --> E[A note on that card]
B -- Yes --> F[Spam review card, low priority]
S[Another system posts with the server secret] --> C
Who can set it up¶
Desk Center → Intakes (under Cases)
The screen belongs to the account's Desk Center administrators. A regular user does not see it and cannot read its settings, because an intake carries the secret a trusted server sends. The account must have Desk Center.
Creating an intake¶
New intake opens a dialog: "Where its leads land, and which websites may use it."
| Field | What it does |
|---|---|
| Name | How the intake is listed, and the first line of every card it opens. |
| Enabled | On by default. A disabled intake answers as if it did not exist. |
| Board | Where its cards are born. A prospect pipeline or an archived board is refused. |
| Column | The column the cards start in. First column is the board's first. |
| Priority | The cards' priority. Default gives them the normal priority, Medium. |
The card¶
| Field | What it does |
|---|---|
| Start from | A preset that fills Title and Contact for a common case (below). |
| Type | The card's type, from the account's types. No type leaves it empty. |
| Title | The card's title. Posted keys go in braces, like {company}. Empty means the lead title, New lead: {name} ({company}); an empty () is dropped, so a lead with no company is New lead: Sophie Turner. Up to 200 characters. |
| Contact | What happens to the person who sent it (below). |
| Preset | Contact | Title |
|---|---|---|
| Lead form | Find or create the person, new people as leads | New lead: {name} ({company}) |
| Onboarding | Find or create the person, new people as contacts | Onboard {company} |
| Task from another system | No contact (a task or an alert) | {title} |
Contact has three choices:
- Find or create the person, new people as leads — the person is looked up by email first, then phone. Somebody new is saved as a lead. A name and an email or phone are required.
- Find or create the person, new people as contacts — the same, but somebody new is saved as a regular contact.
- No contact (a task or an alert) — no person is involved. No name or email is asked for, and the same sender twice is two cards.
Filling the board's fields¶
When the board has fields, the dialog lists them under "Fill the board's fields from posted keys (leave empty to skip)". Type, next to a field, the name of the key the form or system sends for it. The suggestion shown is the field's name in lower case with underscores.
- A field the board requires must be mapped, or the intake cannot be saved: "that board requires …; map a posted key to each, or pick another board".
- A submission that leaves out a mapped required value is refused with the name of the key, and nothing is created.
- Values are read as the field's type: a number, a date (
2026-12-01), yes/no, or one of a select's options. - Keys the intake uses itself (
name,email,phone,company,note, …) cannot fill a field, and a key can be mapped only once. - Anything else the form sends that is not mapped is still written on the card, so nothing sent is lost.
Spam, tags and websites¶
| Field | What it does |
|---|---|
| Spam review column | Where doubtful submissions go. Same column, low priority keeps them in the intake's column at low priority. |
| Tags for the contact | Tags added to the person, separated by commas. |
| Websites allowed to post from a visitor's browser (one per line) | The websites whose pages may use the form, written like https://example.com. Empty means no browser may post: only a trusted server with the secret. |
| Per hour / Per day (pauses at the cap) | Submission limits. Empty means 60 an hour and 500 a day. |
| Paused | Set when the daily limit is reached; untick it to take leads again. |
| Ask for a captcha | Cloudflare Turnstile, off by default. Needs that website's Site key and Secret key. |
The list of websites is not a spam filter
It stops other websites using your form from their visitors' browsers. It does not stop spam: a bot can claim to be any website. Spam is handled by the form token, the rate limits and the review column (below).
Save creates the intake and gives it its address. Editing it later shows the Server secret too.
Putting it on your website¶
Each intake in the list shows its address and two buttons:
- Copy form copies a ready-made HTML form (name, work email, phone, company, "How can we help?" and Send) together with the script that sends it. Paste both into your page and style the form like the rest of your site. After sending, the visitor sees "Thanks, we will be in touch."
- Copy address copies the address alone, for a developer or another system:
https://<your portal domain>/desk/api/public/v1/intake/<intake id>
The script also sends the page the visitor wrote from and the utm_ tags they arrived with, and both appear on the card.
Another system posting to it¶
A system you trust — a signup flow, a CRM, an alert — posts to the same address with the header X-Intake-Secret: <server secret>, as JSON or as form fields. Keep the secret on that server, never in a web page. A trusted sender:
- skips the form token, the per-address limit, the content checks and the captcha;
- may also set the card's
title,descriptionandpriority.
What a card carries¶
A submission opens a card in the intake's column, with:
- the title from the template;
- a description listing the intake, name, email, phone, company, the page it came from and the UTM tags, then the visitor's own message;
- the contact, found or created, with the intake's tags;
- the mapped fields filled in.
The same person again adds a note, "Submitted again through
Spam protection¶
A submission that looks doubtful still arrives, so a real lead is never lost: it becomes a card titled "Spam review: …", at low priority, in the Spam review column, with the reason on the card. A person decides. These look doubtful:
- an email that does not parse, a throwaway email service, or a domain that receives no email;
- a phone number shorter than 7 or longer than 15 digits;
- more than one link in the message;
- the phrases typical of form spam (SEO services, backlinks, crypto, casino, …).
Sending is also limited:
| Limit | What happens |
|---|---|
| 10 a minute from the same address | Refused for that address. |
| Per hour (60 by default) | Refused until the hour passes. |
| Per day (500 by default) | The intake pauses. The list shows "(paused: daily cap of … reached on …)", and nothing is taken until an administrator opens it and unticks Paused. |
A form sent within 3 seconds of the page loading, or more than 2 hours after, is refused: a person takes longer, and a stale page is reloaded. A hidden field that only bots fill is accepted and silently dropped.
New address, or deleting it¶
- New address (the round arrow) — "the old one stops working" at once, and the server secret is replaced too. Use it when an address has leaked or is being abused, then paste the new form or give the new secret.
- Delete (the bin) — the address stops working. Cards it already opened stay.
Neither asks for confirmation.
What it does not do¶
- It does not decide which leads are real. A doubtful one arrives as a Spam review card, and a person decides.
- It does not write to the sender. The visitor sees the thank-you line on the page and nothing else, not even which check a refused submission failed; any reply is the team's.
- It does not create prospects. A prospect pipeline cannot be an intake's board.
See it in a video¶
Admins: Desk Center › Intakes shows an intake created for a website, a visitor sending the form, and the card on the board.