- Industry
- Oil & Gas
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-03
It answers fleet-card holders and station retailers in live chat in short turns from the chat playbook and the account, covering card blocks, PINs, transaction queries, delivery slots and portal help. It hands the chat to a person with a summary as soon as it cannot help, the customer asks, or anyone mentions a safety problem, and logs the outcome on the customer's record.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the chat platform: the conversation and the customer's account, cards and recent transactions..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Customer Service Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the chat platform: it posts the reply, or transfers the chat to the human queue with the handoff summary, and logs the outcome. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The chat playbook: fuel-card help (blocks, PINs, limits, declined transactions), the ordering portal, delivery slot rules, station-network questions and the emergency handoff script.
Reads from
the chat platform: the conversation and the customer's account, cards and recent transactions.
Acts in
the chat platform: it posts the reply, or transfers the chat to the human queue with the handoff summary, and logs the outcome.
Hands back
An object with reply, action (answer, block_card, handoff or callback), handoff_summary (or null) and outcome.
Asks a person when
The chat touches a disputed transaction, suspected card fraud, a safety report or a change to account details.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest reply (sentences) | 3 | Each turn stays this short. |
| Hand off after (turns) | 6 | Unresolved after this many turns, the chat goes to a person. |
| Block a lost or stolen card in chat | On | After verification it may block a card, never unblock one. |
| Change limits or details in chat | Off | Card limits, product restrictions and billing details are never changed in chat. |
| Hours a person is on chat | Mon-Sat 06:00-22:00 | Outside these, the chat offers a callback. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep each reply to 3 sentences.
- Hand off immediately when anyone mentions a leak, spill, fire, smell of gas or fuel, or an injury, with the emergency number in the reply.
- Block a lost or stolen card only after verification and when on is on; never unblock a card or raise a limit in chat.
- Never change card limits, product restrictions or billing details when off is off.
- Hand the chat to a person after 6 unresolved turns or when asked, during Mon-Sat 06:00-22:00, with a summary so the customer does not repeat themselves.
See the Live Chat Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.