Transactional Email for Client Deployments: SMTP2GO Limits and Handover

Choose transactional email around the client's password resets, receipts and workflow notifications. Keep an adequate existing sender when it meets the volume, ownership and recovery requirements. Consider SMTP2GO when you need a separate sending service and can hand its operation to the client.

Before buying, count normal monthly sends and the busiest expected day. Include notification fan-out, repeated requests and your recovery allowance. A deployment with few users can still generate a burst. A password-reset email also has a useful lifetime: delivery after its link expires does not complete the job.

Check your email capacity and reporting window against the retained plan limits. Your inputs stay in your browser; the check does not test delivery.

Start with the existing sender or Free

If the application's current email service already supplies sufficient capacity, usable failure records and client-controlled access, adding another subscription may add work without solving a problem. Verify those conditions against that service's own documentation and your approved acceptance checks. This guide does not establish that SMTP2GO is cheaper or more reliable than your existing provider.

SMTP2GO's Free plan documentation lists 1,000 emails monthly, a 200-email daily cap and 5 days of reporting. The recurring free plan can suit a small deployment whose bursts and investigation window fit those limits. The documentation says daily excess is queued, while attempts beyond the monthly allowance are rejected rather than held until reset.

For time-sensitive notifications, model the daily queue as well as the monthly total. Without a verified sender domain, Free also has a 25-email hourly limit. Confirm that the operator will investigate failures while the records remain available. Low average volume alone is insufficient reason to select Free.

Pay for a requirement you can name

The plan differences guide lists 30 days of reporting for paid plans. Starter removes daily and hourly limits once the account is fully activated, while monthly allowance and overage still apply. Activation is a condition to verify before launch, not a result established by purchasing.

The dated USD record lists Starter's 10,000 emails per month at $15 monthly or $150 paid upfront annually. Excess email costs $1.20 per 1,000 emails. Professional's 100,000-email allowance costs $75 monthly or $750 upfront annually. Annual billing does not turn the monthly allowance into a pool for the whole year.

Choose paid capacity when the documented free caps cannot serve the workload, or when a longer investigation window is required. Separate the subscription from optional extras, taxes and your support fee. Confirm the selected volume tier, current checkout amount and account terms before committing. Review SMTP2GO limits and dated pricing alongside the vendor calculator; the stored price check remains October 3.

Give the client ownership of sending

Use a client-owned account, billing contact and sending domain. Agree who can approve DNS changes and restore access after the agency leaves. Record the SMTP or API secret's location in the client's secret manager, its consumer and rotation owner. Put references in the handover document, never the secret itself.

The Verified Senders guide requires sender verification and documents three CNAME records for domain setup. Use the exact account-provided values and have the client's DNS operator approve them. Preserve unrelated mail records. Sender verification is a setup condition, not a guarantee that every recipient will receive the message in their inbox.

Accept the failure path before launch

In an approved test environment, send to a mailbox the client controls. Save the application event ID, provider response and resulting activity event. SMTP2GO's Activity Report documentation distinguishes a processed message queued by its servers from a delivered event associated with recipient acceptance. Neither is proof of inbox placement or a completed password reset.

Exercise an invalid address and inspect the recorded reason. The bounce documentation says a final hard or soft bounce is not retried. Investigate the cause rather than repeatedly resending to a failed recipient. For a timeout with an uncertain outcome, reconcile provider activity before allowing a new application attempt; define your own duplicate-prevention procedure.

Ask the client operator to find a failed message, explain whether a resend is appropriate and locate the sending configuration. Hand over the selected plan, DNS record inventory, secret references, retention window and escalation contact. These are suggested checks, not results we have demonstrated.

Choose after the workload and handover fit

Stay with an adequate existing sender, or use Free when both caps and the reporting window fit. Shortlist paid SMTP2GO when a specific volume or reporting requirement justifies it and client ownership is resolved. Your acceptance evidence should precede a production switch.

Review SMTP2GO plans on the vendor site if you are ready to evaluate the account and billing conditions. A purchase does not establish delivery performance.