Handles whatever comes in. Gets sharper every time.
Connect any intake source — website forms, inbound email, or API. Latch prepares each submission for your team to review, handles the follow-through once you approve, and learns from every decision to improve the next one.
3 new cases
We'd like to book a demo for our team of 40.
sarah@acmecorp.com
Acme Corp, SaaS, ~40 seats. Enterprise fit.
I've been charged twice this month and nobody is responding.
marcus@example.com
Billing dispute. Third occurrence — prior tickets unresolved.
Found what looks like an exposed API key in your JS bundle.
researcher@bugcrowd.io
Potential credential exposure. Flagged critical — routing away from general queue.
Most forms end up in an inbox
Someone reads it. Forwards it. Asks a question in Slack. Eventually someone does something — or doesn't. There is no record of what happened or why.
Each submission gets its own case
Who sent it, what they asked for, what your team decided, and what happened next are all in one place. Website form or inbound email — same queue, same workflow.
Your team stays in control. Latch does the prep work.
Every submission goes into your Latch queue. Latch reads it and prepares a summary for your team. Your team reviews it and approves what should happen. Then Latch handles the follow-through.
Latch reads it
Latch works through each submission — what kind of request it is, whether anything is missing, what the likely next step looks like. Suggestions improve automatically as Latch learns from your team's past decisions.
Your team reviews it
The submission, the context Latch prepared, and a suggested next step are all in one place. Your team approves or adjusts before anything happens. Every decision stays with your team — always.
Latch handles the rest
Once approved, Latch runs the action and records everything. Each outcome feeds back into Latch — so the next similar request gets an even sharper suggestion.
Two channels. One queue.
Submissions arrive from your website or from inbound email. Latch puts them in the same case queue so your team reviews everything in one place.
Connect your website form
Point your existing form at Latch instead of an email address. Works with plain HTML, React, Next.js, Astro, Webflow, and Framer — and is compatible with existing EmailJS setups.
View install options →Forward an inbox to Latch
Forward an existing inbox — or set up a dedicated inbound address — and emails arrive as cases in the same queue. Useful for support@, hello@, or any address that receives requests.
See email setup →Works for any kind of external request.
Not just contact forms. Latch handles the full range of inbound requests that need a review step before anything happens.
The message, sender, and a suggested owner
Notify Slack, send an acknowledgement
Company, role, and notes on the request
Create a CRM lead, notify sales
The issue, urgency, and similar past cases
Raise a support ticket, classify urgency
Deal size, region, and contact details
Create a CRM opportunity, route to the right rep
Order details, amount, and reason
Check payment system, process refund once approved
Submitted fields and attached documents
Route to reviewers, record the decision
Connected in a few minutes
Forward an inbox, point your existing form at Latch, or post directly to the API. No changes to your site design or field names — you only change where submissions go.
View install guide →Connect your existing setup.
Latch connects to the tools and patterns you already use. No need to rebuild your frontend or change how submissions arrive.
Already using EmailJS? Switch without changing your form HTML or field names. One function call.
Migration guide →Point your form's action attribute at your Latch endpoint. No JavaScript needed.
Install @latch/intake-sdk and call submitIntake() from your submit handler.
Use the intake SDK inside a client <script> block on any Astro page or component.
Paste the Latch snippet into your site's custom code footer and add a data-latch-form attribute to your form.
Forward an existing inbox or use a dedicated inbound address. Emails arrive as cases in the same queue as website submissions.
POST submissions directly to the Latch intake endpoint from any backend, script, or custom integration. No SDK required.
API reference →Native Typeform connector — responses flow directly into Latch cases without a webhook setup.
Native Tally connector — form responses become Latch cases automatically.
Additional site builders, form tools, and intake sources in the pipeline.
How it works in practice
Answers to the most common questions about website and email intake in Latch.
Does my website form need to change?
No. The form your site already has stays the same. You change where it sends submissions — to Latch instead of an email address or form backend. If you are using EmailJS, it is a one-line code change.
How does email intake work?
Forward an inbox — or configure a dedicated inbound address — to Latch. Emails arrive as cases in the same queue as website submissions. Your team reviews them in one place regardless of how they arrived.
What does Latch do before my team sees the submission?
Latch reads the submission, identifies what kind of request it is, flags anything missing or unusual, and prepares a suggested next step. Your team gets a clear view of the case, not a raw form dump or email thread.
Can my team reject or adjust what Latch suggests?
Yes. Latch prepares the summary and suggestion — your team decides. They can approve the suggestion, change it, add notes, or close the case entirely. Nothing happens without a human decision.
Does Latch get better over time?
Yes. Every time your team reviews a case — whether they approve the suggestion, adjust it, or choose something different — Latch learns from that decision. Future suggestions for similar cases improve automatically. The more your team uses Latch to make workflow decisions, the sharper the suggestions become. Your team is always in control; Latch just gets better at preparing the right options.
What actions can Latch take once my team approves?
Latch can send a Slack message, create a CRM lead or opportunity, raise a support ticket, send an acknowledgement to the submitter, trigger a refund, call an internal API, or update a back-office system. Available actions depend on which integrations are connected to your account.
Is everything recorded?
Yes. The original submission, what Latch prepared, who reviewed it, what was approved, and what happened are all kept on the case. If someone asks what happened to a request three weeks ago, the answer is already there.
Ready to try it?
Works with your existing forms and email setup. Takes a few minutes to connect.