← GUIDES / Getting started

Get your store ready to send.

A merchant checklist for sender details, domain verification and a first test email, including what to check when DNS verification is pending.

In this guide

You can prepare and revise drafts while arranging your sending setup. Before a real email goes out, Fikamail needs verified sender details, an active subscription and sending enabled.

Most of the work is confirming your business details and adding the domain records shown in the app. If someone else manages your domain, send them those exact records.

Your preparation checklist
Tick these as a reading aid. They do not update your workspace or save between visits.

Choose a recognizable sender

Use a sending address on a domain your business controls. A personal address at a shared provider such as Gmail does not give you control of that provider’s DNS.

Check the sender name and reply-to address. Customers should recognize your store, and replies should reach a mailbox you monitor. Supply your complete real business postal address; Fikamail uses it in the email footer.

Changing the sending address resets verification, so settle on the address before completing the domain steps.

Add the records from your own workspace

In Settings → Email sending, open Connect sending domain, then choose Get DNS records. Fikamail provides the record types, names and values for your sender.

  • DKIM CNAME records support signatures that receiving mail servers can check.
  • The _fikamail TXT record proves domain control for your Fikamail workspace. Copy its value from the app.
  • DMARC lets receiving servers evaluate authentication against the visible sending domain and the domain’s policy. Fikamail checks for an existing policy when you verify.

Add the records at the provider that manages your domain’s DNS. This may differ from the company hosting your store or selling your domain. Use the values supplied for your workspace; another store’s records will not verify yours.

Keep an existing DMARC policy. The app only suggests a new record when it confirms one is missing. Do not replace an existing policy with a weaker one or add a second policy record to the same name.

For background on SPF, DKIM and DMARC, see Google’s email sender guidance. Use Fikamail’s displayed records for the actual setup rather than copying a generic example. Avoid replacing records used by your other email services.

If verification stays pending

Return to Fikamail and choose Check again after adding the records. DNS changes may take time to become visible.

Before editing them repeatedly, check:

  1. Are you updating the DNS provider used by the domain’s current nameservers?
  2. Does each record have the type shown in Fikamail?
  3. Did the provider append your domain to a name that already included it? Some DNS editors expect only the part before the domain.
  4. Do the values match the app exactly, without missing characters?
  5. Is the sending address still on the domain you just configured?

If the app reports a lookup error, retry when the lookup is available. An error is different from confirmation that a record is missing. If you need help, share the pending status and record names with whoever manages your DNS; they do not need your Fikamail password.

Check a real test email

Once the sender is verified and your plan is active, use the test-send action to send a draft to your own account address. Inspect it in the mailbox you actually use, including on a phone.

Check the subject, preview text, sender identity, reply destination, images, links and postal address. Look in the spam folder too. A received test helps verify this path, but one successful email does not establish inbox placement for your customer list.

Fikamail’s account test uses a test unsubscribe link that explains the test and does not change a subscriber’s consent. Customer emails have their own unsubscribe links and one-click unsubscribe headers.

Enable sending when the work is ready

Domain verification and enabling sending are separate. Complete the setup, review a test, then enable sending when you are ready to approve campaigns or activate flows. Enabling sending alone does not approve a draft.

Fikamail rechecks recipient eligibility and applies sending limits. Verification does not turn an old customer list into a subscribed audience or guarantee that every email will arrive in the inbox.

Before your first send, confirm:

  • Sender details and domain verification are complete.
  • Your subscription is active and sending is enabled.
  • The email and live destinations have been checked.
  • The audience or flow trigger fits the message.
  • Other email tools will not send overlapping messages unintentionally.

Use the campaign and flow approval checklist →