Multichannel intake01
One queue, every channel
Voice, SMS, email, WhatsApp and resident portal requests land on one work order with original audio and attachments intact.
The AI employee thatworks the whole shift
Chronicle answers residents, triages maintenance and coordinates vendors around the clock — executing inside your policy and handing every real decision back to a person, with nothing lost between shifts.
24/7 coverage
Inside-policy execution
Human authority on decisions
Illustrative run: intake to sealed evidence
Chronicle: intakeOne queue, every channelVoice, WhatsApp, SMS, email and the resident portal land on one work order.
Manager approval gateYour limit holdsWork past a configured limit waits for the approver the brief names.
Chronicle: recordDecisions keep their contextIntake, reasoning, approver and outbound messages stay in one chronology.
Maintenance coordination is a chain. Chronicle keeps every link in view.
No borrowed logos, invented ratings or anonymous performance claims — just the categories of work Chronicle is built to coordinate.
Diagnostic triage02
Clear reasoning up front
Urgency score, unit repair history and tenant statements arrive together before any downstream action begins.
Governance & rules03
Human approval gates
Configured budget limits and policy thresholds pause execution until a named approver explicitly authorizes the job.
Execution handoff04
Vendor dispatch briefs
Trade-matched vendor selection, full diagnostic scope, unit access codes and tenant schedule travel with the dispatch.
Context preservation05
Complete unit context
Resident photos, lease terms, warranty status and diagnostic questions stay attached in one readable sequence.
Audit & verification06
Append-only chronology
Every diagnostic step, human approval signature, vendor update and invoice is permanently sealed to the record.
A calm control room for requests that refuse to arrive neatly.
Review the request, Chronicle’s reasoning, the policy boundary and the next action without reconstructing the story yourself.
ChronicleOperations Control Room
Active triage (4)Approval hold (1)Dispatched (6)
Illustrative product runMonthly dispatch authorization+12.4%
$2,500.00
Threshold ceiling: $5,000.00
Median diagnostic latency−18 min
4m 12s
Channel intake → Reasoning complete
Governance statusActive hold
1 Pending approval
Rule R-14 triggered (spend > $250)
Work orders queue4 open
Urgent$340.00
Water under kitchen sinkUnit 4B · WhatsApp inbound · Photo attachedRoutine$120.00
Dishwasher drainage rattleUnit 12 · Resident portal · Context gatheringScheduled$85.00
Hallway light fixtureBuilding C · SMS inbound · Vendor confirmedQueued$65.00
Quarterly HVAC filter checkPolicy schedule · Recurring preventiveRequest CHR-021 · Unit 4B, Riverside
Urgent reviewWater under kitchen sink
Water appeared after running the faucet. Supply valve turned off by tenant.
IMG_4921.heic (1.4 MB)
Chronicle diagnostic reasoningHuman gate hold
Potential active supply pipe leak. Approved trade vendor (Apex Plumbing) is available with 2h response window. Quote estimated at $340.00, exceeding automatic $250.00 threshold — awaiting Property Manager authorization.
Policy rule R-14: Spend > $250.00 requires named manager sign-off
No external vendor contacted without sign-off
Chronicle: triageRanked with its reasoningUrgency, unit history and the resident’s note arrive together.
Manager approval gateConfigured limits holdWork beyond a configured limit waits for a person to approve it.
Chronicle: dispatchApproved vendors onlyPhotos, unit history and notes travel with the handoff.
Chronicle: evidenceCaptured in sequenceDecisions, messages and attachments land in one chronology.
One desk. A 24/7 AI employee that runs every request end to end.
Not a chatbot and not a rule engine — a supervised operator that queues, holds work at your approval limits, dispatches approved vendors, and keeps the evidence in one chronology.
Multichannel intakeEvery channel lands in one ranked queue.
Answers voice, WhatsApp, email and portal requests around the clock. Attaches property, unit and resident history to a single work order and ranks urgency against your policy thresholds.
- Answers voice, WhatsApp, email and portal requests around the clock.
- Attaches the property, unit and resident history to a single work order.
- Ranks the queue by urgency against the thresholds you configure.
Evidence
Voice, WhatsApp, email, tenant portal
IntakeIllustrative record
VoiceWhatsAppEmailPortal
One thread per unit, deduplicated across every channel.
Queue orderUrgency first
Human approval gateWork past your limit waits for a named person.
Pauses quotes, dispatches and spend that exceed a configured limit. Routes the decision to the authorized approver with the full brief attached.
- Pauses quotes, dispatches and spend that exceed a configured limit.
- Routes the decision to the authorized approver with the full brief attached.
- Keeps who approved what, and when, beside the request itself.
Evidence
Spend limit, named approver, audit log
Approval gateIllustrative record
Dispatch exceeds the configured limitHeld until an authorized person signs off
- Policy
- Spend limit
- Route
- Named approver
- Record
- Audit log
Outbound actionNothing sent yet
Vendor handoffThe handoff leaves with everything the vendor needs.
Matches the job to an approved vendor for that property and trade. Sends the work brief, access notes and resident availability together.
- Matches the job to an approved vendor for that property and trade.
- Sends the work brief, access notes and resident availability together.
- Keeps the resident updated as the arrival window is confirmed.
Evidence
Work brief, access notes, resident update
Vendor handoffIllustrative record
Approved plumbing vendorTrade and property match held on file
Brief sent- Work brief with photos and diagnosis
- Unit access notes and entry instructions
- Resident availability and arrival window
One chronologyEvery decision keeps the context that produced it.
Preserves the original message, photos and diagnostic answers. Records each action from intake through approval to closeout on one append-only chronology.
- Preserves the original message, photos and diagnostic answers.
- Records each action from intake through approval to closeout.
- Closes out with completion photos and the invoice on the same record.
Evidence
Original request, approval, completion photos, invoice
ChronologyIllustrative record
- Request received
- Context and urgency recorded
- Approval attributed to a person
- Handoff and closeout attached
PhotosInvoiceOriginal message
Never lose the signal inside the thread.
Sample signals drawn from the request types Chronicle classifies — not live customer traffic.
Level up the whole shift
Put a supervised operator on every request
Start with supervised triage and approvals. Widen autonomy only when your policies and your evidence support it.
Built to power the roles that already own the shift
Each panel is a Chronicle product workflow, not a customer result. Every role runs the same sequence — intake, reasoning, the human gate, dispatch and the recorded evidence — read from where they sit.
Property manager
An after-hours leak, coordinated without skipping the approval that governs it.
- Intake: machine action — A resident texts after hours with a photo. The original message and its attachment are kept, not summarised away.
- Reasoning: machine action — The request is matched to a configured intent, then read against the unit’s repair history and the brief’s after-hours instruction.
- Approval: human gate — Vendor dispatch is an approval action. The brief names the condition and the approver, so the on-call manager decides first.
- Dispatch: machine action — After approval, only the tools the brief permits run — the approved plumbing vendor is briefed, the resident is told.
- Record: machine action — Intake, reasoning, approver and outbound messages land in one chronology, pinned to the brief version that was live.
Illustrative workflow (not customer evidence)
Maintenance lead
A mixed morning queue that stays readable while every configured limit still holds.
- Intake: machine action — A safety concern, a recurring repair and routine scheduling arrive together across SMS, email and the portal.
- Reasoning: machine action — Each request carries its intent match, its urgency reasoning and the unit history that produced it.
- Authority: human gate — Work past the lead’s approval boundary holds for a named approver. What the brief forbids never runs, at any level.
- Dispatch: machine action — Approved work moves. Scheduling honours the brief’s minimum notice, its buffers and its stated restrictions.
- Record: machine action — The queue keeps what was decided, what is still waiting, and exactly who it is waiting on.
Illustrative workflow (not customer evidence)
Owner-operator
Vendor coordination and resident wording, still attached to the decision that authorised them.
- Intake: machine action — An approved repair is ready to coordinate, and the resident is owed a clear next update.
- Drafting: machine action — Chronicle prepares the vendor handoff and the resident message from the approved plan, in the tone the brief sets.
- Approval: human gate — Resident-facing communication stays an approval action, so the owner reads the exact wording before it sends.
- Handoff: machine action — The handoff runs in the brief’s mode — live transfer, callback or task — to the named target.
- Record: machine action — The authorisation and everything it produced stay joined. No message floats free of its decision.
Illustrative workflow (not customer evidence)
Resident services
A safety report and a routine request, separated without splitting the record.
- Intake: machine action — A gas-smell report and a routine scheduling request arrive after hours through different channels.
- Classification: machine action — The gas report matches a configured escalation trigger. The routine request does not, and queues against operating hours.
- Escalation: human gate — Escalation reaches a named contact inside the brief’s response window. A person owns the emergency, not the agent.
- Routing: machine action — The routine request follows the after-hours instruction and waits for the next open hours in the brief’s timezone.
- Record: machine action — Both originals survive intact, and the chronology shows which path each took and what triggered it.
Illustrative workflow (not customer evidence)
Regional director
Approvals spread across properties, still attributable without reopening source threads.
- Portfolio: machine action — Maintenance decisions across several properties sit at different approval boundaries at once.
- Reasoning: machine action — Each shows its request, the reasoning behind its urgency, and the approval rule currently holding it.
- Accountability: human gate — Sensitive actions require a named approver. Approval is attributed to that person, never to the agent.
- Control: machine action — An operator hold stops the employee outright. Published brief revisions are append-only, so history cannot be rewritten.
- Record: machine action — The decision and the context that justified it stay readable together, months later.
Illustrative workflow (not customer evidence)
Operations lead
A shift change where the next operator inherits the record, not the reconstruction.
- Intake: machine action — A shift begins with active requests spread across resident SMS, email and the portal.
- Consolidation: machine action — Each request’s original intake, attachments, unit context and latest action move into the same chronology.
- Ownership: human gate — Whatever is waiting names the approver it waits on, so nothing is ambiguously owned across the handover.
- Follow-up: machine action — Follow-ups run on the brief’s cadence, up to its maximum attempts, and stop on its stated stop conditions.
- Record: machine action — The next operator continues from the recorded decision instead of rereading the thread.
Illustrative workflow (not customer evidence)
The principles Chronicle is built on — and nothing we cannot show
Every tile below is either a product principle or a run labelled as illustrative. There are no customer names, no ratings and no measured outcomes on this page.
- Coverage guarantee24/7
Requests are answered on every connected channel, against the operating hours and after-hours instruction in your brief.
- Operating principle
The useful record is not just what happened. It is the context, decision and next step that made the outcome possible.
Chronicle product statement (not customer evidence) - Authority boundaryNamed approver
Every approval action names the person who owns it. Approval is attributed to that person, never to the agent.
- Illustrative runCHR-021
Water under a kitchen sink: intake → reasoning → approval → dispatch → recorded evidence. A product illustration, not a customer result.
- Record durabilityAppend-only
Published brief revisions cannot be rewritten, and a request stays pinned to the version that was live when it ran.
- Design principle
Every urgent request should arrive with enough context to make the next safe decision.
Chronicle product principle (not a customer testimonial) - Safety boundaryFail-closed
What the brief forbids never runs at any autonomy level, and an operator hold stops the employee outright.
Ready to supervise
Put an AI employee on the shift tonight
Start with supervised triage, clear reasoning and human approval gates. Expand autonomy only as your evidence and policy comfort grow.
No credit card required — Free 14-day evaluation — Fail-closed architecture