The morning reply round: clear every waiting customer before lunch

Most lost deals are not lost on price. They are lost because a reply took two days. The morning reply round is a short routine that makes sure nobody who wrote to you yesterday is still waiting today.

1. Ask who is waiting

Open Claude, Cursor or whichever agent you connected to Apavin and ask: "Who is waiting on a reply?" The agent calls get_reply_queue, which returns every conversation where the customer wrote last, across business email and WhatsApp, oldest first. WhatsApp threads show how long their 24 hour window has left.

Apavin also ships this as a ready prompt called morning_reply_round. In clients that show MCP prompts, pick it from the list.

2. Load your house rules

Ask the agent to read your reply guidelines first. get_reply_guidelines returns the instructions your admin wrote in Apavin (tone, what you never promise, how you sign off) plus your business details and the titles of the documents you uploaded, such as a price sheet. Every draft then starts from your rules instead of the model's defaults.

3. Draft everything

"Draft a reply to each of them." For email, each draft is also saved to the mailbox's Drafts folder. For WhatsApp, the agent checks the window and uses an approved template where it must.

4. Approve in one pass

Open Settings, MCP, Approvals in Apavin. Every message is there with its recipient, account and text. Approve, edit in your mailbox, or decline. Each approved message is sent once, even if a client retries.

5. Leave a trail

Ask the agent to add a note to each customer and to create follow-up tasks for anyone who needs a call. add_customer_note and create_follow_up_task write to the customer record in Apavin, so the next person sees what happened.

How long does it take?

With ten to fifteen waiting conversations, the agent's part takes a couple of minutes. Reading and approving is the rest. The aim is that the person spends their time on judgment, not typing.