Answers before
you spend a credit.
Provider choice, bulk planning, failure handling, guarantees, exports, API automation, and responsible result handoff—explained without hiding the boundaries.
Start creating →Failed items consume zero credits. If credits were reserved while processing, they return to the workspace balance automatically.
Understand the product before creating a task.
These answers explain what MailMaker does, how orders are tracked, and what information should be reviewed before submission.
What is MailMaker?+
MailMaker is a prepaid dashboard and API for requesting email-account creation tasks across Gmail, Yahoo, Outlook, Proton, and iCloud. Every task keeps its provider, requested quantity, estimated credits, status, successful count, failed count, and result together.
Do I need a subscription?+
No. MailMaker uses prepaid credits rather than a monthly subscription. Credits remain in the workspace until they are used for successful account results.
Can I create one account before running a bulk task?+
Yes. Starting with a small representative request is the recommended way to confirm the provider, result format, receiving workflow, and credit behavior before increasing quantity.
Which providers are currently available?+
MailMaker supports Gmail, Yahoo, Outlook, Proton, and iCloud. Each provider has its own credit rate and dedicated direct, bulk, and API-oriented workflow pages.
What happens after I submit an order?+
The request receives a task ID and moves through observable states such as queued, processing, completed, partial, or failed. The final task separates successful and failed results so the output and credit charge can be reconciled.
Pay for successful results, not failed attempts.
The guarantee is intentionally simple enough to verify from the task and credit ledger.
What is the MailMaker credit-back guarantee?+
Every account reported as failed by a MailMaker task is guaranteed to consume zero credits. If credits were reserved while that item processed, they return to the workspace balance automatically.
How is a partially completed task charged?+
A partial task is charged only for its successful accounts. Failed items do not consume credits, and any credits reserved for those failed items return automatically.
Does the guarantee mean every requested account will succeed?+
No. The guarantee protects your MailMaker credits when creation fails; it is not a promise that every request will complete successfully or that a third-party provider will keep an account active forever.
How many credits does each provider use?+
Gmail and Yahoo use one credit per successful account, Outlook and Proton use two, and iCloud uses three. The estimated total is displayed before submission.
Do returned credits expire?+
Returned credits go back to the same workspace balance and follow the same no-subscription credit model. They remain available for a later approved task.
What should I do if task counts and credit movement do not match?+
Do not submit a duplicate replacement order. Keep the original task ID, stop downstream release, and contact support so the task result and ledger can be reviewed together.
Choose a provider because the workflow needs it.
Provider names are not interchangeable. The right choice follows the required mailbox coverage, downstream product, budget, and ownership model.
When should I choose Gmail?+
Choose Gmail when the product, QA plan, or approved workflow specifically needs a Google-hosted inbox. The Gmail task does not include Google Workspace domain or seat administration.
When should I choose Yahoo?+
Choose Yahoo when you need Yahoo Mail delivery, rendering, compatibility, or provider-diversity coverage. Keep Yahoo outcomes separate so a mixed-provider aggregate does not hide a Yahoo-specific issue.
Does Outlook creation include Microsoft 365 tenants or licenses?+
No. MailMaker's Outlook workflow is focused on Microsoft-hosted consumer email-account tasks. It does not provision Microsoft 365 seats, Azure tenants, Entra ID users, or company directories.
What is different about a Proton workflow?+
A Proton task should include a stricter result-handling plan. Choosing a privacy-oriented provider does not automatically protect exported credentials, so access control, logging exclusions, and deletion ownership still matter.
Does iCloud creation include managed Apple IDs?+
No. The iCloud workflow is for email-account tasks, not Apple Business Manager, device enrollment, or organization-managed Apple identity.
Can multiple providers share one credit balance?+
Yes. The workspace balance is shared, while every task preserves its own provider, rate, requested quantity, successful count, failed count, and actual credit use.
Scale with batches that remain explainable.
Bulk creation is useful when each batch has a clear purpose, owner, budget, and result destination.
How should I choose the first bulk quantity?+
Start with the smallest batch that still uses the real provider settings, export format, owner, and downstream destination. Increase volume only after the first task is reconciled and accepted.
Should different clients or environments share one task?+
No. Separate clients, releases, and environments so a configuration change, failure pattern, credential handoff, or deletion decision remains isolated and auditable.
Which result counts should I review?+
Review requested, successful, and failed quantities together with estimated credits, actual credits used, credits returned, processing time, and any replacement quantity.
How should I retry a partial batch?+
Preserve the successful output, investigate the failure category, and create a replacement only for the approved unresolved quantity. Do not repeat the full original request.
Which export formats are available?+
MailMaker's workflow supports structured result handoff through JSON, CSV, and TXT options. Choose the format your approved receiving system can validate and store securely.
Automate the task lifecycle without hiding decisions.
The API should repeat an approved operating model, with idempotency, bounded status polling, limits, and credential-safe logging.
Can every provider be used through the API?+
Yes. Gmail, Yahoo, Outlook, Proton, and iCloud use the same task-oriented API model while retaining their provider-specific rate and operational scope.
Why should task creation use an idempotency key?+
An idempotency key lets the client recover the same logical request after a network timeout without intentionally creating a second order and spending credits twice.
How does an integration know when a task is complete?+
Store the task ID returned at creation and retrieve that task at a bounded interval. Stop polling when it reaches completed, partial, or failed, then reconcile requested, successful, failed, and credit values before releasing results.
What should application logs contain?+
Logs can contain task IDs, provider, state, counts, duration, correlation IDs, and error categories. Raw passwords, recovery data, and exported credentials should stay out of normal logs.
Which limits should an automated creator enforce?+
Use provider allowlists, maximum quantity, maximum credit cost, concurrency limits, scoped API keys, bounded retries, and a manual stop or escalation path.
Know what MailMaker guarantees—and what remains yours.
Transparent boundaries prevent a successful technical task from being mistaken for permission, permanent provider access, or broader identity administration.
Who is responsible for authorization and provider rules?+
The customer is responsible for having an authorized purpose, following applicable provider rules, controlling access to results, and removing data when it is no longer needed.
Does MailMaker guarantee permanent access to third-party accounts?+
No. MailMaker guarantees the credit treatment of the creation result. Ongoing provider availability, future account status, and customer usage remain outside that credit-back guarantee.
Does an email-account task include enterprise identity administration?+
No. Email-account creation should not be interpreted as Microsoft 365 tenant management, Google Workspace administration, Apple Business Manager, device enrollment, or organization-directory provisioning.
How should credentials be handed off?+
Choose a named owner and an access-controlled destination before submission. Keep raw credentials out of tickets, analytics, normal logs, and broadly shared folders.