Client Update: Task Acknowledgment and ETA
Purpose: confirm you received a client request, show you understood it, and commit to a delivery time.
Use it when: the client sends any task by message, email or voice note.
Goal: the client knows, in one message, that the task is owned and when it will be done.
Version: v1.0
Before you send
- Read the full request, including attachments and any earlier messages on the topic
- Check the Client Workflow Record: is there a task card for this?
- Check today's priorities: can you meet a realistic time?
- Note the client's time zone for the ETA
- Respond within the Communication Standard window (see Narqix Standards)
The flow
1. Acknowledge and restate
You: Got it, (CLIENT FIRST NAME). You need a list of 30 roofing contractors in (CITY) with phone, website and licence status.
Why it works: restating proves you understood and catches misunderstandings before you start.
2. Commit to a time, with the zone
You: I will have it to you by 3:00 PM ET today.
Why it works: a named time and zone replaces worry with a plan.
3. Ask only what blocks you, with your suggestion
You: One question: should I include companies that only do residential? My suggestion is commercial only, since the job is a warehouse. Reply "yes" if that works.
Why it works: one question with a suggested answer lets the client reply in one word.
If the task will take longer than the client expects
You: Got it. A full list of 100 will take until tomorrow 12:00 PM ET. I can send the first 30 today by 4:00 PM ET so you can start calling. Does that work?
Offer a partial delivery first. Never accept a deadline you know you will miss.
If the task conflicts with another priority
You: Happy to do this. It would push the invoice batch from 2:00 PM to 5:00 PM ET. Which should go first?
Let the client choose the order. Never quietly drop one task for another.
If the task is outside scope or risky
You: Thanks for sending this. Because it involves changing payment details, I will confirm with you by phone first, as we agreed for any payment changes.
Out of scope requests go to your Narqix lead. Risky requests (money, deletion, mass sending) get a read back before action.
4. Update before the deadline if anything changes
You: Quick update: 22 of 30 done. Two sources are slow to load, so the full list will be at 3:30 PM ET instead of 3:00. The first 22 are in the sheet now.
Why it works: an early update is professional; a missed deadline with no warning breaks trust.
Tricky replies
| Client says | You reply |
|---|---|
| "Can you just do it now?" | "Yes, starting now. You will have it by (TIME AND ZONE)." (Then reshuffle and tell them what moves.) |
| "Why so long?" | "It is 30 contractors with licence checks, about 6 minutes each. I can send the first 10 within the hour if that helps." |
| No reply to your question | Proceed with your stated suggestion and say so: "No reply yet, so I went with commercial only, as suggested." |
After you send
- Create the task in the task tracker: title, ETA with zone, link to the request.
- Add it to your start of day priorities or end of day report.
- Set a reminder 30 minutes before the ETA to check you are on track.
Coach's note: never send just "Noted" or "Ok". Those words tell the client nothing. A good acknowledgment answers three questions: did you understand, when will it be done, and do you need anything?
© Narqix Academy