The Chat Is Over. Where Is the Record?
A phone call leaves nothing behind. A chat can leave a better record than an email thread — if somebody decided what the record is. What a support transcript should carry, and what ours does.
Three weeks after a support conversation, someone asks the question every operations team dreads: what exactly did they tell us? On a call, the answer is whatever two people remember. In a chat, the answer should be on paper. Too often it is in a window that closed, under a login that expired, attached to a screenshot that no longer opens.
Four things a transcript has to carry
A transcript worth keeping
- Every line, in order, with the time and the name of who wrote it
- The files that were shared — the files themselves, not a list of names
- How it ended, and who ended it
- A copy somewhere other than the customer’s inbox
Each of those closes a specific argument. Times settle when advice was given. Files settle what was looked at. The ending settles whether the matter was closed or abandoned. The second copy settles that the first was not edited.
Files that open in three years
Links to shared files in a chat are short-lived on purpose: they are private documents, and a link that works forever is a link anyone who finds it can open. That makes a link the wrong thing to put in a record. So when an answered chat with AWRA support ends, the files travel with the email as attachments, up to fifteen megabytes in total, and open in any mail program for as long as you keep the message. Anything beyond that arrives as a download link that works for thirty days, with a note beside it saying so.
A record that depends on a link is a record with an expiry date.
Who ended it, in words
Every chat closes on one line that names who closed it — “Ada ended the chat”, “Washingtone from AWRA support ended the chat”, or that it closed after thirty minutes with no new messages. The customer, the representative and the transcript all show the same words. A transcript that just stops does not tell you whether the question was answered or abandoned; one that ends on a name does.
Two copies, two inboxes
The transcript goes to the email address the conversation was held under, with our support inbox copied. You hold your record; we hold ours; and they are the same document. If nobody picked up the chat within three minutes, it never becomes a dead end either: it lands in the support inbox as a message, with the conversation and its file links, and is answered by email.
How the chat itself works is covered in a person in three minutes, or an email.
Test any support transcript you receive
Can you tell who wrote each line?
It should show
A name and a time on every message.
If it does not
It is a summary, not a record.
Do the shared files open without signing in?
It should show
Attachments, or links that say when they expire.
If it does not
Save the files now, while the links work.
Does it say how it ended?
It should show
A closing line with a name.
If it does not
Ask whether the matter was resolved.
What AWRA OpsHub does today
- A transcript emailed when an answered chat ends, with the AWRA support inbox copied
- Every line with its time and its writer
- Shared files attached to the email up to fifteen megabytes in total, with thirty-day links beyond that
- A closing line that names who ended the chat
- Unanswered chats passed to the support inbox with their file links and answered by email
More we can add to your workspace
- A history of past chats inside your workspace
- Transcripts saved as PDF to a record of your choosing
- A retention period for chat history set by your organization
Where we point you to a specialist
- A support chat records advice about using the product. Changes to a contract, a price or a plan are agreed in writing with your account contact, not in a chat.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsVerdict
Decide what the record is before the conversation starts: every line with a name and a time, the files themselves, a named ending, and a second copy. Then a support chat is the best evidence you have of what you were told.
Keep a record of every answer
Chat with AWRA support from the app or our website, and keep the transcript when it ends.
How support chat worksFrequently asked questions
Do I get a transcript of my live chat with AWRA support?
Yes. When a chat that a representative answered ends, the conversation is emailed to you and the AWRA support inbox is copied.
Are the files I shared included in the transcript?
Yes. They are attached to the email, up to fifteen megabytes in total, so they open in any mail program. Files beyond that limit arrive as download links that work for thirty days.
How do I know who ended the chat?
Every chat closes on a line that names who ended it, or says it closed after thirty minutes with no new messages. The same line appears for you, for the representative and in the transcript.
What happens to a chat nobody answered?
After three minutes it is passed to the support inbox as a message, with the conversation and links to any files, and answered by email.
