← All use cases

Payment reminders that know when to stop.

Your agent emails customers about failed payments and open invoices. Each reminder goes out once, follow-ups stop when the customer replies, and billing questions reach your team.

One reminder per invoice.

Agents retry. Give each reminder a dedupe key built from the invoice, and a second attempt is blocked with a reason instead of reaching the customer twice.

send_email · billing@yourco.com
send_email({ to: "ops@foldhaus.com",  template_id: "payment-failed", dedupe_key: "inv_1042:reminder-1",  payload: { invoice: "1042", amount: "249.00 EUR" } })→ { requestId: "req_51aa", status: "queued" } # the same call again→ { requestId: "req_51aa", status: "blocked",    reason: "duplicate", duplicate: true }
blocked · duplicate

Follow-ups stop on a reply.

Your agent schedules one follow-up. A reply from the customer cancels it, and so does a suppression or a person taking over the thread. When the invoice is paid, your payment webhook handler can cancel it.

schedule_followup · billing@yourco.com
schedule_followup({ contact_email: "ops@foldhaus.com",  thread_request_id: "req_51aa", delay_minutes: 4320,  cancel_on_reply: true })→ { followupId: "fu_2c41", status: "pending", scheduledAt: "..." } # invoice paidDELETE /v1/agent/followups/:id→ { cancelled: true }

Billing questions go to a person.

A reply about a charge is classified as billing, and the next-action check tells your agent to stop and ask a human. Refunds and disputes are handed over with a note.

next_best_action · billing@yourco.com
next_best_action({ contact_email: "ops@foldhaus.com" })→ { recommendation: "escalate",    reasoning: "Sensitive intent detected (billing). Requires      human review before any action." }
escalate · waiting on a human

Give your agent its own mailbox.

Start free

$ npx @molted/cli auth signup