Support agent
Answers tickets, issues refunds inside your limits and escalates the rest.
- Last night
- 19:26Refunded order #48213 under the 30-day policy
- 01:52Answered 64 tickets in German and Japanese
- 07:41Drafted 19 enterprise replies for review
Stillhour agents answer tickets, match invoices and research leads from 6 pm to 8 am. Your team comes in to a handover report and a short list of calls only a person should make.
Tickets, invoices, leads and alerts keep coming after everyone logs off. At 9:00 your team opens a pile that sat there all night, and starts the day behind.
Six agents, each with one job and its own limits. Hover one to see when it worked last night and what it did.
Answers tickets, issues refunds inside your limits and escalates the rest.
Matches invoices to purchase orders, reconciles payouts, holds anything odd.
Researches sign-ups and accounts so the 9:00 calls start warm.
Runs scheduled jobs, rotates keys and writes the handover.
Screens applications and books interviews across calendars.
Checks every action against your rules and keeps the audit log.
Nothing clever. The day team writes a brief, you set the limits once, agents work with receipts, and the morning starts with a report instead of a pile.
The day team leaves notes: open threads, VIP customers, anything unusual. Agents read them before they start.
You decide what each agent may do, how much it may spend, and when it has to stop and ask a person.
Every action is logged with the reason, the data it used and an undo button.
One report: what got done, what was held, and the few decisions that need a person.
Write limits the way you would explain them to a new hire. Every rule shows how often it was used last night, and you can switch one off without touching the rest.
Every agent gets its own permissions for every tool: read it, draft in it, act in it, or stop and ask a person. Change a cell and the policy rewrites itself in plain English.
Support agent can read the help desk, billing, the CRM and email; draft replies, refunds and emails; and close tickets and issue refunds. It must ask a person before sending email, closing a ticket from a VIP customer or refunding anything over $500.
Connect the help desk, billing, bank feed and the rest in a few minutes. Agents start with read-only access, and you choose what they may change.
Answers and closes tickets, and tags anything the day team should see.
Without agents the weekend piles up, and Monday starts with a queue. With Stillhour the night shift works it down and leaves a short list for a person.
| Tickets | 212 → 9 |
| Invoices | 140 → 12 |
| Leads | 96 → 14 |
| Alerts | 58 → 5 |
The orange hatch is work agents finished between Friday evening and Monday morning: 466 items, each one logged and reversible. What is left at 9:00 is the short list for a person.
Customers · after the first month
All customer stories
Plans are priced by how many hours a day your agents cover. Move the slider to see what your night would cost.
For teams that want the night covered and the day to themselves.
For teams whose customers never close the laptop.
For regulated teams and custom workflows.
Kestrel Supply, Halvard Health, Tessel Pay, Carrow Air.
“We used to open Monday with 212 tickets waiting. Now it's nine, and the handover tells us which nine need a human.”
A solutions engineer walks through one of your real queues and shows what a night shift would have done with it.
Book 20 minutesIt stops and asks. Anything below the confidence threshold you set, or outside the rules you wrote, goes into the handover report as a decision for a person, with the context and a suggested answer. Agents do not guess.
Setup takes about a week. Your first supervised night is on us.