Taskra reads your support email and writes replies in your name. The setup is a one-time DNS change — it sounds technical but the wizard at /email-setup walks you through it.
Two ways to receive email
Option A — Use a Taskra inbox address
Your customers email "support@inbox.yourstore.com". Taskra owns the inbox, replies fly through your domain so customers see your brand. Recommended for most stores.
Option B — Forward from your existing email
Keep using support@yourstore.com. Add a forwarding rule in Gmail/Outlook/Workspace to a Taskra inbound address. Slightly more setup but no DNS changes.
The DNS records you'll need
When you pick Option A, the wizard generates these records for you:
- MX record — points "inbox.yourstore.com" at Resend's inbound servers
- TXT record (DKIM) — proves we're allowed to send on your behalf
- Optional SPF/DMARC — improves deliverability if you don't have them yet
Adding the records — by registrar
- 1Namecheap: Domain List → Manage → Advanced DNS. Add each record with its Type, Host and Value as shown.
- 2Cloudflare: DNS → Records → Add record. Important: turn the orange proxy cloud OFF for MX records.
- 3GoDaddy: My Products → DNS → Add Record. Use "@" only if the host is the root.
- 4Google Domains / Squarespace: DNS → Custom Records → Add. Same fields.
DNS changes take 5 minutes to 24 hours to propagate. The wizard's "Check again" button polls until it sees your records — usually under 15 minutes.
Verifying it's working
Once the wizard's verify step turns green, send a test email from any external account (Gmail works) to your inbox address. It should appear in /inbox within 30 seconds with an AI draft attached.
Common issues
- "Records not detected yet" — wait 10 more minutes, then click Check again. Most registrars take longer than they admit.
- MX record looks right but no email arrives — double-check the priority is set to 10 (some registrars default to 0).
- Customers getting "this email is not from yourstore.com" warnings — add the SPF/DMARC records the wizard offers as optional.
If you already have email at a different provider on the root domain (e.g. Google Workspace at @yourstore.com), use the inbox subdomain ("inbox.yourstore.com") so the two systems don't collide. The wizard does this by default.