Where to begin

A short checklist that walks you through the five things every new MailCamp account needs before sending its first campaign.

A short checklist that walks you through the five things every new MailCamp account needs before sending its first campaign.

The get-started panel tracks your progress toward your first send. Each item links to the screen where you complete it; the rocket card on the left always shows the next step.

The five steps

  1. Complete the company survey — this collects the legal details and processing agreement we need before mailing on your behalf.
  2. Add a sending email address and verify it. You cannot send a campaign without at least one verified address.
  3. Create your first mailing list — the container that holds the contacts you will send to.
  4. Add or import contacts so the list has people in it.
  5. Design your first campaign and send it to the list.
📘

Always know what is next

Click the rocket-icon card on the left to jump straight to the next unfinished step — no need to remember where you were.

👍

When all five are done

The widget collapses to a confirmation message and the rest of the dashboard takes over. From here on you live in Campaigns, Contacts, and Statistics.

Can I hide the get-started widget?

Once all five steps are done it collapses on its own to a confirmation message. There is no manual dismiss — that way you cannot lose track of unfinished setup work before your first send.

Do I have to complete the steps in order?

No — each step has a direct link and can be completed in any order. The rocket-icon card always points at whichever step you have not done yet.

What happens after I finish all five steps?

The widget collapses to a confirmation message. From there you mostly live in Campaigns, Contacts, and Statistics — the dashboard becomes your performance overview rather than a checklist.

Why does the "company survey" step matter?

It collects the legal details and signed processing agreement we need before mailing on your behalf. Skipping it blocks the first send — there is no work-around.

See also


Did this page help you?