Email autoresponder etiquette

Written by Aashiq, Founder, AskVault · Reviewed by Aashiq

Last updated: May 15, 2026 · 3 min read

Rule 1: identify as bot

Customers trust bots that disclose. Avoid lying.

Good footer:

Sent by your AI assistant. Reply for human help.

Bad footer:

[no indicator; impersonating a human]

Disclosure improves response rate by 10 to 20% in customer-research studies. Avoids backlash if customer realizes later.

Rule 2: respond fast

Email is high-tolerance channel; customers expect under 4 hours normally. Bot beats that:

Bot reply within 60 seconds of receipt.
Compare: human auto-reply within 4 hours; full human reply within 24 hours.

Speed-to-reply alone lifts CSAT noticeably.

Rule 3: keep replies concise

Email allows long replies, but concise wins:

Under 300 words for routine answers.
3 to 5 sentences is the sweet spot.
Lead with the answer, then context.
End with a clear next step ("Need more help? Reply or visit our help center.").

Long bot replies feel auto-generated. Concise feels human.

Standard footer:

[Bot reply]

AskVault Support support@askvault.co | yoursite.co Sent by AI assistant. Reply for human help.

Configure under Deploy Hub > Email > Sender Identity > Signature.

Rule 5: offer human escape

Every bot reply should make escalation easy:

Was this helpful? Reply YES, or reply with "agent" to talk to a human.

About 5 to 15% of email customers prefer human contact. Make the path frictionless.

Avoiding spam triggers

Bot emails sometimes land in spam. Reduce risk:

SPF/DKIM/DMARC configured on your domain.
Avoid spam-triggering words in subjects (free, urgent, win, $$$).
Don't send to invalid addresses (bounce rate impacts sender reputation).
Vary message-IDs and timestamps (built-in; just ensure no rapid-fire bot sending).
Warm up new domains by sending low volume first.

Standard email deliverability practices.

Subject-line conventions

For bot replies:

Prefix with "Re:" automatically.
Match original subject if exists.
Don't include "Auto-reply" explicitly (some filters demote).

For proactive bot emails (rare):

Clear subject like "Order #12345 shipped".
Avoid clickbait that triggers spam.

Threading

The bot replies to the original message:

In-Reply-To and References headers set correctly.
Quoted message appended below the reply (configurable).
Single thread in customer's inbox.

Useful for keeping conversation coherent.

When the bot shouldn't auto-reply

Five cases:

Customer messages from a clearly-personal address about a sensitive issue.
Subject indicates urgency ("URGENT", "SOS", "DOWN").
Customer marked VIP in CRM. Escalate to a human immediately.
Auto-responder loop detected (their out-of-office plus your auto-reply ping-pong).
Subject contains "harassment", "abuse", "legal" etc.

Configure exclusions under automation rules.

Draft-only mode

For sensitive workflows:

Bot drafts reply but doesn't send.
Lands as a draft in your Gmail/Outlook.
Human reviews and clicks Send.

Hybrid mode: draft on sensitive topics, auto-send on routine. Configure per topic/tag.

Measuring success

Track:

First-response time. Should be under 60 seconds.
Resolution rate. % bot-resolved vs human-needed.
CSAT. Send survey after resolution.
Spam rate. Replies landing in spam (monitor sender reputation).

Visible under Analytics > Channel: Email.

Common pitfalls

Bot too verbose. Trim response-length setting.

Generic auto-reply feel. Customize the system prompt for tone.

Customers don't know it's a bot. Add the disclosure footer.

Replies break threading. OAuth handles correctly; IMAP can drift. Use OAuth when possible.

FAQ

Should I tell customers they're talking to a bot?

Yes. Trust improves; backlash drops. Disclosure is best practice.

Can I have a different tone per topic?

Yes via skill messages per skill or automation rules.

Do regulatory rules require disclosure?

Some (California Bot Bill, EU AI Act). Confirm with legal. AskVault default disclosure satisfies most.

Was this page helpful?