Pagerox for support
A support queue is the same five jobs over and over: look up what happened, draft the answer, make it right, tell the team, and catch what came in overnight. This guide gives all five to one agent and keeps every refund and every sent reply in your hands.
1. One agent, five jobs
Create an agent for support; Lumen Labs calls theirs Sol. Tell it the jobs in the thread, in your own words. It does not need a description or a form.
- Look up an order or an account when someone asks what happened.
- Draft the reply in the tone you use.
- Refund or credit, inside the policy you give it.
- Post a short summary of the day.
- Sweep the queue on a schedule and flag what needs a person.
2. Connect the help desk and payments
The first time the agent needs your help desk or your payment tool it shows a Connect card. Sign in once. More apps are behind the plus under Apps in the agent's panel, and a tool of your own can be added there as an MCP server by its address.
3. Teach the refund policy once
Walk the agent through one real refund and tell it the policy as you go: what is covered, up to what amount, what it should attach, when it should stop and ask. Then ask it to save that as a skill.
A skill is plain text you can read on the card before you save it. When a later refund goes differently, the agent proposes an update and shows only the lines that change. You accept it or dismiss it.
4. Approvals on money and replies
Paying and sending wait for you by default. A refund arrives as an approval card that names the customer and the amount. Allow once runs it. Deny stops it and the agent says so in the thread.
When you trust a narrow case, Always allow saves a rule and the card says which. Keep an Ask first rule for the rest, for example for any refund above your limit. Ask first always wins over Always allow, and both live under Settings, Auto-review.
5. Work that runs after you log off
Ask for the recurring jobs and they show up under Work in the panel, each with a toggle. They run on the agent's computer in the cloud, so nobody needs to be signed in. A schedule can fire as often as every 15 minutes.
- "Every 15 minutes, read the new tickets and tell me which ones need a person."
- "Every weekday at 17:00, post the summary of the day."
- "When a mail arrives at your address, open a ticket for it and draft the reply."
Work can also start on something that arrives: a message in a Slack channel, or a mail to the agent's own address. When a run ends, you get a short email that says what it did. Anything it wanted to send or refund on the way waits for you as a card.
Next: Sharing agents with your team, so the whole team can ask Sol from Slack.