Client implementation is strictly confidential. Organisation identities, internal systems and outcomes are withheld. The stories below are labelled demonstrations until a client approves publication.
Client identities, internal systems and implementation details are not disclosed. Anonymised stories and testimonial excerpts are published only with client approval.
No client-approved case studies are published here yet.
Approved stories appear in this section with the client’s written permission. Until then, the demonstration stories underneath show the operating pattern only.
Demonstration stories · Not client deployments
How an ANNA OS team is configured in practice.
These are authored examples written to show how ANNA OS roles, channels and approvals fit a real working week. They are not client-approved case studies, the quotes are illustrative writing rather than client endorsements, and no organisation is identifiable.
DemonstrationTrades & property · 40 staff
Enquiries that used to wait until Monday
After-hours reception and job enquiries
BeforeCalls, texts and web messages arrived after hours and at weekends. Whoever opened the office on Monday reconstructed them from memory, note apps and missed-call lists.
With the SAM teamA SAM receptionist answers on voice, WhatsApp and web chat, records the property, the work requested and the urgency, checks approved guidance on service coverage, and prepares one handover summary per enquiry. Appointment times are proposed, never confirmed.
Approval boundaryA site supervisor approves every appointment before it reaches a customer calendar.
“Nothing reaches a customer until a supervisor signs it off. That is the part our team actually trusts.”
BeforeThe front desk handled ringing lines, patients at the counter and a shared inbox at once. Messages that needed a clinician could sit unnoticed until the desk was free.
With the SAM teamA SAM answers calls and messages against documented urgency rules, captures the reason for contact and a callback window, and routes anything flagged clinical to the on-duty clinician instead of replying to it. Call recordings and transcripts stay available for the practice’s own review.
Approval boundaryClinical judgement stays with registered staff. Anything flagged clinical goes to the on-duty clinician, and the SAM never assesses symptoms or advises on treatment.
“The escalation reaches the clinician first. The SAM moves the conversation, never the decision.”
DemonstrationHospitality & events · Seasonal team of 25
The same question, answered the same way
Enquiry capture and quotation drafting
BeforeEnquiries arrived through Instagram, phone and email, each missing a different detail. Every quotation was rewritten from scratch, often late at night.
With the SAM teamA SAM collects dates, guest numbers, venue and dietary notes, matches them to approved menu and pricing guidance, then drafts a quotation for the account owner to edit. Where a detail is missing it asks the customer for that one detail instead of guessing.
Approval boundaryPricing, contracts and refunds are proposed only; a named owner reviews and sends them.
“I review and adjust now. I stopped rewriting the same email at midnight.”
BeforeSeasonal peaks decided whose week it was. Outstanding client documents were chased when someone remembered to chase them.
With the SAM teamA SAM tracks requested documents per engagement from approved checklists, drafts reminders for the engagement lead to release, and answers routine process questions from approved firm guidance while flagging anything that needs a partner’s view.
Approval boundaryNo client-facing message leaves the firm until a person releases it; fee and advice questions go to a partner.
“Chasing stopped being a memory test. Every reminder still carries someone’s name.”
DemonstrationTransport & automotive · Two depots
Workshop questions answered without the workshop
Status enquiries and booking windows
BeforeQuestions about job progress tied up the same two coordinators through the day while the yard kept moving.
With the SAM teamA SAM answers progress enquiries from approved workshop status, offers collection and delivery windows inside the operator’s service area, and hands unusual requests to the duty controller with the full transcript.
Approval boundaryAnything that changes a job time or a cost is confirmed by the controller first.
“The phones quietened down and the yard kept its rhythm.”
DemonstrationInsurance & financial services · Enterprise team
One shape of file, whatever the channel
First notice of loss capture and routing
BeforeOvernight and weekend claims arrived across several channels with no consistent record, so the morning handler started from the beginning each time.
With the SAM teamA SAM takes first contact on voice, chat and email, captures the policy reference, incident type and location, screens for the fraud and safety flags the unit has defined, and routes the file to the right queue with a summary and transcript.
Approval boundaryClaims decisions, reserves and payments stay with authorised handlers, and sensitive fields are restricted by policy.
“Every file arrives in the same shape. That consistency is what we were asking for.”
Illustrative applications · Not client deployments
The work ANNA OS is designed to support.
These scenarios explain proposed uses of the documented capabilities. They are not client stories, verified outcomes or testimonials.
ASAMIA ANNA OS · Concept illustration
Reception and customer enquiries
From an enquiry to a clear handover
A service team can design a SAM to collect the reason for an enquiry, consult approved business guidance and prepare a summary for the person responsible. A proposed appointment remains subject to the team’s approval.
An operations team can scope a SAM around approved procedures and business documents. The role can draft a response, identify missing context and refer uncertain or sensitive questions to a named reviewer instead of making a commitment.
A business owner can define acceptance checks and sign-off responsibilities for proposed model changes. The intended process compares a change against the role’s requirements and keeps approval with an authorised person.
