The order placed at three in the morning is not an edge case. Between evening browsers, other time zones and the simple fact that people shop when their day allows, a third of a storefront's clock runs while its owner is asleep. The question is not whether things happen overnight — they do — but whether anything answers.
Here is what a typical night actually contains for a small storefront: a customer asking where yesterday's order is, someone abandoning a basket over a shipping question, a booking request from a customer six hours ahead of you, a size query on a product page, and one genuinely unhappy message composed at midnight with feeling. Five conversations. Each one is either answered in the moment or waiting to become something worse at breakfast.
The four conversations that happen after hours
- Where is my order — the highest-volume question in commerce, and the easiest to answer perfectly if the agent can see real order state.
- Can I change or cancel — time-sensitive by nature; an answer at 8 a.m. is often an answer to a question that no longer matters.
- Does it fit, does it suit, is it in stock — pre-purchase questions where an instant answer is frequently the sale itself.
- Something is wrong — the message that most needs acknowledgement in minutes, because grievance compounds overnight in a way gratitude does not.
The common thread: none of these can be handled well by a canned reply. They are only worth automating if the agent is answering from the actual state of the business — the order record, the stock level, the booking calendar, the returns policy as written. An agent that answers confidently without that grounding is worse than voicemail.
What "answering" has to mean
Reads the real state
The agent sees orders, inventory, bookings and the customer's own history — so "where is it" gets a tracking status, not a promise that someone will check.
Acts inside guardrails
Some actions it takes outright; some it queues for your approval; some it is simply not allowed. You set those lines per action, and every step is logged.
That second half is the part that lets you actually sleep. On a Phoxta business the agent's write-access is governed: each kind of action — issuing a refund, moving a booking, changing an order — is set to off, approve-first, or automatic. The overnight refund request does not silently empty the till; it sits in an approval queue with the conversation attached, and the audit trail records everything the agent did and why.
The morning after
The measure of a good overnight agent is what your first coffee looks like. Instead of an inbox of small fires, you get a briefing: conversations handled, orders taken, the two decisions that genuinely need a human, queued and contextualised. The number to watch is first-response time across the whole clock — when the 3 a.m. customer and the 3 p.m. customer get the same experience, the night has stopped being a liability.
Customers do not experience your working hours. They experience your response times.
Every Phoxta business ships with this as standard equipment — the agent on every channel, the governance controls, the audit trail and the morning briefing. The pricing page shows the plans; the night shift is included.
