Your contact form, answered.
A submission becomes an email thread in your agent's mailbox, from the address the visitor typed. Your agent replies to them there and hands off what needs a person.
One call from your form handler.
Your form's backend records the submission as an inbound message, with the visitor's address as the sender. Molted opens a thread for it in the mailbox, the same as if they had emailed.
POST /v1/agent/record-inbound{ "fromEmail": "sam@lumen.co", "toEmail": "hello@yourco.com", "subject": "Contact form: onboarding question", "bodyText": "Name: Sam\nCompany: Lumen\nHow do I set up the integration? I need help." }→ { "messageId": "msg_9e1f", "threadId": "thr_5d02", "isNewThread": true, "classificationJobId": "job_77c3" }Screened and labelled like email.
Anyone can type into a form, so a submission gets the same treatment as inbound mail: it is classified and screened for injection before your agent reads it. Your agent sees the label and the risk level with the message.
get_thread({ thread_id: "thr_5d02" })→ messages[0] { direction: "inbound", fromEmail: "sam@lumen.co", intent: "support", routingAction: "notify_owner" }→ envelopedMessages[0].agentGuidance { injectionRisk: "low", contentTrust: "untrusted" }The reply goes to the visitor.
Your agent replies in the thread and the answer lands in the visitor's inbox, from your address. Their reply comes back to the same thread, so the conversation carries on by email.
reply({ thread_id: "thr_5d02", body: "Hi Sam, here is the setup guide for the integration." })→ { requestId: "req_c9a4", status: "queued" }What needs a person goes to one.
A sales question, a partnership, a complaint: your agent hands the thread to your team with a note instead of guessing. The visitor keeps one thread with you either way.
handoff_thread · note · 409 thread_taken_over while a person has it
Give your agent its own mailbox.
We'll email you when signups reopen.