Stage 11 of 12
Customer Support for an Email Service Provider
Support at an ESP is mostly account review, sender domain DNS, deliverability questions and abuse reports. This guide covers where support requests land in Octeth, what Octeth emails new accounts and what you add yourself, the help docs your customers need, and how to set response targets.
By Cem Hurturk, founder of Octeth Updated 6 min read
- Email support
- Help docs
- Written support commitments
On this page
Most requests at an ESP are about getting to the first send: an account waiting for review, a sender domain that does not verify, a campaign that lands in spam. Recipients and mailbox providers write too, about your customers’ mail. Set up where each kind of request lands, what new accounts receive, and what you promise, before the first signup.
What the support desk handles
| Request | Who sends it | Where it is covered |
|---|---|---|
| Account review: why the account cannot send yet | New accounts, which start Untrusted | Stage 8, abuse prevention |
| Sender domain DNS: records that do not verify | Customers adding their domain | Stage 6, sender domain authentication |
| Deliverability: bounces, blocks, the spam folder | Customers who are sending | Stage 10, deliverability operations |
| Billing: failed payments, plan changes | Paying customers | Stage 9, Stripe billing |
| Abuse reports | Recipients, mailbox providers, blocklist operators | abuse@, stage 2, legal and policies and stage 8, abuse prevention |
Octeth’s in-app support form uses almost the same split. Its categories are Account review, Billing, Sending and deliverability, Technical or API, and Other. An Untrusted account opens the form with Account review already chosen, because that is what new accounts ask about.
Keep abuse reports out of the customer queue. They come from people who are not your customers, they need the full message headers to find the sending account, and they carry their own response promise. Stage 2 covers the abuse@ mailbox and the report-abuse page.
Choose where support requests land
Two brand settings decide where every Contact support link in the new interface goes (Branding in the staff area):
- Support URL. A help desk or contact page. Every Contact support link opens it in a new tab.
- Support email. With no support URL, Contact support opens the in-app support form, which mails this address. The address is also shown after signup, and it is the seller email on invoices unless your invoice details set another one.
With both empty, the Contact support links are hidden.
The in-app form, from Octeth 6.0.5, sends the request to your support email with Reply-To set to the customer, so you answer from your own inbox (a request staff send from inside an account replies to the staff member instead, and sends the customer no acknowledgement). It adds the account’s user ID, name, email, trust level, user group and plan, and the page the customer came from. The customer gets an acknowledgement without their text. Octeth stores nothing, and each account can send 5 requests an hour. The form needs working system mail for the new interface, which stage 4 sets up.
We recommend leaving the support URL empty and using the in-app form, because each request then arrives with the account details. Tell existing customers on your contact page to use Support in the app sidebar.
Which help desk tool to use behind the support address is your choice. We have no first-hand comparison to give.
Plan the onboarding sequence
What Octeth sends
| When | |
|---|---|
| Welcome, with the verification link | At form signup. The account stays disabled until the link is clicked. The link expires after 7 days. Accounts created with Google sign-up are enabled at once. |
| Password reset | When the customer asks for one |
| Support acknowledgement | After each in-app support request |
| Account approved | When staff mark an account Trusted after it submitted the review questionnaire, from Octeth 6.0.6 |
| Payment failed, account suspended, subscription ended | Through billing, covered in stage 9 |
The new interface sends these under your brand’s sender name. The approval email goes through the classic app’s system mail instead, so set up both senders in stage 4. The dashboard also shows a four-step checklist until the first campaign is sent: create your workspace, verify your sending domain, import your first contacts and send your first campaign. Each step ticks itself from the account’s real state.
What you add
Run the onboarding series from your own email tool. The operator webhook sends a user.signed_up event for each account that signs itself up, by form or by Google (Webhooks for sign-ups and subscriptions). Point it at an automation tool that adds the account to a list in your own email tool, and run the sequence from there. Stage 8 uses the same event to tell staff about each signup.
Write the sequence around what blocks the first send:
- Account review. A new account cannot send until staff approve it. Say what the review asks, how long it takes, and how to answer questions.
- Sender domain. Link the help doc for the DNS records, and offer help with them.
- First contacts and first campaign. Link the import rules from your acceptable use policy.
Then decide which servers send it. Send system mail through an SMTP host on a different IP from your customers’ delivery servers (stage 4, installing Octeth). Onboarding mail sent from your shared customer IPs shares their reputation.
An agency platform with closed signup needs no automated sequence. A person creates each account and walks the client through these same steps.
Write the help docs customers need
Your customers need docs for the parts of the platform that are yours, not only the email editor:
- Sender domain setup. Each record the sender domain screen shows, where to add it, and the common errors, such as a second DMARC record. Stage 6 lists the records and the mistakes we have seen.
- Account review. What you ask, what you check, how long it takes and what happens after approval.
- Plans and limits. What each plan includes and what happens at the limit: whether sending stops at the quota or overage is billed.
- Acceptable use. What you refuse, what gets an account suspended, and the bounce and complaint limits from stage 8.
- Suppression. Why an address is suppressed after a bounce, a complaint or an unsubscribe, and where the customer can see it.
- Sending by API and SMTP relay. Where credentials live and which limits apply.
Use the labels your customers see on screen. Path settings rename a section’s address, not its label (stage 4). If your brand hides the platform behind it, do not send customers to Octeth’s own docs. The brand’s Documentation URL (from 6.0.5) adds a Documentation item to the user menu. Empty hides it.
Set response targets
Publish a first-response target for each kind of request: urgent requests when the service is unavailable, all other requests, and abuse reports, which need a target of their own. Lessons from our builds:
- Promise a first reply, not a fix. Say in your terms that the target is for a first reply, not for resolving the issue.
- Say what a missed target means. State that the times are targets, not guarantees, and whether missing one earns a service credit.
- Define work days. Name the days, the time zone and the holidays in your terms, or “24 hours” has no fixed meaning.
- Promise only the coverage you staff. If nobody reads support at weekends, say so.
- Match the review time. The account review settings (from 6.0.6) have a review time sentence that shows on the review banner, the review page and the support page. Leave it empty or make it true.
Stage 2 covers where these commitments go in your terms. Pick the numbers yourself.
Before you move on
- Every Contact support link in the app goes somewhere a person reads: a support URL or a support address.
- You sent a test request through the in-app form and got both the request and the acknowledgement.
- Abuse reports go to abuse@ and are handled apart from customer requests.
- The operator webhook is on before signups open, and a test signup reached your onboarding list.
- Your onboarding emails explain account review and the steps before the first send.
- Help docs cover sender domain records, account review, plan limits, the acceptable use policy and suppression.
- Your help docs use the labels your customers see on screen, and none of them names a product you hide.
- Your response targets name the work days, the time zone, the holidays and what counts as urgent.
- The review time on the account review page matches what your staff can do.
What we've seen go wrong
A missing reset email that was a typo
A new account got its welcome email but reported no password reset email. The interface log showed one reset request, for an address with a typo. Octeth answers the same way for an address it does not know and sends nothing, so a reset form cannot tell a customer that the address is wrong. Look up the exact address in the log before you debug mail delivery.
A signup alert that failed and showed success
A workflow that posted each new signup to a staff chat failed on a real signup, because the chat step read the event's underscores as formatting. The workflow run still showed success, and that signup's alert was never resent. Test your alerts with a payload that contains underscores and angle brackets, and check failed steps, not only the run status.
Signups before the webhook produced no event
On one install, signups were open before the operator webhook was set up. An account that signed up less than two hours before the webhook was turned on produced no signup event, so it never reached the signup workflow. Turn the webhook on before you open signups, or add earlier accounts to your onboarding list by hand.
Related glossary terms
We build ESPs
Rather have us build this?
Your team supports your customers. We run the servers, the MTA and the backups behind them.