We built an email and diary assistant for our own business. The useful part is having the writing started and the relevant information beside it. The examples here are made up.
Less time writing the same email replies.
Get a draft ready to check, instead of starting again after a busy day.
An email arrives
Someone asks about work you offer.
A reply is drafted
Approved information supplies the answer.
You review and send
Check the wording and the latest message.
Missing prices or dates need review. Check the draft before sending.
Stop writing the same answer from scratch
Choose a question you answer regularly. Perhaps someone asks whether you offer a particular service, or what information you need before preparing a quote. Give the assistant current, approved business information to work from.
A draft can explain the service and ask for missing details without you hunting for an old reply to adapt.
Consider a made-up enquiry asking for work next month without describing the job. The reply should ask what work is needed. A date in someone's request doesn't establish that you have space in your diary.
Check the draft beside the incoming message. Prices, availability and promises need a source you trust. If that information isn't available, the reply should ask a question or flag the gap for you.
The setup needs to fit how you answer people. If the latest job information sits in local files or a separate customer system, agree how the drafting tool gets the approved details. We check the tools and working habits first, so you do not have to copy everything into a new app just to get a useful draft.
Keep control without rewriting every word
You need a draft short enough to review while you're busy. An extra offer, a suggested start date or a promise to include something creates another decision. Tell the writing step what it can use and what it must leave for you.
For example:
Prepare a short reply from the incoming message and our approved business information. Ask for missing details. Do not invent a price, available date or commitment. Save the reply for review and flag anything those sources cannot answer.
Enforce the sending limit in the software, as well as in the writing instructions. The content of an incoming email must not be allowed to change those limits or reveal another conversation.
Keep complaints and negotiations with a person when testing a first version. They involve decisions about the relationship and the work, beyond repeating an approved answer.
A waiting draft can become out of date
Read the latest message before sending. Someone may have supplied the missing detail or a colleague may already have replied. Check the recipients too.
If several people share the inbox, agree how they show who is reviewing a reply. Two people checking competing drafts can create more work than the tool removes.
Test made-up requests separately from live work, including missing information and changed circumstances. After adjusting the instructions, repeat the checks. Keep a record of drafts you accepted and what you changed.
If you keep removing the same invented promise, stop and fix that behaviour before adding more message types. Count the review time too; it is part of the email job.