Skip to content

Private beta · email that starts from your product, sent from your inboxes

Docs

Setting up Momentloft

The parts that happen outside the app: your domain, your AI key, and how your product enrolls people.

1. Domain checklist

Production sending stays off for a domain until these pass. The sandbox works without them. Ideally send from a domain or subdomain that already receives replies from your customers.

  • SPF — one TXT record listing every service that sends as the domain. Build it.
  • DKIM — the signing key your mailbox provider gives you (Google Workspace and Microsoft 365 both generate one in their admin consoles), published as the TXT or CNAME record they specify.
  • DMARC — a TXT record at _dmarc.yourdomain. p=none with a report address is enough to start. Build it.
  • A working reply-to. Replies stop sequences, so the inbox has to receive mail.

2. Your AI provider key

Drafting runs on your own key, stored encrypted and used only for your sequences and reply drafts. Create a key with your provider, set a spending limit there, and paste it into the app during setup. You can rotate or remove it at any time.

3. How people get enrolled

Two equal ways in, and every contact records which one added it:

  • A list: upload a CSV or paste rows. Map the email column and any fields your sequence uses, and name the source so the reason is kept.
  • Your product: call the enroll API when a moment happens — a trial starts, a limit is hit. The event name becomes the provenance, like trial.started.

The full API reference, request signing and example payloads are shared with beta seats while the API settles. Join the beta or ask at support@momentloft.com.