Customer Text + Email Communication Reference

Why this matters

Text + email are primary customer communication for many service businesses. Customers expect quick response + clear messaging. The tech who communicates well in writing builds trust + reduces miscommunication. This is the field card.

When to text vs call vs email

Text:

  • Quick updates
  • Appointment confirmations
  • "On my way" notices
  • Brief questions
  • Customer responses time-flexible

Call:

  • Urgent (immediate response needed)
  • Complex topics (back-and-forth)
  • Emotional / sensitive
  • Customer prefers
  • After-hours emergencies

Email:

  • Documents (estimates, invoices, manuals)
  • Detailed information
  • Photos / videos
  • Records customer needs to keep
  • Less urgent

Match channel to message.

Customer preferences

Ask:

  • "Do you prefer text, call, or email?"
  • "Best number for text?"
  • "Best email?"

Note in service record. Use what customer wants.

Texting best practices

Identify yourself:

  • First text: "Hi [Customer], this is [Name] with [Company]"
  • Customer knows who you are

Brief + clear:

  • Get to point
  • Customer reading on phone (small screen)
  • Long messages: send as email instead

Professional tone:

  • No slang / abbreviations (or sparingly)
  • No emojis (unless customer initiates style)
  • Proper grammar (auto-correct helps)
  • Customer's name

Wait for response timing:

  • Customer may be working / driving
  • 1-2 hours for response normal
  • Don't bombard

Sample text exchanges

Appointment confirmation: "Hi [Customer], this is [Name] with [Company]. Confirming your service tomorrow [day] between [time window]. Reply YES to confirm OR call to reschedule. Thanks!"

On my way: "Hi [Customer], heading to your home now; arriving around [time]. - [Name]"

Running late: "Hi [Customer], running about 30 min behind. Will arrive around [new time]. Apologies for the delay. - [Name]"

Diagnostic update: "Hi [Customer], I diagnosed the issue. It's the [component]. Repair comes to [amount]. Want me to proceed? Reply YES to authorize."

Follow-up after service: "Hi [Customer], thanks for letting us serve you today. Everything working OK? Any questions? - [Name]"

Email best practices

Subject line:

  • Clear + specific
  • "Service Estimate for [Address] - [Date]"
  • Customer can find later

Greeting:

  • "Hi [Customer]," OR "Dear [Customer],"
  • Professional

Body:

  • Organized
  • Bullet points for lists
  • Short paragraphs
  • Concrete details

Closing:

  • "Best regards" OR "Thanks"
  • Your name + title
  • Company info + phone
  • Logo if customary

Attachments:

  • Properly named (not "scan_001.pdf")
  • Reasonable size (compress if large)
  • Confirm received

Email signatures

Professional signature:

[Name], [Title]
[Company Name]
[Phone] | [Email]
[Website]
[License # if applicable]
[Logo]

Consistent across team; reflects company brand.

Auto-replies

For:

  • Out-of-office (vacation, training)
  • After-hours acknowledgment
  • Acknowledgment of receipt (large companies)

Sample after-hours: "Thanks for your message. Our office hours are [hours]. For emergencies, please call [emergency line]. Otherwise we'll respond next business day."

Response timing

Customer expectations:

  • Text: same business day usually
  • Email: 24 hours
  • Emergency: immediate

Don't:

  • Ghost customers (no response)
  • Delay for days
  • Send "we'll get back to you" without follow-through

Customer urgent texts

If customer texts urgent issue:

  • Acknowledge quickly ("Got your message; calling now")
  • Call immediately
  • Don't keep them waiting in text

Texts at inappropriate times

Avoid:

  • Very late evening (after 9 PM)
  • Very early morning (before 8 AM)
  • Weekends (for routine matters)

OK:

  • During business hours
  • After hours for emergencies
  • Customer-initiated (you can respond when reasonable)

Documentation matters

Every text + email = part of customer record:

  • Save / archive
  • Available for dispute
  • Customer can reference

Some service software captures automatically.

Privacy + security

Don't:

  • Send credit card details
  • Send passwords
  • Send sensitive customer data outside secure channels

Customer info:

  • Don't share with other customers
  • Don't use for personal communication

Group texts

When multiple parties:

  • Customer + spouse
  • Customer + family member
  • Customer + property manager

Consider:

  • All on same thread (efficient)
  • Separate threads (privacy)
  • Customer's preference

Texting from personal phone

Issues:

  • Mixes personal + business
  • Customer has your personal number
  • Hard to share with team
  • Compliance concerns (some industries)

Better: business phone OR app (Google Voice, OpenPhone, etc.)

Business communication on business channel.

Email folders / organization

For your inbox:

  • By customer
  • By project type
  • By status (active, completed)

Searchable + organized.

When customer texts complaint

Treat seriously:

  • Acknowledge quickly
  • Empathize
  • Don't argue via text
  • Often best: "Let me call you to discuss"
  • Phone for tone + back-and-forth

When customer texts threats / abuse

If customer texts:

  • Threats
  • Profanity
  • Discriminatory language

Response:

  • Don't engage in kind
  • Document
  • Escalate to management
  • Sometimes block (after consultation)

Tone matters in text

Without voice / face:

  • Easy to misinterpret
  • Brevity can read as curt
  • Punctuation matters (! vs .)
  • Customer may read differently than intended

Soften:

  • "Please" + "thanks"
  • "Just letting you know..."
  • "Want to make sure you got..."

Templates for common situations

Save time + maintain consistency:

Appointment confirmation: "Hi [Customer], confirming your appointment on [date] at [time]. Will text when on the way. - [Name]"

Estimate provided: "Hi [Customer], emailed your estimate for [work]. Total is [amount]. Let me know if any questions. Want to proceed? Reply YES to schedule."

Follow-up: "Hi [Customer], following up on the [equipment] we serviced [date]. Working well? Any questions? - [Name]"

Reminder: "Hi [Customer], reminder your [scheduled service] is [date]. Reply YES to confirm. - [Name]"

Mistakes to avoid

Texting:

  • All caps (READS AS SHOUTING)
  • No identification
  • Long paragraphs (overwhelming on phone)
  • Slang / abbreviations (unprofessional)
  • Sending multiple texts back-to-back

Email:

  • No subject line
  • Wall of text (no paragraphs)
  • All caps
  • Demanding tone
  • Missing attachments referenced

Photos via text

For service:

  • Quick proof of work
  • Verify customer's understanding
  • Document conditions
  • Easier than email sometimes

Photo quality:

  • Good light
  • In focus
  • Show what's needed
  • Not too many

Customer's photo back

If customer sends photo OR video:

  • Acknowledge receipt
  • Provide assessment
  • Schedule visit if needed

This is becoming common pre-service communication.

Email vs text for invoices

Email is the document channel. The invoice itself, the estimate, the warranty paperwork, the permit copy. Reasons:

  • Attachment survives; a texted image gets lost in a photo roll
  • Threaded record with a timestamp you can produce later
  • Customer can forward to a spouse, bookkeeper, property manager, or insurer without retyping
  • Prints cleanly for a customer who files paper
  • Line-item detail is readable on a full screen

Text is the notification channel. Short, action-prompting, time-sensitive:

  • "Invoice sent to your email, total is on it, payment link inside"
  • "Payment received, thanks"
  • "Friendly reminder, the invoice from Tuesday is still open"

The pattern that works: email the invoice, text that it was sent. Customers read texts within minutes and email within days, so the text is what actually gets the invoice opened.

Payment links: a link in a text converts better than a link buried in an email, because the customer is already holding the phone. Send the document by email and the pay link by text if your system allows both.

Never text:

  • Full card numbers or bank details, in either direction. If a customer texts you a card number, do not store it; call them and take it live, or send a payment link.
  • The only copy of a document. Text is a pointer, not a file cabinet.

Which do you use for collections: start with email so there is a written trail of the terms, escalate to text for the reminder, escalate to a phone call after that. Text-only collections read as pushy and give you the weakest record.

Match the customer: some commercial accounts require the invoice to arrive at a specific AP address or through a portal, and a texted image will never get paid. Ask at the first job how they want to be billed and put the answer in the customer record.

References

  • TCPA (Telephone Consumer Protection Act) for text marketing
  • CAN-SPAM Act for email
  • Service business communication standards
  • Manuall internal: Customer Communication Standards, Customer Documentation Discipline