How do you get AI to write customer emails that don't sound generic?

Feed it the specifics. Paste the customer's actual message, their order or account record, and one or two examples of how your business already writes. A reply that names the real order number, repeats back the problem in the customer's own words, and matches your house voice reads as written by a person. Generic comes from drafting on a blank slate. Physea can pull those specifics from your connected tools so the draft is grounded before you see it.

When should you send a follow-up text to a lead who got a quote but didn't book?

Within about an hour of them viewing the quote, while the decision is still warm. Keep it to two sentences and one clear question, for example whether they'd like to lock in a date or have a question about the price. One nudge that day, then one more after two or three days. After that, more texts annoy rather than convert. Physea can watch for the quote view and draft the message keyed to that job.

Is it OK to use AI for appointment reminders and confirmations by text?

Yes, and it works well because reminders are short and structured. Include the date, time, address, one prep instruction, and a reply-to-confirm or reschedule option. Honor opt-outs and avoid sending outside reasonable hours. Get consent before texting and keep an easy STOP path. Physea can assemble the reminder from your calendar and send it on a schedule across your patient or customer list.

How do you use AI to draft customer emails, replies, and follow-ups?

Use AI to read each message's intent first, then draft a reply that matches the customer's tone and pulls in the real details: their order number, appointment time, or the exact line they wrote. The hard part is not the writing, it's the judgment about intent, tone, timing, and grounding. This page covers replies, support-inbox tagging, lead follow-ups, and short SMS reminders and confirmations.

Last updated 2026-06-14 · Physea Labs

Customer messages stack up faster than anyone can answer them well. A retail support inbox fills with refund requests, where-is-my-order questions, and the occasional angry note, all mixed together. A roofing crew has three quotes sitting unanswered while the leads cool off. A dental front desk needs to remind tomorrow’s patients without sounding like a robot. The writing itself is rarely the bottleneck. The bottleneck is doing it quickly, in your voice, with the right facts, for every single message, all day.

That’s why this work eats hours. Each reply is small, but there are many, and a sloppy one costs you more than the time saved.

What actually decides the outcome

A good customer message hinges on a few judgment calls, not on vocabulary.

Reading the intent before you write. A “where is my refund” email and a “I want to cancel” email look similar and need opposite replies. Misread the intent and the rest is wasted. For a support inbox, tagging each message by what the customer actually wants (refund, shipping, product question, complaint) is the step that decides everything downstream.

Tone matched to the relationship and the channel. A long-time client and a first-time buyer get different warmth. And a text is not a shortened email. A 160-character SMS has no room for throat-clearing, so it has to carry the date, the ask, and a way to reply, and nothing else.

Grounding in the real record. The single biggest tell of an AI-written or template reply is vagueness. Naming the actual order number, the appointment time, the exact line the customer wrote, that is what makes it land as real. Generic erodes trust faster than a slow reply does.

Timing and how many touches. A quote follow-up an hour after the view converts; the same words three days later mostly don’t. And there’s a ceiling: one or two nudges help, the fourth annoys. Knowing when to stop is part of the skill.

Consent and quiet hours for texts. SMS is regulated and personal. Get consent, keep a working STOP path, and don’t send at 11pm.

How to do it by hand

This is the honest manual approach, and it works:

Sort first, write second. Skim the inbox and tag each message by intent. Group the refunds together, the shipping questions together. Batching like-with-like is faster than answering top to bottom.
Pull the record. Before drafting, open the order, the job, or the appointment so the real details are in front of you.
Draft from a real example. Keep two or three of your own best past replies. Start from the closest one, then swap in this customer’s facts and their problem in their words.
Calibrate tone to who it is. First-timer, loyal regular, or someone upset all get a slightly different opening line.
For follow-ups, set the clock. Note when a quote was sent or a cart abandoned, and schedule the nudge for the window that still has heat (an hour for hot leads, a day for carts).
For texts, keep it to one job. Date, place, one instruction, one reply option. Confirm consent and skip late hours.

Where it goes wrong

The common failures are predictable. Replies that never name the order number read as form letters. A support queue answered top to bottom instead of by intent means urgent complaints wait behind easy questions. Follow-ups sent days late, after the lead already booked a competitor. Texts that read like a paragraph and get ignored, or worse, sent without consent. And the slow drift where, under volume, every reply starts sounding identical and customers feel processed rather than helped.

Doing it yourself vs. handing it to Physea

By hand, you can write a genuinely good reply. The cost is that you have to do it for every message, pull every record yourself, and keep the timing in your head. At ten messages a day it’s tedious; at a hundred it’s a full-time job, and quality slips exactly when volume spikes.

Physea’s Liminality runs the whole thing over MCP, across the tools you already use. It reads the incoming message, tags it by intent, pulls the matching record from your store or calendar, drafts the reply or text grounded in those real details and in your voice, and handles the timing for follow-ups and reminders. It reuses what worked before, so the system gets sharper the more it runs. You review and approve the outcome instead of doing the chore. The point isn’t a faster typist; it’s that the right message, with the right facts, goes out at the right time without you assembling it each time.

For chasing unpaid balances and dunning specifically, see the companion page on payment reminders, and for responding to public feedback, see online reviews.

Common questions

How do you get AI to write customer emails that don't sound generic?: Feed it the specifics. Paste the customer's actual message, their order or account record, and one or two examples of how your business already writes. A reply that names the real order number, repeats back the problem in the customer's own words, and matches your house voice reads as written by a person. Generic comes from drafting on a blank slate. Physea can pull those specifics from your connected tools so the draft is grounded before you see it.
When should you send a follow-up text to a lead who got a quote but didn't book?: Within about an hour of them viewing the quote, while the decision is still warm. Keep it to two sentences and one clear question, for example whether they'd like to lock in a date or have a question about the price. One nudge that day, then one more after two or three days. After that, more texts annoy rather than convert. Physea can watch for the quote view and draft the message keyed to that job.
Is it OK to use AI for appointment reminders and confirmations by text?: Yes, and it works well because reminders are short and structured. Include the date, time, address, one prep instruction, and a reply-to-confirm or reschedule option. Honor opt-outs and avoid sending outside reasonable hours. Get consent before texting and keep an easy STOP path. Physea can assemble the reminder from your calendar and send it on a schedule across your patient or customer list.